Differences

This shows you the differences between two versions of the page.

--- hortus:fair:metadata [2026/04/07 13:57] – savino.frisardi
+++ hortus:fair:metadata [2026/04/08 12:27] (current) – savino.frisardi
@@ Line 5: / Line 5: @@
 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.
+**Core fields checklist**
 ^ Field ^ Required in HORTUS? ^ ITSERR guideline ^ Notes / examples ^
@@ Line 18: / Line 19: @@
 | **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**
 ----
@@ Line 26: / Line 27: @@
 Metadata formats (also called metadata sets) define which fields appear when you describe a resource. In HORTUS they are organised in three governance levels:
-  * Standard metadata: common reference formats intended for the whole platform. They promote interoperability and consistent indexing.
+  * **Standard metadata**: common reference formats intended for the whole platform. They promote interoperability and consistent indexing.
-  * Community metadata: formats shared publicly by users with the community. They can capture discipline-specific needs (e.g., manuscript description) without necessarily becoming platform-wide standards.
+  * **Community metadata**: formats shared publicly by users with the community. They can capture discipline-specific needs (e.g., manuscript description) without necessarily becoming platform-wide standards.
-  * Personal metadata: formats you create for your own needs (private). Personal formats can combine standard/community fields with project-specific additions.
+  * **Personal metadata**: formats you create for your own needs (private). Personal formats can combine standard/community fields with project-specific additions.
 ----
@@ Line 60: / Line 61: @@
-IMMAGINE
+{{:hortus:fair:exampleresource.jpg?600|}}
 ----
@@ Line 79: / Line 80: @@
-**Pre-defined object types in HORTUS**
+==== Pre-defined object types in HORTUS  ====
+**Standard metadata sets**
-*Standard metadata sets*
 HORTUS includes a first group of Standard metadata sets that are designed for interoperability with well-known external platforms and infrastructures. These formats provide a stable “common language” for describing resources in a way that can be more easily mapped, exported, or re-used outside HORTUS (e.g., when depositing or aligning records with external catalogues). The initial standard formats include Zenodo, SSHOC, and CLARIN VLO. This list is not fixed: additional standard sets can be introduced over time, but to preserve consistency and trust, new standard formats are added through a moderated process, typically based on community needs and technical feasibility.
-*Community metadata sets*
+**Community metadata sets**
 In addition to standards, HORTUS foresees Community metadata sets that provide practical templates aligned with the types of resources commonly managed in the platform. These formats are intended to support discipline-oriented or project-oriented practices, offering field structures that are meaningful for researchers while still encouraging consistency across the community. The initial set includes a Generic template and dedicated community templates for major resource categories: Publications, Datasets, Images (2D), Audio and video, 3D models, and Software/tools. Like object types, this collection is expandable: HORTUS users can propose new community metadata sets (or improvements to existing ones), and the moderator board reviews and approves them to keep the catalogue coherent and avoid fragmented or incompatible formats.