hortus:fair:metadata
This is an old revision of the document!
Understanding HORTUS metadata management
Core metadata: minimum required quality for every Marketplace resource
HORTUS already enforces some mandatory fields when creating a new Marketplace resource (First step of the catalogue resource creation: Define MAIN INFORMATION). The checklist below recommends a minimum quality bar for ITSERR-wide consistency.
| Field | Required in HORTUS? | ITSERR guideline | Notes / examples |
|---|---|---|---|
| Title | Yes | Mandatory | Use a descriptive title; avoid acronyms-only unless widely recognised. |
| Abstract / Description | Yes | Mandatory | 2–8 lines. Explain what it is, why it exists, and how to reuse it. |
| Publication location | Yes | Recommended | Use the real release/publication date (not only upload date). |
| Publication date | Yes | Mandatory | Use the real release/publication date (not only upload date). |
| Language | Yes | Recommended | Add all relevant languages (content language, transcription language, etc.). |
| Authors / Creators | Yes | Mandatory | Include contributors and, when relevant, corporate authorship. |
| License | Yes | Mandatory | Choose an explicit reuse license (e.g., CC BY, CC BY-SA) when possible. |
| Resource type | Yes | Mandatory | Choose from the agreed taxonomy (Publication, Dataset, Image, …). |
| Keywords | Yes | Mandatory | Use consistent vocabulary (discipline + method + corpus + geography/time). |
| Project link | Optional in UI | Strongly recommended | Link the resource to the correct Project/sub-project page. |
| Identifiers (DOI/URL) | Optional | Recommended | Add a DOI if it exists; otherwise, a stable URL/handle. |
Core fields checklist
hortus/fair/metadata.1775558381.txt.gz · Last modified: by savino.frisardi