The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "DCH-RP:PoC 2 Evaluate EUDAT services"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{DCH-RP:PoC_main_menu}} {{DCH-RP:PoC_PoC2_submenu}} {{TOC_right}} | {{DCH-RP:PoC_main_menu}} {{DCH-RP:PoC_PoC2_submenu}} {{TOC_right}} | ||
== Introduction == | |||
This experiment will look at the suitability of the EUDAT services for DCH. | This experiment will look at the suitability of the EUDAT services for DCH. | ||
The EUDAT project provides two services that may be of interest to the DCH community: | The EUDAT project provides two services that may be of interest to the DCH community: | ||
* B2SAFE - offers functionality to replicate datasets across different data centres in a safe and efficient way while maintaining all information required to easily find and query information about the replica locations. The information about the replica locations and other important information is stored in PID records, each managed in separate administrative domains.The B2SAFE Service is implemented as an iRODS module providing a set of iRODS rules or policies to interface with the '''EPIC handle API''' and uses the '''iRODS middleware''' to replicate datasets from a source data (or community) centre to a destination data centre. See [http://www.eudat.eu/b2safe B2SAFE webpage] for details. | * '''B2SAFE''' - the central EUDAT service that offers functionality to replicate datasets across different data centres in a safe and efficient way while maintaining all information required to easily find and query information about the replica locations. The information about the replica locations and other important information is stored in PID records, each managed in separate administrative domains.The B2SAFE Service is implemented as an iRODS module providing a set of iRODS rules or policies to interface with the '''EPIC handle API''' and uses the '''iRODS middleware''' to replicate datasets from a source data (or community) centre to a destination data centre. See [http://www.eudat.eu/b2safe B2SAFE webpage] for details. | ||
* '''B2SHARE''' - (previously SimpleStore) is a customised version of Invenio ([http://invenio-software.org/ invenio-software.org]) designed to offer a simple mechanism for uploading and sharing scientific data with associated metadata. It is intended for a large number of small files, like spread-sheet files with research data or analysis results, which may contain important data but do not easily fit in with regular data management. See [http://www.eudat.eu/b2share B2SHARE webpage] and [https://github.com/B2SHARE/b2share/wiki/User-Documentation B2SHARE User Documentation] for details. | |||
The B2SAFE service is interesting for DCH data from the point of view of assuring data sustainability and it will be used as a base layer for this experiment. However, B2SAFE offers quite low level interface which may occur impractical. The DCH institutions usually need easy access to their data and possibility to share the data between users and organizations. Thus, an additional layer for simplifying the access is needed. At the moment, three possible scenarios are considered, each of them using different tool or service as the upper layer of the software stack. They are shown on the below pictures: | |||
<gallery mode="traditional" widths=320px heights=400px> | |||
Image:b2share-b2safe.png|B2SHARE and B2SAFE scenario | |||
Image:nds2-b2safe.png|NDS2 GUI client and B2SAFE scenario | |||
Image:dlibra-b2safe.png|Community client and B2SAFE scenario | |||
</gallery> | |||
== B2SAFE workfow == | |||
The picture below shows B2SAFE workflow. [[File:b2safe.png|frame|B2SAFE workflow]] | |||
[[Category:Proofs Of Concept 2]] | [[Category:Proofs Of Concept 2]] | ||
Revision as of 14:55, 4 March 2014
| WP5: Proofs of Concept | Scenarios | PoC Phase 1 | PoC Phase 2 | DCH Glossary |
Introduction
This experiment will look at the suitability of the EUDAT services for DCH. The EUDAT project provides two services that may be of interest to the DCH community:
- B2SAFE - the central EUDAT service that offers functionality to replicate datasets across different data centres in a safe and efficient way while maintaining all information required to easily find and query information about the replica locations. The information about the replica locations and other important information is stored in PID records, each managed in separate administrative domains.The B2SAFE Service is implemented as an iRODS module providing a set of iRODS rules or policies to interface with the EPIC handle API and uses the iRODS middleware to replicate datasets from a source data (or community) centre to a destination data centre. See B2SAFE webpage for details.
- B2SHARE - (previously SimpleStore) is a customised version of Invenio (invenio-software.org) designed to offer a simple mechanism for uploading and sharing scientific data with associated metadata. It is intended for a large number of small files, like spread-sheet files with research data or analysis results, which may contain important data but do not easily fit in with regular data management. See B2SHARE webpage and B2SHARE User Documentation for details.
The B2SAFE service is interesting for DCH data from the point of view of assuring data sustainability and it will be used as a base layer for this experiment. However, B2SAFE offers quite low level interface which may occur impractical. The DCH institutions usually need easy access to their data and possibility to share the data between users and organizations. Thus, an additional layer for simplifying the access is needed. At the moment, three possible scenarios are considered, each of them using different tool or service as the upper layer of the software stack. They are shown on the below pictures:
B2SHARE and B2SAFE scenario
NDS2 GUI client and B2SAFE scenario
Community client and B2SAFE scenario
B2SAFE workfow
The picture below shows B2SAFE workflow.
B2SAFE workflow