Differences

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

--- hortus:fair:creation [2026/04/07 14:13] – savino.frisardi
+++ hortus:fair:creation [2026/04/07 14:18] (current) – savino.frisardi
@@ Line 51: / Line 51: @@
 | **Revise a rejected format** | If the format is Rejected, it remains visible to you and returns as a draft when you required to edit it. After you will be able to submit it again when ready. | Rejection does not block the workflow permanently; it supports improvement and quality control. |
 | **Use an approved format** | Once approved, the metadata format becomes reusable in Metadata Management and is available when describing Marketplace resources. | Approval turns your custom format into a stable template that can support repeated, consistent metadata entry. |
+|**Select the approved format in Marketplace**| When creating or editing a Marketplace resource, go to Step 3 – Metadata management, choose the metadata type (Standard, Personal, or Community), select the approved format, and fill in its fields.| This is where the metadata format becomes operational and starts structuring real resource descriptions.|
 ----
-===== Metadata lifecycle =====
+**Metadata format lifecycle**
-Metadata formats also follow a lifecycle:
+^ Status ^ What it means ^ What you can do next ^
+| **Draft** | The metadata format has been created and saved, but not yet submitted for moderation. | View it, edit it, and improve it before submission. |
-  * Draft → creation phase
+| **Waiting for approval** | The metadata format has been sent to moderation and is awaiting review. | Track its status and wait for moderator action. |
-  * Submitted → under review
+| **Approved** | The metadata format has passed moderation and is now reusable in Metadata Management and Marketplace workflows. | Select it when creating or editing Marketplace resources. |
-  * Approved → reusable
+| **Rejected** | The metadata format was reviewed but not accepted in its current form. | Revise the draft and resubmit it when ready. |
-  * Updated → versioned changes
 ----
-===== Good practices =====
+**Good practices**
-  * use clear field definitions
+^ Good practice ^ What it means ^ Why it matters ^
-  * avoid redundancy
+| **Check existing formats before creating a new one** | Search, sort, and inspect available metadata formats before starting from scratch. | This reduces duplication and encourages consistency across the platform. |
-  * use controlled vocabularies where possible
+| **Use duplication when possible** | Start from an existing metadata format and adapt it instead of rebuilding everything manually. | It saves time and keeps your format closer to accepted standards. |
-  * ensure consistency across records
+| **Write clear field names and descriptions** | Make each field understandable for future users. | A readable format is easier to reuse and less likely to generate inconsistent data. |
+| **Use controlled vocabularies where useful** | Restrict certain fields to predefined values instead of free text. | This improves data quality, comparability, and later filtering. |
+| **Preview before saving** | Review all field definitions and datatypes before storing the format as a draft. | This helps catch mistakes early and reduces unnecessary revisions later. |
 ----