Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "For the atmosphere domain" assertion.
- declaration considerations "For the atmosphere domain" 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 "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 "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Harmonization of the vocabulary is still required. Under development." assertion.
- declaration considerations "Harmonization of the vocabulary is still required. Under development." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "There are multiple licenses being used within EPOS. This is a federation of services, each of them can select their own license." assertion.
- declaration considerations "Generic." assertion.
- declaration considerations "Generic." assertion.
- declaration considerations "The identifier should be able to handle Digital Specimens (a specific type of Digital Object) and related metadata. " assertion.
- declaration considerations "A Registration Agency for Digital Specimen and Natural Science Collections data is needed given the diverse and cross-cutting needs for specimen data. A global engagement is required to realise the potential power of persistent identifiers." 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 "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 "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 "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 "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 "Availability (in contrast to DOIs), easy maintenance of local handle server, etc" assertion.
- declaration considerations "Standard, compatibility with B2FIND harvesting, etc" assertion.
- declaration considerations "Use has been evaluated in EUDAT prototype project" 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 "MADRIGAL has served well for distributing analysed data from the legacy systems and will remain in use for that purpose. It will not scale well to EISCAT_3D data however." 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 "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 "Available identity providers of all EISCAT users, including those in China and Japan, must be federated." assertion.
- declaration considerations "An old de facto standard among incoherent scatter radars and other upper atmospheric instruments." assertion.
- declaration considerations "MADRIGAL data are archived in a legacy binary format. Transfer to a HDF5 based standard is going on." assertion.
- declaration considerations "Agreed by EISCAT Associates." assertion.
- declaration considerations "Description was implemented as a prototype exercise in ENVRI." assertion.
- declaration considerations "No specific constraints related to UUID use. Limitation is about the incomplete production of metadata records" assertion.
- declaration considerations "Non-systematic and heterogeneous practice between platforms. Need for implementation support" 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 "Non-systematic usage among platforms IS." assertion.
- declaration considerations "DCAT-AP is intended to be the unifying profile in the ENVRI context." assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "GeoNetwork, in use in the AnaEE France community." assertion.
- declaration considerations "In use in the AnaEE France community. CKAN portal wil be implemented at the AnaEE EU level,with the objective of indexing the platform remote catalogues" assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "no additional elements to report" assertion.
- declaration considerations "Preliminary state. Only registered users in a local internal database have write access. " 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 "DMP not yet completed" assertion.