Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Internal data transfer" assertion.
- declaration considerations "Under discussion" assertion.
- declaration considerations "Metadata in JSON format through REST API" assertion.
- declaration considerations "Currently joining italian DataCite consortium" assertion.
- declaration considerations "NetCDF compliant with Climate and Forecasts (CF) Metadata Convention v1.7" assertion.
- declaration considerations "RESTful API" assertion.
- declaration considerations "THREDDS catalog" assertion.
- declaration considerations "RESTful API" assertion.
- declaration considerations "NetCDF 1.7 compliance" assertion.
- declaration considerations "NetCDF compliant with Climate and Forecasts (CF) Metadata Convention v1.7" assertion.
- declaration considerations "EPIC handle PID points to DO landing page containing the URL of the actual file for downloading, and each file contains PID to the corresponding landing page." assertion.
- declaration considerations "THREDDS catalog" assertion.
- declaration considerations "Internal data transfer" assertion.
- declaration considerations "history and traceability information" assertion.
- declaration considerations "Widely used format in the community." assertion.
- declaration considerations "It's the standard." assertion.
- declaration considerations "Easy access to data for users." assertion.
- declaration considerations "Widely used." assertion.
- declaration considerations "Need internal one. Not yet implemented." assertion.
- declaration considerations "Non-systematic and heterogeneous practice between platforms. Need for implementation support" assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "Not yet implemented. Preliminary work in 2021" assertion.
- declaration considerations "Planned at least in the AnaEE France community." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Preliminary state for an institutional repository. 1) Open access for published data on Dataverse repository. 2) Restricted access for contributors." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Planned to be integrated in the AnaEE pipelines." assertion.
- declaration considerations "Not yet implemented. Planned to be integrated in the AnaEE semantic pipelines." assertion.
- declaration considerations "Non-systematic and heterogeneous practice between platforms. Need for implementation support." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Not yet completed." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Initially used in the AnaEE France community." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "No specific constraints related to UUID use. Limitation is about the incomplete production of metadata records." assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Preliminary state for an institutional repository. 1) Open access for published data on Dataverse repository. 2) Restricted access for contributors." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "Initially used in the AnaEE France community. To be extended to EU level." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" assertion.
- declaration considerations "The identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "The FAIR Digital Object model should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata and a wide variety of collections and specimens data. For Digital Specimens, often there is no distinction between data and metadata, the attributes for the digital object should be index and discoverable. " assertion.
- declaration considerations "Ensuring interoperability between DiSSCo and GBIF infrastructures. " assertion.
- declaration considerations "Different systems (bata providers are not aware of DOIP and not compatible yet. " assertion.
- declaration considerations "DOIP is not natively supported in the systems currently used in the community. At the moment it only provides JSON response." assertion.
- declaration considerations "A single sign on (SSO) interface that is compatible with EOSC and AARC guidelines. Not all the institutions are AAI federation ready so alternative federated login options need to be provided (such as orcid, google). " assertion.
- declaration considerations "A policy to help the community understand what data should be open or not. How to handle ethical and legal issues. " assertion.
- declaration considerations "The Data Management Plan is a living document. Proper training, resources need to be in place for " assertion.
- declaration considerations "DarwinCore Archive provides a mechanism to share data in a tab delimited format. " assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " assertion.
- declaration considerations "Again, concept of datasets need to be defined within our community. " assertion.
- declaration considerations "There are other alternatives and options out there (Cloudevents, distributed ledgers, other transactional systems). How to combine these?" assertion.
- declaration considerations "The identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "The identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "The FAIR Digital Object model should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata and a wide variety of collections and specimens data. For Digital Specimens, often there is no distinction between data and metadata, the attributes for the digital object should be index and discoverable. " assertion.
- declaration considerations "Ensuring interoperability between DiSSCo and GBIF infrastructures. " assertion.
- declaration considerations "Different systems (bata providers are not aware of DOIP and not compatible yet. " assertion.
- declaration considerations "DOIP is not natively supported in the systems currently used in the community. At the moment it only provides JSON response." assertion.
- declaration considerations "REST is widely use however, not all systems will have a REST API endpoint. Alternative would be to import the data." assertion.
- declaration considerations "A single sign on (SSO) interface that is compatible with EOSC and AARC guidelines. Not all the institutions are AAI federation ready so alternative federated login options need to be provided (such as orcid, google). " assertion.
- declaration considerations "The Data Management Plan is a living document. Proper training, resources need to be in place for." assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " assertion.
- declaration considerations "The specification design work in openDS is an iterative process. There will be pilots and testing done of the concepts via the cordra software implementation at nsidr.org." assertion.
- declaration considerations "Standard, compatibility with B2FIND harvesting, etc" assertion.
- declaration considerations "Existing EISCAT datasets should be downloadable through a web browser. For future EISCAT 3D data it is planned to use DIRAC to stage data for analysis on grid or cloud resources." assertion.
- declaration considerations "Availability (in contrast to DOIs), easy maintenance of local handle server, etc" assertion.
- declaration considerations "Use has been evaluated in EUDAT prototype project" assertion.
- declaration considerations "Compatibility with B2FIND" assertion.
- declaration considerations "Existing EISCAT datasets should be downloadable through a web browser. For future EISCAT 3D data it is planned to use DIRAC to stage data for analysis on grid or cloud resources." assertion.
- declaration considerations "This is a legacy system that will be merged with the EISCAT_3D data portal in future. Implementation TBD." assertion.
- declaration considerations "EISCAT is a member o the PITHIA Network of Research Facilities and PITHIA builds upon developments during the ESPAS FP7 project." assertion.
- declaration considerations "A version of the EISCAT data download server which is an OIDC introspection enabled Checkin client has been developed." assertion.
- declaration considerations "Used in EISCAT HDF5 archive format for Level 3 data (analysed physical parameters)" assertion.
- declaration considerations "Analysed data from EISCAT radars (Level 3 data) are now archived in a dedicated HDF5 format and indexed in a SQL database with DataCite metadata records." assertion.
- declaration considerations "eLTER DIP is the central access point to eLTER metadata from a range of sources using geonetwork as backbone technology. " assertion.
- declaration considerations "DEIMS-SDR REST-API shares information on sites, locations, sensors, datasets and networks as json." assertion.
- declaration considerations "See also DEIMS REST-API." assertion.
- declaration considerations "Direct download using https/http request for datasets shared via B2SHARE." assertion.
- declaration considerations "Direct download using https/http request for datasets shared via B2SHARE." assertion.
- declaration considerations "Will be replaced by the eLTER RI DMP." assertion.
- declaration considerations "Will be replaced by the eLTER RI DMP." assertion.
- declaration considerations "Will be replaced by the eLTER RI DMP." assertion.
- declaration considerations "Will be replaced by the eLTER RI DMP." assertion.
- declaration considerations "Will be replaced in the long run by the final eLTER RI Data Spec." assertion.
- declaration considerations "Will be replaced in the long run by the final eLTER RI Data Spec." assertion.