Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "no consideration" assertion.
- declaration considerations "no consideration" 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. 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 "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 "The Data Management Plan is a living document. Proper training, resources need to be in place for " assertion.
- declaration considerations "How to maintain the standards and vocabularies? How to make it usable for different systems? " 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 "There are other alternatives and options out there (Cloudevents, distributed ledgers, other transactional systems). How to combine these?" assertion.
- declaration considerations "The DOIs are the best way to permanently identify a given digital object, in a format controlled by the International DOI Foundation. We have an agreement with DataCite and this will guarantee the cross-domain findability. When a DOI is not available, users can specify a persistent internal identifier." assertion.
- declaration considerations "We have an agreement with DataCite." assertion.
- declaration considerations "It represents the standard de facto as secure communication protocol." assertion.
- declaration considerations "Metadata records are freely accessible in the LifeWatch ERIC Metadata Catalogue, based on GeoNetwork, hence no login is required. The authentication and authorization are needed to add and manage metadata records and currently are performed by using a traditional login mechanism that identifies and authenticates users through the couple of credentials (username and password). It will adopt the SAML 2.0 protocol, with a multifactor authentication and is going to analyse the OAUTH infrastructure (analysis of providers, costs, issues, etc.)." assertion.
- declaration considerations "The knowledge representation languages used for datasets depend from the LifeWatch ERIC national node. Some examples are XMLS, CSV, DwC-A, NetCDF, etc." assertion.
- declaration considerations "The LifeWatch ERIC Metadata Catalogue actually allows to manually specify the thesaurus/vocabulary to be used for a given field (e.g., keyword, type, etc.) but in the future we plan to use drop-down and autocomplete lists for the semantic annotation of metadata fields and values by using semantic artifacts provided by the EcoPortal platform." assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The structured vocabularies used to encode datasets depend on the LifeWatch ERIC national node. " assertion.
- declaration considerations "The models, schemas used for datasets depend from the LifeWatch ERIC national node. Some examples are DwC-A, NetCDF, etc." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "A mixture between mostly CC-BY, CC-0 and CC-BY-NC is used, it depends on the LifeWatch ERIC national node." assertion.
- declaration considerations "The URI holds the historically assigned local incremental ID in the RDBMS. " assertion.
- declaration considerations "The URI holds the historically assigned UUID in the system." assertion.
- declaration considerations "Internally the metadata registry uses its own custom model that enables supporting multiple schemata, among which ISO 19115" assertion.
- declaration considerations "Data are added by users who require an account (uname and psswd). Data in private folders are not publically-accessible : if you click on a data link, you will get a message to that effect. Data in the public folders are accessible and a click on the link will start the download. Uses a custom SSO system called 'InovOcean-auth'" assertion.
- declaration considerations "Darwin Core is an extension of Dublin Core, and it used EML as its metadata. In addition, DwC-Archive data format incorporates particular vocabularies that are referenced to within the archive. " assertion.
- declaration considerations "For ecological data. In fact, the EML version (2.1) we currently use does not have full semantic annotation, but we are looking into adopting the version (2.2) that does introduce better support for that." assertion.
- declaration considerations "Supporting DCAT makes us align with growing use within the EU (as prescribed through the semic-eu DCAT-A -- https://github.com/SEMICeu/DCAT-AP" assertion.
- declaration considerations "Data format used by EurOBIS and EMODNet/Bio" assertion.
- declaration considerations "In some cases CC0 is concidered 'too open' - and since the academic context has a tendency for proper citation and attribution this step up is considered very mild." assertion.
- declaration considerations "under consideration" assertion.
- declaration considerations "Our data are ecological, so we use EML. There are fields in EML to accommodate provenance, and we are hoping that this can be expanded on in the near future" assertion.
- declaration considerations "To expand on the options we offer (albeit the amount of provenance included in the json export is quite sparse)" assertion.
- declaration considerations "metadata records have local identifiers either created locally or harvested through dif:entry_id or 'iso /gmd:MD_Metadata/gmd:fileIdentifier/gco:CharacterString'." assertion.
- declaration considerations "sios do not own data, but relies on partner repositories. UIDs is a requirement, PIDs (DOI) is a recommendation currently." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "This is used to indexed data locally and expose them on the data access portal. Filters and facets are based on elements of this schema." assertion.
- declaration considerations "Data are openly available" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "This is the recommended license, but support is in place for all CC licenses. " assertion.
- declaration considerations "The Argo data selection is a dedicated and specialized to our Argo community" assertion.
- declaration considerations "This is the Argo ERDDAP server.This API provides access to Argo data and metadata. https://www.ifremer.fr/erddap" assertion.
- declaration considerations "Argo DOI is indexed on Google, Bing, Seanoe, OpenSearch, google dataset search" assertion.
- declaration considerations "The data access is anonymous. The download statistics from https and ftp servers are analyzed without user identification." assertion.
- declaration considerations "The long term preservation of Argo dataset is shared by Ifremer and US-NCEI. Both sites preserve and mint regular DOIs of the whole dataset (monthly snapshots)" assertion.
- declaration considerations "The Argo DOI representation language is compliant with DataCite RDF schema and RDF Schema.org " assertion.
- declaration considerations "The Argo SPARQL endpoint allows interoperable and semantic queries on Essential Ocean Variables (NVS, CF) and well established vocabularies such as ORCID, FOAF, SOSA (sensors) or DCAT (catalogue of services)." assertion.
- declaration considerations "We use DataCite and Schema.org for Argo data and metadata DOI" assertion.
- declaration considerations "Argo data and metadata are distributed with a CC-By license" assertion.
- declaration considerations "The provenance information is recorded in Argo NetCDF implementation documented on http://dx.doi.org/10.13155/29825" assertion.
- declaration considerations "Standard in the community" assertion.
- declaration considerations "Standard in the community" assertion.
- declaration considerations "Recommended within ENVRI Atmospheric community" assertion.
- declaration considerations "Provided by Geonetwork server" assertion.
- declaration considerations "Community standard. Used for observed variables, instrument types and platform type" assertion.
- declaration considerations "Community standard" assertion.
- declaration considerations "Community standard" assertion.
- declaration considerations "Recommended in community" assertion.
- declaration considerations "Recommended in community" assertion.
- declaration considerations "Highly community relevant." assertion.
- declaration considerations "community relevant" assertion.
- declaration considerations "Generally relevant. Used for direct download of data." assertion.
- declaration considerations "Widely used in community." assertion.
- declaration considerations "Analysed data inserted in Madrigal are also indexed by experiment in https://handle.eiscat.se" assertion.
- declaration considerations "Use has been evaluated in EUDAT prototype project" 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 "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 "Use has been evaluated in EUDAT prototype project" 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 "Description was implemented as a prototype exercise in ENVRI." assertion.
- declaration considerations "DataCite metadata records are added when analysed results are converted from Matlab to HDF5 files." 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 "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 "De facto standard among legacy incoherent scatter radars" 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 "DataCite is the most used" assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "Datasets are provided in NetCDF files and text (CSV), available through https from portal and ERDDAP." assertion.
- declaration considerations "Harmonized metadata uses NERC Vocabulary Server (NVS)." assertion.
- declaration considerations "Provenance is currently being harmonized across EMSO ERIC regional facilities; however, the most common mechanism is currently via NetCDF." assertion.
- declaration considerations "EMSO ERIC uses a harmonized metadata schema based on OceanSites specifications, CF and other conventions. The final document is not publicly available yet. The schema is used through different mechanisms such as NetCDF (below) and ERDDAP." assertion.
- declaration considerations "DataCite is the most used" assertion.
- declaration considerations "Most of datasets are made publicly available; however, some functionalities requires authentication and authorization." assertion.
- declaration considerations "EMSO ERIC uses a harmonized metadata schema based on OceanSites specifications, CF and other conventions. The final document is not publicly available yet." assertion.
- declaration considerations "No specific constraints related to UUID use. Limitation is about the incomplete production of metadata records" assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "Non-systematic usage among platforms IS." assertion.
- declaration considerations "GeoNetwork, in use 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.