| Latest revision |
Your text |
| Line 20: |
Line 20: |
| | The ENVRI Reference Model models an archetypical environmental research infrastructure (RI). As a service infrastructure, EUDAT itself is therefore not an implementation of the Reference Model, but is rather a source of implementations for instances of objects required by any RI implementing the Model. | | The ENVRI Reference Model models an archetypical environmental research infrastructure (RI). As a service infrastructure, EUDAT itself is therefore not an implementation of the Reference Model, but is rather a source of implementations for instances of objects required by any RI implementing the Model. |
| | | | |
| − | <center>'''Table 1''': Mapping EUDAT Services to the Reference Model Elements</center>
| |
| | | | |
| − | {| class="wikitable" style="background-color:#ffffff; margin: auto;"
| |
| − | |-
| |
| − | | style="padding: 7px"| '''EUDAT Services''' || '''Computational Viewpoint''' || '''ENVRI Common Subsystem'''
| |
| − | |-
| |
| − | | style="padding: 7px"| Safe replication || [[File:lightbulb.png|16px]] [[CV Data Curation|'''data transfer service''']] || [[File:lightbulb.png|16px]] [[CV Data Curation|'''CV Data Curation''']]
| |
| − | |-
| |
| − | | style="padding: 7px"| Staging || [[File:lightbulb_on.png|16px]] [[CV Data Curation|'''data importer''']] || [[File:lightbulb.png|16px]] [[CV Data Curation|'''CV Data Curation''']]
| |
| − | |-
| |
| − | | style="padding: 7px"| Metadata Catalogue || [[File:lightbulb.png|16px]] [[CV Data Curation|'''catalogue service''']] || [[File:lightbulb.png|16px]] [[CV Data Curation|'''CV Data Curation''']]
| |
| − | |-
| |
| − | | style="padding: 7px"| Simple Store || [[File:lightbulb_on.png|16px]] [[CV Data Curation|'''data store controller''']] || [[File:lightbulb.png|16px]] [[CV Data Curation|'''CV Data Curation''']]
| |
| − | |}
| |
| − |
| |
| − | From the [[File:lightbulb.png|16px]] [[:Category:Computational Viewpoint|'''''computational''''']] perspective, EUDAT offers services that can be used to instantiate various objects in the Reference Model. For example EUDAT’s Safe Replication facilities can implement various required services within the [[File:lightbulb.png|16px]] [[Model Overview|'''subsys_cur''']] of an environmental RI:
| |
| − |
| |
| − | * [[File:lightbulb_on.png|16px]] [[CV Data Acquisition|'''CV Data Acquisition''']]: EUDAT does not offer facilities for [[File:lightbulb_on.png|16px]] [[Model Overview|'''subsys_acq''']], relying on data already gathered by client RIs.
| |
| − | * [[File:lightbulb.png|16px]] [[CV Data Curation|'''CV Data Curation''']]: EUDAT can provide instances of any of the computational objects used for data curation (including [[File:lightbulb.png|16px]] [[CV Data Curation|'''data store controller''']], [[File:lightbulb.png|16px]] [[CV Data Curation|'''data transfer service''']] and [[File:lightbulb.png|16px]] [[CV Data Curation|'''catalogue service''']]), either in place of or complementary to instances provided by an environmental RI – the extent to which EUDAT assumes the curation role for an infrastructure will vary from case-to-case.
| |
| − | * [[File:lightbulb_on.png|16px]] [[Example 2: Using the Reference Model as an Analysis Tool (EUDAT)#|'''CV Data Access''']]: Data access to EUDAT curated data is brokered by EUDAT, whilst the RI would broker RI-curated data. In practice the RI [[File:lightbulb_on.png|16px]] [[Example 2: Using the Reference Model as an Analysis Tool (EUDAT)#|'''broker''']] would sit in front of the EUDAT broker, forwarding data requests that involve data delegated to EUDAT.
| |
| − | * [[File:lightbulb_on.png|16px]] [[CV Data Processing|'''CV Data Processing''']]: EUDAT do not offer data processing (beyond ''metadata annotation'') as a core service; ''workflow enactment'' is being investigated as a future service however, which would allow a later version of the EUDAT platform to implement elements of a [[File:lightbulb_on.png|16px]] [[Model Overview|'''subsys_pro''']].
| |
| − | * Whilst certain aspects of EUDAT such as the Simple Store for researchers might be directly accessible as an independent [[File:lightbulb_on.png|16px]] [[CV Data Use|'''gateway service''']], in general EUDAT sits behind a client RI, its services hidden behind the RI’s native services from the perspective of the RI’s user community. It would be likely however that the ‘virtual laboratories’ by which community groups interact with an RI would be in some way augmented by EUDAT services; in particular, implementations of the [[File:lightbulb_on.png|16px]] [[CV Data Use|'''security service''']] would integrate the EUDAT AAI service to allow seamless integration of EUDAT-held datasets with locally-held RI datasets.
| |
| − |
| |
| − | The most immediately apparent conclusion that can be drawn from cursory analysis of EUDAT services in the context of the Reference Model is that EUDAT can potentially implement the entire [[File:lightbulb.png|16px]] [[CV Data Curation|'''CV Data Curation''']] of an environmental RI; however in practice, one would expect that an RI would retain a certain amount of data locally (particularly raw data that is expensive to transfer off-site), necessitating a more nuanced division of labour between the RI and EUDAT. In particular, EUDAT provides replication services, allowing the co-existence of RI and EUDAT data stores holding the same data, and EUDAT provides metadata (including global persistent identifier) services, allowing EUDAT to provide any [[File:lightbulb.png|16px]] [[CV Data Curation|'''catalogue service''']] (probably complementary to catalogue services maintained by an environmental RI itself). The delegation of services will be a product of negotiation between the environmental RI and the EUDAT project (some degree of automation may be possible, but likely sufficient for only smaller projects).
| |
| − |
| |
| − | == <span style="color: #BBCE00">Summary</span> ==
| |
| − |
| |
| − | The principal potential benefit of using the Reference Model in general is the ability to precisely identify components required by an environmental RI and then identify how (if at all) the RI implements those components. In the EUDAT context, EUDAT provides a number of services that implement certain components (primarily in [[File:lightbulb.png|16px]] [[CV Data Curation|'''CV Data Curation''']]); it should therefore be possible to identify the equivalent services in a modelled RI and determine whether or not there is a benefit to delegating those services to EUDAT. This decision may be based on cost (particularly related to economies of scale) and development time (in cases where the RI has not yet implemented the service, but may be able to use the EUDAT service instead).
| |
| | [[Category:Appendix D Guidlines for using the Reference Model]] | | [[Category:Appendix D Guidlines for using the Reference Model]] |
