Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Will follow ENVRI-FAIR recommendations" assertion.
- declaration considerations "Metadata are stored in a MongoDB database. Documents are identified by a UUID." assertion.
- declaration considerations "DOI are minted using the AERIS prefix (obtained via the French member of Datacite: INIST-CNRS)" assertion.
- declaration considerations "DOI are minted using the AERIS prefix (obtained via the French member of Datacite: INIST-CNRS)" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite schema" assertion.
- declaration considerations "widely used in community" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite" assertion.
- declaration considerations "REST api" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Using Thredds data server. We would need to convert all data to the NetCDF format" assertion.
- declaration considerations "Metadata are openly available" assertion.
- declaration considerations "Data are open" assertion.
- declaration considerations "5 years min. as defined in the ACTRIS DMP" assertion.
- declaration considerations "Home made JSON format, compliant with standards" assertion.
- declaration considerations "Conversion of all data to NetCDF planned. " assertion.
- declaration considerations "Community relevant" assertion.
- declaration considerations "under development" assertion.
- declaration considerations "Ongoing submission of missing names" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Community standard" assertion.
- declaration considerations "Wide" assertion.
- declaration considerations "Will follow ENVRI-FAIR recommendations" assertion.
- declaration considerations "Will follow ENVRI-FAIR recommendations" 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 "DiSSCo does not specifically distinguish between data and metadata for digital specimen, allowing most data fields to be used also as metadata for discovery. " assertion.
- declaration considerations "Understanding how schema.org works with the Digital Object Architecture." assertion.
- declaration considerations "A FAIR service providing access to Digital Specimens and Collections. Harmonising data from different types of collections and institutions of different sizes can be a challenge. " assertion.
- declaration considerations "Ensuring interoperability between DiSSCo and GBIF infrastructures. " assertion.
- declaration considerations "A FAIR service providing access to Digital Specimens and Collections. Harmonising data from different types of collections and institutions of different sizes can be a challenge. As each individual specimen is described as Digital Object, the dataset concept for DiSSCo is not clearly defined. Collection Object (group of Digital Specimens) can be thought of as datasets. " assertion.
- declaration considerations "Different systems (bata providers are not aware of DOIP and not compatible yet. " assertion.
- declaration considerations "A common guidelines and recommendations for application programming interfaces (APIs) is lac" 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 "JSON Schema alone is not enough for validation, need semantic validation (JSON-LD etc.)" assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " 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 "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 "Each object contains a minimum of mandatory terms consistent with its formal object type definition, with the possibility to include optional additional terms and enrichments as necessary." assertion.
- declaration considerations "We might need to use different licenses for certain attributes of the objects. At the moment, our idea is as open as possible and as closed legally necessary. For example, hiding location data for endangered species. " assertion.
- declaration considerations "Training and education for the data providers, managers, stewards for understanding different aspects of open data licenses. " assertion.
- declaration considerations "There are other alternatives and options out there (Cloudevents, distributed ledgers, other transactional systems). How to combine these?" assertion.
- declaration considerations "There are other alternatives and options out there (Cloudevents, distributed ledgers, other transactional systems). How to combine these?" assertion.
- declaration considerations "Widely used for data citation, mainly used by us for collections and elaborated data products" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "Handle PIDs are used for all data objects at the highest possible granularity" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "under way" assertion.
- declaration considerations "Used in Jupyter hub and many other applications by the community for easy access to SPARQL, ontology, metadatahttps://pypi.org/project/icoscp/" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "The ICOS SPARQL open endpoint https://meta.icos-cp.eu/sparql serves (read-only) the complete ICOS ontology and all metadata in RDF format. It is used by most back-end and front-end services of the ICOS Carbon Portal. A GUI version is served at https://meta.icos-cp.eu/sparqlclient/" assertion.
- declaration considerations "The m2m interfaces to interact with the meta and data services and other back end services are based on REST 'inspired' https calls. The calls are document at the CP github repository at pages https://github.com/ICOS-Carbon-Portal/meta and https://github.com/ICOS-Carbon-Portal/data" assertion.
- declaration considerations "Used in Jupyter hub and many other applications by the community for easy access to SPARQL, ontology, metadatahttps://pypi.org/project/icoscp/" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "Through ERDDAP (Ocean domain)" assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "For ORCID and Facebook identity providers " assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "All ICOS data is available open and free." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "ICOS is set up for the long term, 20-25 years starting from 2015. Statutes and data policy mention that data and metadata should be preserved also after that. In case ICOS ERIC is wound down in the future there will be a one year period to develop the contingency plan. All current landing pages generated dynamically by our metadata system can then be generated as static html pages that will together form a frozen metadata system which can be served by a simple static website at very low cost or be integrated as sub-site in another permanent website." assertion.
- declaration considerations "CF-1.7 compliant netcdf metadata included in the netcdf data objects" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "http://meta.icos-cp.eu/ontologies/cpmeta/" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "Metadata are stored in a MongoDB database. Documents are identified by a UUID." assertion.
- declaration considerations "DOI are minted using the AERIS prefix" assertion.