페이지 이력

...

...

•   CV Data Acquisition: EUDAT does not offer facilities for subsys_acq, relying on data already gathered by client RIs.
•   CV Data Curation: EUDAT can provide instances of any of the computational objects used for data curation (including data store controller, CV Data Curation#data data transfer service and 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.
•   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 broker would sit in front of the EUDAT broker, forwarding data requests that involve data delegated to EUDAT.
•   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 subsys_pro.
• Whilst certain aspects of EUDAT such as the Simple Store for researchers might be directly accessible as an independent  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 security service would integrate the EUDAT AAI service to allow seamless integration of EUDAT-held datasets with locally-held RI datasets.
  
  

...