Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "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 "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 "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 "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 "" assertion.
- declaration considerations "" 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 "Understanding how schema.org works with the Digital Object Architecture." assertion.
- declaration considerations "Understanding how schema.org works with the Digital Object Architecture." assertion.
- declaration considerations "Understanding how schema.org works with the Digital Object Architecture." assertion.
- declaration considerations "Understanding how schema.org works with the Digital Object Architecture." assertion.
- declaration considerations "Understanding how schema.org works with the Digital Object Architecture." 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 "A policy to help the community understand what data should be open or not. How to handle ethical and legal issues. " 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 "A policy to help the community understand what data should be open or not. How to handle ethical and legal issues. " 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 "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 "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 "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 "The metadata is always connected to/or part of the respective datasets." assertion.
- declaration considerations "Analysed data inserted in Madrigal are also indexed by experiment in https://handle.eiscat.se:8000" assertion.
- declaration considerations "Decision on implementation depends on EISCAT_3D development. " assertion.
- declaration considerations "There's no metadata-data linking schema used. Metadata is usually part of the dataset (in case of Level 3 data in Madrigal the metadata is part of the HDF5 file, in the case of L1 and L2 data, metadata is part of the dataset download)." assertion.
- declaration considerations "Use has been evaluated in EUDAT prototype project. It is planned to come to use with EISCAT_3D data." assertion.
- declaration considerations "EISCAT is a PITHIA-NRF Node, metadata for EISCAT datasets will be registered and findable through the PITHIA-NRF e-science centre search engine." assertion.
- declaration considerations "This is a legacy system that will be merged with the EISCAT_3D data portal in the future. Implementation TBD." assertion.
- declaration considerations "Madrigal has served well for distributing analysed data from the legacy systems and will remain used for that purpose. However, it will not be used with EISCAT_3D data." assertion.