rd-alliance / metadata-directory Goto Github PK

Link: Home page

Associated standard: Unclear, but uses data from the Protein Data Bank. Therefore adding this use case is contingent on identifying the metadata scheme used by PDB.

Would there be an tracker that would work for the directory? snippet would then need to be added to appropriate templates.

The DDI entry in the catalogue should explain what DDI Codebook and DDI Lifecycle are. Associated entries should clarify which of the two is used (if applicable and known).

See: http://frictionlessdata.io/standards

Category: General Research Data

Link: Home page

Description: The PREMIS Data Dictionary for Preservation Metadata is the international standard for metadata to support the preservation of digital objects and ensure their long-term usability. Developed by an international team of experts, PREMIS is implemented in digital preservation projects around the world, and support for PREMIS is incorporated into a number of commercial and open-source digital preservation tools and systems. The PREMIS Editorial Committee coordinates revisions and implementation of the standard, which consists of the Data Dictionary, an XML schema, and supporting documentation.

(Originally considered out of scope for DCC DMC, now in scope for MSD.)

The GitHub README links to v2 at https://rdamsc.bath.ac.uk/ - but there is no link to that from https://rd-alliance.github.io/metadata-directory/ web content. So only someone trying to contribute might found out about v2.

Therefore new efforts like RDMKit continue to link to this instance of the directory (which perhaps is more edible, given that https://rdamsc.bath.ac.uk/scheme-index does not render any descriptions, unlike the nicer https://rd-alliance.github.io/metadata-directory/standards/)

I'm fine with this one being normative again - but then https://rdamsc.bath.ac.uk/ should point back here.

Category: Physical Science

Link: Website

Description: NeXus is an international standard for the storage and exchange of neutron, x-ray, and muon spin resonance data. The structure of NeXus files is extremely flexible, allowing the storage of both simple data sets, such as a single data array and its axes, and highly complex data and their associated metadata, such as measurements on a multi-component instrument or numerical simulations. NeXus has a simple API that allows the reading and writing of data in HDF or XML.

(While properly a data format, the NXentry-class groups "contain all the data that is required to describe an experimental run or scan" so this probably counts as metadata.)

Category: General Research

Links:

• Home page

Description: The Common European Research Information Format is the standard that the EU recommends to its member states for recording information about research activity. Since version 1.6 it has included specific support for recording metadata for datasets.

Sponsor: EuroCRIS

Tools: Current Research Information System software that uses CERIF includes

• Elsevier PURE
• Avedas CONVERIS
• Symplectic ELEMENTS

Use cases:

• OpenAIRE

GEOSS has compiled a registry of standards relevant to earth observations.

Tasks:

1. Identify standards/extensions from the GEOSS Standards Registry that are in scope but currently missing from MSD.
2. Either write original entries for those standards, or obtain permission from GEOSS to reuse their content.

The Allotrope Foundation is working on a new data format for chemistry data, the Allotrope Data Format (ADF). There was a presentation by Gerhard Noelken about it at the Royal Society of Chemistry on 20 October 2015.

It seems the format will include data description using RDF and a 'library of extensible taxonomies'.

The expected delivery of the complete format will be in November 2016.

Link: Home page

There is already a corresponding GBIF use case of EML that could be used as a basis for this one.

There is a newline after "description:" on line 33 and another at line 34. Some yaml-tools:

• yamllint 1.10.0 (https://yamllint.readthedocs.io/en/stable/) which uses PyYaml
• http://www.yamllint.com/
• https://codebeautify.org/yaml-validator

among them, considers this a syntax error.

Category: Physical Science

Link: Home page

Description: The Standard for Documentation of Astronomical Catalogues is a data and metadata format developed as an alternative to FITS.

Sponsor: Centre de Données astronomiques de Strasbourg (CDS)

Currently all the MI* standards are grouped under the MIBBI entry. MIBBI was a coordinating project (not a standard) and the MIBBI Portal that listed the MI* standards is deprecated in favour of the BioSharing catalogue. The MI* standards do however form a coherent family and some (all?) may be expressed in terms of MIBBI Foundry modules.

Options (in decreasing order of workload):

1. Replace the current MIBBI standard entry with the 40-ish MI* entries.
2. Replace the current MIBBI Portal extension entry with the 40-ish MI* entries as extensions of MIBBI rather than independent standards.
3. List the 40-ish MI* standards within the description of MIBBI.

These three profiles of ISO 19115 are among those used by SeaDataNet:

• Common Data Index (CDI)
• European Directory of Marine Environmental Research Projects (EDMERP)
• European Directory of the Ocean Observing Systems (EDIOS)

Many INSPIRE-compliant profiles of ISO 19115 are already included, but INSPIRE itself is missing.

(From a suggestion by Marion Wittenberg and Angus Whyte)

CLARIN normalises the metadata it holds using the Component Metadata Infrastructure (CMDI). This is really a wrapper around a metadata record, providing (among other things) explicit links/identifiers to the metadata profile used and the thing being described.

The profiles themselves are documented in the CLARIN Component Registry. The metamodel used in the registry is that a component corresponds to a thing, an element is a property of a thing, and components may be nested to show relationships between things. A profile is, in effect, a component that corresponds to a thing a CMDI record might describe. Elements should be linked to a description of their semantics.

There are profiles in the Component Registry for the following standards relevant for language resources:

• Dublin Core Terms (already included) and OLAC (Open Languages Archives Community)
• IMDI (ISLE Metadata Initiative) – Wikipedia has a list of use cases
• TEI (Text Encoding Initiative) headers
• Meta-Share maximal and minimal records
• MODS
• PARADISEC