Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "Community standard." assertion.
- declaration considerations "Community standard." 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.
- declaration considerations "DOI are minted using the AERIS prefix" assertion.
- declaration considerations "Handle server hosted by AERIS with a prefix obtained from ePIC" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite" assertion.
- declaration considerations "Internal metadata format compliant with standards, incl. ISO 19115" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite" assertion.
- declaration considerations "community relevant" assertion.
- declaration considerations "Using AERIS AAI server (keycloak)" assertion.
- declaration considerations "Using AERIS AAI server (keycloak)" assertion.
- declaration considerations "5 years min. as stated in the ACTRIS DMP" assertion.
- declaration considerations "under development" assertion.
- declaration considerations "Home-made metadata format compliant with standards" assertion.
- declaration considerations "community relevant" assertion.
- declaration considerations "Automatic conversion from internal metadata format to Datacite" assertion.
- declaration considerations "rest api" assertion.
- declaration considerations "community relevant" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Using Thredds data server" assertion.
- declaration considerations "-" assertion.
- declaration considerations "Using Thredds data server. We need to convert all data to the NetCDF format" assertion.
- declaration considerations "Metadata are openly available" assertion.
- declaration considerations "Using AERIS AAI server (keycloak)" assertion.
- declaration considerations "Home made JSON format, compliant with standards" assertion.
- declaration considerations "conversion to netcdf planned" assertion.
- declaration considerations "Community relevant" assertion.
- declaration considerations "Ongoing submission of missing concepts" assertion.
- declaration considerations "Conversion from GEOMS HDF planned" assertion.
- declaration considerations "HDF4 files, a conversion to NetCDF is planned for ACTRIS but both formats will be distributed because HDF is required by NDACC" assertion.
- declaration considerations "Widely accepted. " assertion.
- declaration considerations "Will follow ENVRI recommendations" assertion.
- declaration considerations "Will follow ENVRI recommendations" assertion.
- declaration considerations "Commonly used within the community" assertion.
- declaration considerations "For some of the ACTRIS datasets, DOIs are still not available" assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Datacite is used by the parts of ACTRIS that have implemented DOIs for their datasets." assertion.
- declaration considerations "The metadata of the ACTRIS metadata catalog is indexed in WMO Information System (WIS) and available through their search engine." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "The metadata of the ACTRIS metadata catalog is indexed in WMO Information System (WIS) and available through their search engine." assertion.
- declaration considerations "Community relevant" assertion.
- declaration considerations "Metadata available in the ACTRIS data portal through HTTPS." assertion.
- declaration considerations "Direct download via primary repositories through HTTPS." assertion.
- declaration considerations "Streaming of data using OPeNDAP." assertion.
- declaration considerations "Requirement by European Commision." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "ACTRIS internal vocabulary is used for variable names in the ACTRIS data portal." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Community relevant." assertion.
- declaration considerations "Cost effective solution, our data portal requires lots of PIDs due to large number of digital objects." assertion.
- declaration considerations "Will be used to identify people." assertion.
- declaration considerations "DOIs required for collections, e.g. yearly data sets." assertion.
- declaration considerations "Our data portal already assigns PIDs (EPIC handle) for any arbitrary data collection downloaded by the user." assertion.
- declaration considerations "Widely used format in the community." 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 "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 "Most convenient protocol." assertion.
- declaration considerations "It's the standard." assertion.
- declaration considerations "Easy access to data for users." assertion.
- declaration considerations "Open access required by the community. Easy access to metadata." assertion.
- declaration considerations "Open access required by the community. Easy access to data." assertion.
- declaration considerations "Implementation in progress." assertion.
- declaration considerations "It's the most widely used format." assertion.
- declaration considerations "Widely used." assertion.
- declaration considerations "Standard." assertion.
- declaration considerations "Need internal one. Not yet implemented." assertion.
- declaration considerations "Standard." assertion.
- declaration considerations "Best option." assertion.
- declaration considerations "Requirement." 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 "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 "Training and education for the data providers, managers, stewards for understanding different aspects of open data licenses. " assertion.
- declaration considerations "The identifier system should be able to accommodate Digital Specimens (a specific type of FAIR Digital Object) and related metadata. " assertion.
- declaration considerations "The identifier system should be able to accommodate Digital Specimens (a specific type of FAIR 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 "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 "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 "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 "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 "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 "currently under development. Needs to align with existing specifications and also efforts from other research infrastructure in the biodiversity domain. " 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 "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.