This step establishes how the project team will obtain the research object and the metadata, documentation, dependencies and provenance required to be able to analyse and work on it.
Access may be open or controlled and may be provided through an API, query interface, repository download, version-control system, bulk-transfer service, object store or secure processing environment. The output may be a local or staged working copy, or authorised access within an environment where the object cannot be exported.
This step requires sufficient information to repeat and verify acquisition. It does not focus on the final exchange formats or the eventual release mechanism for the FAIRified research object.
The hosting environment considered here acts as a source for the FAIRification activity. It may also be retained, improved or complemented as a target environment where the FAIRified research object is deployed to in a later step. Where limitations in its access or retrieval capabilities need to be addressed, record these as potential tasks for later implementation.
During project examination you can use the related capabilities as a guide to determine what access and retrieval capabilities are required, what is already available and what gaps could prevent the work from proceeding.
During an implementation cycle, you can use the related capabilities to identify potential tasks and relevant resources to establish and validate the required access and retrieval arrangements.
Research object access
Research object retrieval
Research object deposition
Research object versioning
Research object transfer
Rights and reuse conditions
Privacy and disclosure control
Release management
Research object access
Ensure that the FAIRification team is permitted and technically able to reach the research object and its associated metadata.
Examples of concerns:
- Open, registered or controlled access
- Authentication and authorisation
- Data-access applications and approvals
- Secure-environment requirements
- API or repository availability
- Applicable conditions affecting acquisition and project use
Resources
2 ELIXIR Stories items
- Intrinsically Disordered Protein Community Interoperability Showcase: Exploiting Bioschemas Markup Cascade mapping from FT 1: easier/better access to data via W3C standardised SPARQL endpoints (ideally machine interpretable) instead of custom APIs (for humans to implement/adapt to)
- Plant Sciences Community Showcase Cascade mapping from FT 1, 7: hosting capabilities showcased with FAIRDARE
3 FAIR Metroline items
- Data access and retrieval Focuses on how data is accessed and retrieved from the source, which directly underpins data access.
- Define access conditions Clarifies who can access the data and under which restrictions, making data access operational.
- Obtain informed consent Links data access to the conditions set by consent, especially where future use and reuse are concerned.
3 FAIR Cookbook items
Research object retrieval
Ensure that the required research object, version, components and metadata can be selected, obtained/downloaded and verified by the FAIRification team.
Considerations relating to research object retrieval, eg query language, results representation and exporting capabilities
Resources
2 ELIXIR Stories items
- Intrinsically Disordered Protein Community Interoperability Showcase: Exploiting Bioschemas Markup Cascade mapping from FT 1: easier/better access to data via W3C standardised SPARQL endpoints (ideally machine interpretable) instead of custom APIs (for humans to implement/adapt to)
- Plant Sciences Community Showcase Cascade mapping from FT 1, 7: hosting capabilities showcased with FAIRDARE
2 FAIR Metroline items
- Data access and retrieval Addresses how data can be obtained from its source, which is central to data retrieval.
- Query (use) over resources Enables retrieval through searching and querying resources in a structured and reusable way.