Difference between revisions of "CV Presentation Objects"
Line 35: | Line 35: | ||
* A science gateway object can instantiate any number of [[CV_Presentation_Objects#Virtual_laboratory|'''virtual laboratory''']] objects. | * A science gateway object can instantiate any number of [[CV_Presentation_Objects#Virtual_laboratory|'''virtual laboratory''']] objects. | ||
+ | == <span style="color: #BBCE00">Virtual laboratory</span> == | ||
+ | {| class="wikitable" style="background-color:#ffffff; float:right; margin-left: 10px;" | ||
+ | |- | ||
+ | |style="padding: 0px"| [[File:CVOVirtualLaboratory.png]] | ||
+ | |} | ||
+ | ''Community proxy for interacting with RI components.'' | ||
+ | |||
+ | A virtual laboratory object encapsulates interaction between a user or group of users and a subset of the science functions provided by a research infrastructure. Its role is to bind a [[CV_Service_Objects#AAAI_service|'''AAAI service''']] with (potentially) any number of other infrastructure objects. | ||
+ | |||
+ | A virtual laboratory object must provide at least one interface: | ||
+ | |||
+ | * '''authorise action (client)''' is used to retrieve authorisation for any restricted interactions with the data acquisition components. | ||
+ | |||
+ | Specific sub-classes of virtual laboratory should be defined to interact with the infrastructure in different ways. The ENVRI RM defines the [[CV_Presentation_Objects#Field_laboratory|'''field laboratory''']] object for interaction with the [[CV Data Acquisition|'''CV Data Acquisition''']] components. | ||
+ | |||
+ | == <span style="color: #BBCE00">Field laboratory</span> == | ||
+ | {| class="wikitable" style="background-color:#ffffff; float:right; margin-left: 10px;" | ||
+ | |- | ||
+ | |style="padding: 0px"| [[File:CVOFieldLaboratory.png]] | ||
+ | |} | ||
+ | ''Community proxy for interacting with data acquisition instruments.'' | ||
+ | |||
+ | A sub-class of [[CV_Presentation_Objects#Virtual_laboratory|'''virtual laboratory''']] object encapsulating the functions required to access, calibrate, deploy or withhold instruments during the data acquisition phase. | ||
+ | |||
+ | Deployment of an instrument entails the deployment of an instrument controller by which the instrument can be interacted with. | ||
+ | |||
+ | * A field laboratory object can instantiate any number of [[CV_Component_Objects#Instrument_controller|'''instrument controller''']] objects. | ||
+ | |||
+ | A field laboratory should provide at least two operational interfaces in addition to those provided by any virtual laboratory: | ||
+ | |||
+ | * '''calibrate instrument (client)''' is used to calibrate the reading of data by instruments based (in principle) on scientific analysis of data output. This interface can also be used to monitor activity on a given instrument. | ||
+ | * '''update registry (client)''' is used to register and/or withdraw instruments used for data acquisition. | ||
+ | |||
+ | <p style="background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px 20px 10px 20px;"> | ||
+ | '''Note'''<br> | ||
+ | A field laboratory is created by a science gateway in order to allow researchers in the field to interact with the data acquisition objects. | ||
+ | |||
+ | The degree of freedom with which a field laboratory interacts with other data acquisition objects is contingent on the nature of the research infrastructure and policed by a [[CV_Service_Objects#AAAI_service|'''AAAI service''']] object (as defined for all user laboratories). | ||
+ | </p> | ||
[[Category:CV Objects]] | [[Category:CV Objects]] |
Revision as of 20:35, 27 March 2020
CV Presentation objects are the entry points for human users to the systems and services provided to access research data and their derived products. In the ENVRI RM, complex interactions between the components facilitating data use and other components are mediated by virtual laboratory; these objects are deployed by science gateways in order to provide a persistent context for such interactions between groups of users and components within the RI. The Reference Model recognises the following specific sub-classes of laboratory:
Regardless of provenance, all laboratories must interact with a AAAI service in order to authorise requests and authenticate users of the laboratory before they can proceed with any privileged activities. |
|
Science gateway
Community portal for interacting with an infrastructure.
A science gateway object encapsulates the functions required to interact with a research infrastructure from outside with the objects provided for data acquisition, data curation, data brokering and data processing. A science gateway should be able to provide virtual 'laboratories' for authorised agents to interact with and possibly configure many of the science functions of a research infrastructure. A science gateway is also known as a Virtual Research Environment.
- A science gateway object can instantiate any number of virtual laboratory objects.
Virtual laboratory
Community proxy for interacting with RI components.
A virtual laboratory object encapsulates interaction between a user or group of users and a subset of the science functions provided by a research infrastructure. Its role is to bind a AAAI service with (potentially) any number of other infrastructure objects.
A virtual laboratory object must provide at least one interface:
- authorise action (client) is used to retrieve authorisation for any restricted interactions with the data acquisition components.
Specific sub-classes of virtual laboratory should be defined to interact with the infrastructure in different ways. The ENVRI RM defines the field laboratory object for interaction with the CV Data Acquisition components.
Field laboratory
Community proxy for interacting with data acquisition instruments.
A sub-class of virtual laboratory object encapsulating the functions required to access, calibrate, deploy or withhold instruments during the data acquisition phase.
Deployment of an instrument entails the deployment of an instrument controller by which the instrument can be interacted with.
- A field laboratory object can instantiate any number of instrument controller objects.
A field laboratory should provide at least two operational interfaces in addition to those provided by any virtual laboratory:
- calibrate instrument (client) is used to calibrate the reading of data by instruments based (in principle) on scientific analysis of data output. This interface can also be used to monitor activity on a given instrument.
- update registry (client) is used to register and/or withdraw instruments used for data acquisition.
Note
A field laboratory is created by a science gateway in order to allow researchers in the field to interact with the data acquisition objects.
The degree of freedom with which a field laboratory interacts with other data acquisition objects is contingent on the nature of the research infrastructure and policed by a AAAI service object (as defined for all user laboratories).