General metadata vocabularies
Cross-disciplinary controlled values used to describe research resources, contributors, dates, identifiers, languages and technical formats consistently.
This resource provides practical guidance on selecting and recording standardised values for metadata fields shared across research domains, repositories and catalogue systems.
Using established vocabularies reduces ambiguity, supports automated validation and improves the exchange of metadata between repositories, DOI services, catalogues and research infrastructures.
Resource information
Resource type: Controlled vocabulary reference
Vocabulary level: General and cross-disciplinary metadata
Primary audience: Researchers, data stewards, repository managers, metadata specialists and software developers
Primary uses: Dataset description, repository deposit, DOI registration, metadata validation and catalogue exchange
Main sources: DataCite, COAR, DCMI, CRediT, ORCID, ROR, IETF, ISO and IANA
Last reviewed: July 2026
Purpose and scope
General metadata vocabularies define standard values for properties that occur across disciplines and types of research output.
They help repositories and researchers use the same meaning for concepts such as dataset, software, data curator, collection date, translated title, personal name, organisation and file format.
These vocabularies provide the cross-disciplinary layer of a metadata record. More detailed scientific concepts should be supplied through domain-specific vocabularies and ontologies.
Important: always use the vocabulary required by the destination metadata profile. A repository may use one vocabulary internally and map its values to another vocabulary during export.
General vocabulary families
Resource description
Resource types, title types, description types and other values describing the nature and content of a research output.
People and organisations
Name types, contributor roles and identifier schemes for researchers, organisations and research contributors.
Dates and locations
Typed dates, language tags, country codes and other standardised geographic or temporal values.
Technical description
File formats, media types, identifier types and values used to describe technical representations.
Main vocabulary sources
| Vocabulary or registry | Primary coverage | Typical implementation |
|---|---|---|
| DataCite controlled lists | Resource types, contributor types, title types, date types, description types and identifier types | DOI metadata and repository application profiles |
| COAR Resource Types | Detailed and hierarchical types of repository resources | Institutional repositories, aggregators and catalogue mappings |
| DCMI Type Vocabulary | High-level cross-domain categories for the nature of a resource | Dublin Core and general-purpose metadata |
| CRediT | Roles describing contributions to the production of a research output | Contribution statements, publications and research records |
| ORCID | Persistent identification of individual researchers | Creator and contributor metadata |
| ROR | Persistent identification of research and funding organisations | Affiliations, publishers, funders and hosting institutions |
| IETF BCP 47 | Language tags | Language of titles, descriptions, names and resource content |
| ISO 3166 | Countries and principal subdivisions | Geographic coverage, addresses and organisational locations |
| IANA Media Types | Standard Internet media types | Technical format of files and distributions |
Resource types
DataCite uses a broad controlled value in
resourceTypeGeneral and permits a more specific free-text
value in resourceType.
General type: identifies the broad category required for DataCite metadata.
Specific type: provides a narrower repository or domain description.
Example: general type Dataset and specific
type Molecular dynamics simulation dataset.
| Group | DataCite resourceTypeGeneral values |
|---|---|
| Data and representations | Dataset, Collection, Image, Sound, Audiovisual, Model, PhysicalObject |
| Publications and documents | Book, BookChapter, Journal, JournalArticle, ConferencePaper, ConferenceProceeding, DataPaper, Dissertation, Preprint, Report, Standard, Text |
| Computational resources | ComputationalNotebook, Software, Workflow, InteractiveResource, Service |
| Research infrastructure and processes | Instrument, StudyRegistration, OutputManagementPlan, Project, Award, Event |
| Scholarly communication | PeerReview, Poster, Presentation |
| Fallback | Other |
COAR Resource Types
COAR Resource Types should be used when a repository or aggregator needs a more detailed and hierarchically organised description than the broad DataCite categories provide.
Example general type: dataset
Example publication type: journal article
Example report subtype: data management plan
Example computational type: workflow
Representation: persistent concept URI plus a multilingual label
| Research object | DataCite general type | COAR type |
|---|---|---|
| Research dataset | Dataset |
http://purl.org/coar/resource_type/c_ddb1
|
| Software package | Software |
http://purl.org/coar/resource_type/c_5ce6
|
| Journal article | JournalArticle |
http://purl.org/coar/resource_type/c_6501
|
Title types
The main title is recorded without a title type. Additional titles should use a controlled value explaining their function.
| DataCite value | When to use it |
|---|---|
AlternativeTitle |
Another recognised name or title for the same resource. |
Subtitle |
A subordinate title extending or clarifying the main title. |
TranslatedTitle |
A translation of the main title into another language. |
Other |
A title type not represented by the available controlled values. |
{
"titles": [
{
"title": "Metadata profile for research datasets",
"lang": "en"
},
{
"title": "Профіль метаданих дослідницьких датасетів",
"titleType": "TranslatedTitle",
"lang": "uk"
}
]
}
Description types
| DataCite value | Purpose |
|---|---|
Abstract |
A concise explanation of the resource, its purpose and content. |
Methods |
Information about collection, generation, processing or analysis. |
TableOfContents |
A structured or textual overview of the resource contents. |
TechnicalInfo |
Software, file, instrument or technical-use information. |
SeriesInformation |
Legacy description of series information; structured RelatedItem metadata is preferred where applicable. |
Other |
Additional information not represented by another description type. |
Contributor roles
DataCite contributor types identify how a person or organisation is associated with the described resource.
| Role group | DataCite values |
|---|---|
| Data support | DataCollector, DataCurator, DataManager |
| Research and production | Researcher, Producer, Editor, Translator, Supervisor |
| Project roles | ProjectLeader, ProjectManager, ProjectMember, WorkPackageLeader |
| Contact and related people | ContactPerson, RelatedPerson |
| Organisations and infrastructure | Distributor, HostingInstitution, RegistrationAgency, RegistrationAuthority, ResearchGroup, RightsHolder, Sponsor |
| Fallback | Other |
CRediT contributor roles
CRediT describes the specific activities through which an individual contributed to producing a research output.
Conceptualization · Data curation · Formal analysis · Funding acquisition · Investigation · Methodology · Project administration · Resources · Software · Supervision · Validation · Visualization · Writing – original draft · Writing – review and editing
| Aspect | DataCite contributorType | CRediT |
|---|---|---|
| Primary purpose | Describes the contributor's relationship to the registered resource. | Describes the activities performed during production of the work. |
| Organisations | Includes institutional and infrastructure roles. | Primarily intended to describe individual contributions. |
| Example | DataCurator |
Data curation |
| Implementation | DataCite DOI metadata | Contribution statement or additional structured metadata |
Names and identifier schemes
| Entity | Recommended identifier | Example use |
|---|---|---|
| Individual researcher | ORCID iD | Creator, contributor or contact person |
| Research organisation | ROR ID | Affiliation, publisher, funder or hosting institution |
| Research output | DOI | Dataset, software, report, workflow or publication |
| Research activity or project | RAiD | Project or research activity linked to an output |
| Archived software source | SWHID | Specific archived software object |
| Physical sample | IGSN | Sample or specimen used to produce data |
| Research resource | RRID | Instrument, facility, organism, antibody or other resource |
Date types
| DataCite value | Meaning in a metadata record |
|---|---|
Created |
Date when the resource was created. |
Collected |
Date or period during which data were collected. |
Coverage |
Temporal period represented by the resource. |
Submitted |
Date when the resource was submitted. |
Accepted |
Date when the resource was accepted. |
Issued |
Date of formal publication or issue. |
Available |
Date when the resource became or will become available. |
Updated |
Date of a modification or update. |
Valid |
Period during which the resource or information is valid. |
Copyrighted |
Date when copyright was established. |
Withdrawn |
Date when the resource was withdrawn. |
Other |
Another typed date, clarified through additional information. |
Language tags
Use a standard language tag instead of entering the language name as unrestricted text.
Ukrainian: uk
English: en
British English: en-GB
German: de
Traditional Chinese: zh-Hant
Use the shortest adequate tag: use en
unless a regional or script distinction is important.
Do not translate the code: use uk, not
ua, for the Ukrainian language.
Separate language from country: language
uk and country UA represent different
concepts.
Country codes
Use ISO 3166 codes for countries and territories when the metadata profile requires a controlled geographic value.
| Country | Alpha-2 | Alpha-3 |
|---|---|---|
| Ukraine | UA |
UKR |
| Germany | DE |
DEU |
| Finland | FI |
FIN |
File formats and media types
Record the machine-readable media type separately from a filename extension and, where useful, from the human-readable format name.
| Format | Filename extension | IANA media type |
|---|---|---|
| Comma-separated values | .csv |
text/csv |
| JSON | .json |
application/json |
.pdf |
application/pdf |
|
| PNG image | .png |
image/png |
| TIFF image | .tif or .tiff |
image/tiff |
| ZIP archive | .zip |
application/zip |
Format name: useful for human-readable documentation.
Extension: identifies the conventional filename suffix but is not a complete format identifier.
Media type: supports machine processing and content negotiation.
Format version: should be recorded separately when compatibility depends on a specific release.
How to record a controlled value
Where the metadata system supports structured values, record more than the displayed label.
{
"value": "dataset",
"conceptUri": "http://purl.org/coar/resource_type/c_ddb1",
"vocabulary": "COAR Resource Types",
"vocabularyVersion": "3.2",
"language": "en"
}
Value: preferred human-readable label.
Concept URI: stable identifier of the concept.
Vocabulary: name of the source vocabulary.
Vocabulary version: release used by the record.
Language: language of the displayed label.
Example of controlled values in a metadata record
{
"resourceType": {
"resourceTypeGeneral": "Dataset",
"resourceType": "Computational materials dataset",
"coarType": {
"label": "dataset",
"uri": "http://purl.org/coar/resource_type/c_ddb1"
}
},
"titles": [
{
"title": "Example computational dataset",
"lang": "en"
},
{
"title": "Приклад обчислювального датасета",
"titleType": "TranslatedTitle",
"lang": "uk"
}
],
"contributors": [
{
"name": "Example Researcher",
"nameType": "Personal",
"contributorType": "DataCurator",
"nameIdentifier": {
"scheme": "ORCID",
"uri": "https://orcid.org/0000-0002-1825-0097"
},
"creditRoles": [
"Data curation",
"Validation"
]
}
],
"affiliation": {
"name": "Example Research Institution",
"identifierScheme": "ROR",
"identifier": "https://ror.org/example"
},
"dates": [
{
"date": "2026-07-01",
"dateType": "Created"
},
{
"date": "2026-07-20",
"dateType": "Issued"
}
],
"language": "en",
"country": "UA",
"formats": [
{
"formatName": "Comma-separated values",
"fileExtension": ".csv",
"mediaType": "text/csv"
},
{
"formatName": "JSON",
"fileExtension": ".json",
"mediaType": "application/json"
}
]
}
How to select a general metadata vocabulary
1. Identify the field
Determine whether the value describes a resource, contributor, date, identifier, language, country or technical format.
2. Check requirements
Review the metadata profile and destination repository for a required vocabulary or code list.
3. Select the concept
Choose the most precise valid value without using a narrower term than the available evidence supports.
4. Preserve provenance
Store the vocabulary name, concept identifier and version where the system permits.
Mapping between general vocabularies
A local repository may need to translate the same value into several external representations.
| Local concept | DataCite | COAR | DCMI |
|---|---|---|---|
| Research dataset | Dataset |
http://purl.org/coar/resource_type/c_ddb1
|
http://purl.org/dc/dcmitype/Dataset
|
| Software | Software |
http://purl.org/coar/resource_type/c_5ce6
|
http://purl.org/dc/dcmitype/Software
|
| Image | Image |
Selected COAR image subtype |
http://purl.org/dc/dcmitype/Image
|
Validation rules
Value validation
Check that the supplied code or term belongs to the required controlled list.
Identifier validation
Check identifier syntax, scheme name and resolvability where appropriate.
Context validation
Confirm that the value is valid for the metadata property in which it is used.
Mapping validation
Verify that exported values preserve the intended meaning in the destination profile.
Common implementation errors
Using a filename extension as the complete format description: the technical representation remains ambiguous.
Using a country code as a language code:
UA represents Ukraine, while uk represents
Ukrainian.
Using only a displayed organisation name: changes, translations and similarly named organisations cannot be disambiguated.
Using CRediT as a replacement for DataCite contributorType: contribution activities and metadata relationships are different concepts.
Choosing Other too early: a suitable controlled value may already exist.
Combining several values in one string: individual terms cannot be validated or indexed.
Recording a label without its vocabulary: the source and meaning of the value become unclear.
Ignoring vocabulary versions: later changes cannot be traced reliably.
How to use this resource
1. Find the property
Identify the metadata field for which a standard value is required.
2. Select the source
Use the vocabulary prescribed by DataCite, the repository or the destination catalogue.
3. Record structured values
Preserve codes, identifiers, labels and vocabulary information in separate fields.
4. Validate the export
Check how the value appears in DataCite, OAI-PMH, catalogue and machine-readable web metadata.