...
Metadata refers to the contextual information about a resource (e.g. a dataset), often described as “data about data”. This mMetadata Metadata can come in many different types and forms. Perhaps t The type of metadata you might be most familiar with is the generic descriptive metadata often collected from in repositories (e.g., such as Zenodo (see the example of how zenodo describes the resources on its repository). This generic metadata includes details about on what the resource is about (e.g., data from patient health records), who created it (e.g., a research team at Radboudumc) and when it was collected (e.g., 2023). Typically, it also discloses information about the possible uses of the resource (e.g., applicable licensing) and access restrictions (e.g., available for public use/restricted access). There are other Other types of metadata , below a non-exhaustive listcommonly used are:
Provenance metadata: This refers to how the resource came to be, what protocols were followed, and what tools were used. The purpose of this metadata is to ensure that you, your colleagues or others can reproduce the initial research.
Content Structural metadata: Depending on the type of resource, this refers to a detailed description of your resource that goes beyond the generic information explained above. For instance, in the context of a dataset containing data collected from a questionnaire, content metadata could include the questions asked and the allowed range of values.
Codebooks: A detailed document that provides information about the structure, content, and organization of a dataset. A codebook usually describes information such as variable names, and measurement methods and units.
In this step, the focus will be on assessing the availability of your metadata. This involves identifying and collecting all types of metadata being gathered about your resource. Check their quality and ensure they are as accurate and complete as possible. Depending on your objectives <point towards FAIR objectives>, this step is a good starting point . Whether you aim to simply gain a clear view of what metadata currently describes your resource, expand your current metadata, ensure compliance with requirements to publish it in a metadata catalogue <Point to Register resource level metadata> or follow a semantic model to describe your metadata; this step is common across multiple purposes.In this step, the focus will be on assessing the availability of your metadata. This step is a good starting point and a common first step for multiple objectives <point towards FAIR objectives>, whether you aim to:
gain a clear view of what metadata currently describes your resource
expand your current metadata
ensure compliance with requirements to publish it in a metadata catalogue <Point to Register resource level metadata>
follow a semantic model to describe your metadata
This step involves identifying and collecting all types of metadata gathered for your resource, checking their quality and ensuring they are as accurate and complete as possible.
Metadata is data about data. It comes in many types, such as descriptive metadata, provenance metadata, etc [cb_metadata]. Metadata helps people to locate the data and allows it to be reused and cited [GoFAIR]. Furthermore, metadata can be machine-actionable, allowing for automation of data handling and validation [RDMKit_MachineActionable]. Findability, accessibility and reusability of data can be improved by providing metadata with details about license, copyright, etc., as well as description of use conditions and access of data [Generic].
Maybe more how to:
Check whether metadata regarding regarding findability, accessibility, and reusability is already available and whether this metadata is already being collected using standardized vocabularies [Generic, FAIRopoly]. What metadata should be gathered may depend on the stakeholder community [Generic].
[FAIRopoly] Identify what metadata is already being collected by your registry (e.g., provenance, creation date, file type and size, timestamp). The result of this step will support defining the metadata model of your registry. Also, check if your metadata is already being collected using standardized vocabularies.
Why is this step important
...