hortus:publish:contributions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hortus:publish:contributions [2026/04/07 12:25] – savino.frisardi | hortus:publish:contributions [2026/04/07 12:30] (current) – savino.frisardi | ||
|---|---|---|---|
| Line 37: | Line 37: | ||
| - | IMMAGINE | + | {{: |
| ---- | ---- | ||
| Line 72: | Line 72: | ||
| ====Typical lifecycle logic==== | ====Typical lifecycle logic==== | ||
| + | |||
| + | A simple way to understand My Contributions is to read it as a lifecycle monitor. | ||
| + | |||
| + | ^ Lifecycle stage ^ What it usually means in My Contributions ^ | ||
| + | | **Draft** | You created the item, but it is still a work in progress and not yet fully submitted. | | ||
| + | | **Waiting for approval / waiting for moderation** | You submitted the item, and it is now waiting for a moderator or authorised reviewer to take a decision. | | ||
| + | | **Approved** | The contribution has passed the review stage and can move into the next functional state of the platform. | | ||
| + | | **Rejected** | The contribution was not accepted in its current form and may need revision before resubmission. | | ||
| + | |||
| + | This lifecycle visibility is one of the strongest aspects of the feature. It gives the researcher a concrete understanding of how research data and entities evolve inside HORTUS. | ||
| ====Why this feature is important for researchers==== | ====Why this feature is important for researchers==== | ||
| Line 87: | Line 97: | ||
| - | ==== What it manages ==== | ||
| - | * drafts | ||
| - | * submitted items | ||
| - | * approved content | ||
| - | * rejected items | ||
| - | * published outputs | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Why this matters ==== | ||
| - | |||
| - | * centralised control of your work | ||
| - | * visibility of lifecycle status | ||
| - | * easier management of revisions | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Structure ==== | ||
| - | |||
| - | Items are usually organised by: | ||
| - | |||
| - | * type (resource, project, event, metadata) | ||
| - | * status (draft, pending, approved, published) | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== How to read lifecycle panels ==== | ||
| - | |||
| - | Each item shows: | ||
| - | |||
| - | * current status | ||
| - | * required actions (if any) | ||
| - | * history of changes | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Typical lifecycle logic ==== | ||
| - | |||
| - | * Create item → Draft | ||
| - | * Submit → Pending | ||
| - | * Review → Approved / Rejected | ||
| - | * If approved → Published | ||
| - | * If rejected → revise and resubmit | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Moderation workflow ===== | ||
| - | |||
| - | Moderation is a core feature of HORTUS. | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== What moderators check ==== | ||
| - | |||
| - | * content quality | ||
| - | * metadata completeness | ||
| - | * permissions | ||
| - | * consistency | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Outcomes ==== | ||
| - | |||
| - | * Approved → item progresses | ||
| - | * Rejected → revisions required | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Implications for users ==== | ||
| - | |||
| - | * publication is not immediate | ||
| - | * quality standards must be met | ||
| - | * iteration may be required | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Best practices for publishing ===== | ||
| - | |||
| - | * complete all metadata fields | ||
| - | * use clear and accurate descriptions | ||
| - | * attach relevant files | ||
| - | * verify permissions before submission | ||
| - | * review content before submitting | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Summary ===== | ||
| - | |||
| - | Publishing in HORTUS is: | ||
| - | |||
| - | * structured | ||
| - | * moderated | ||
| - | * metadata-driven | ||
| - | |||
| - | Users can: | ||
| - | |||
| - | * create multiple types of content | ||
| - | * track their lifecycle | ||
| - | * improve quality through review | ||
| - | * disseminate research outputs effectively | ||
| - | |||
| - | ---- | ||
hortus/publish/contributions.1775557538.txt.gz · Last modified: by savino.frisardi
