Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- 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 "Community relevant." assertion.
- declaration considerations "Datacite is used by the parts of ACTRIS that have implemented DOIs for their datasets." assertion.
- declaration considerations "Community relevant." 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 "The metadata of the ACTRIS metadata catalog is indexed in WMO Information System (WIS) and available through their search engine." 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 "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 "Community relevant." assertion.
- declaration considerations "OGC CS has been considered during Danubius-PP." assertion.
- declaration considerations "eduGAIN has been decided during Danubius-PP." assertion.
- declaration considerations "eduGAIN has been decided during Danubius-PP." assertion.
- declaration considerations "As specified in Data Policy." assertion.
- declaration considerations "According to DANUBIUS-PP" assertion.
- declaration considerations "Work in progress." assertion.
- declaration considerations "Work in progress." assertion.
- declaration considerations "Currently in use by the community of users." assertion.
- declaration considerations "Under consideration." assertion.
- declaration considerations "Work in progress." assertion.
- declaration considerations "Considered currently in the DMP and DP" assertion.
- declaration considerations "Considered currently in the DMP and DP" assertion.
- declaration considerations "Several options are considered. No final decision yet." assertion.
- declaration considerations "Analysed data inserted in Madrigal are also indexed by experiment in https://handle.eiscat.se" assertion.
- declaration considerations "DataCite metadata records are added when analysed results are converted from Matlab to HDF5 files." 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 "EISCAT is a member o the PITHIA Network of Research Facilities and PITHIA builds upon developments during the ESPAS FP7 project." assertion.
- declaration considerations "Compatibility with B2FIND" assertion.
- declaration considerations "Considered by ENVRI-FAIR" 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 "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 "A version of the EISCAT data download server which is an OIDC introspection enabled Checkin client has been developed." assertion.
- declaration considerations "An old de facto standard among incoherent scatter radars and other upper atmospheric instruments." assertion.
- declaration considerations "Used in EISCAT HDF5 archive format for Level 3 data (analysed physical parameters)" assertion.
- declaration considerations "De facto standard among legacy incoherent scatter radars" assertion.
- declaration considerations "Archived Level 3 (analysed) data have been converted to two new HDF5 based archive formats. This includes MADRIGAL version 3 which now uses a HDF5 format as standard." 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 "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 "No additional elements to report." assertion.
- declaration considerations "GeoNetwork, in use in the AnaEE France community. CKAN portal under development at the AnaEE EU level (https://data.anaee.eu/)." assertion.
- declaration considerations "Planned at least in the AnaEE France community." 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 "Not yet completed." assertion.
- declaration considerations "No additional elements to report." assertion.
- declaration considerations " NetCD files will be generated from the AnaEE semantic pipelines. First for data French platforms then extended to other AnaEE european platforms." assertion.
- declaration considerations "Initially used in the AnaEE France community." assertion.