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:20] – savino.frisardi | hortus:publish:contributions [2026/04/07 12:30] (current) – savino.frisardi | ||
|---|---|---|---|
| Line 37: | Line 37: | ||
| - | IMMAGINE | + | {{: |
| ---- | ---- | ||
| Line 51: | Line 51: | ||
| - | ==== What it manages | + | ====How to read the lifecycle panels==== |
| - | * drafts | + | For each contribution type, My Contributions uses a dashboard logic based on three main panels. |
| - | * submitted items | + | |
| - | * approved content | + | |
| - | * rejected items | + | |
| - | * published outputs | + | |
| - | ---- | + | ^ Panel ^ What it shows ^ Why it matters ^ |
| + | | **Left panel** | Items to be sent to moderation or items in the moderation queue. This area is especially relevant for authorised moderators or users with review rights. | It identifies the contributions that still need a decision step before they can move forward. | | ||
| + | | **Middle panel** | Your draft items. These are contributions you started but have not yet submitted. | It helps you return to unfinished work and continue refining it before sending it into the review workflow. | | ||
| + | | **Right panel** | My items — your own submitted or tracked contributions. | It helps you monitor what you already created and whether those items are waiting for approval, accepted, or otherwise progressing through the lifecycle. | | ||
| - | ==== Why this matters ==== | ||
| - | * centralised control of your work | + | In the Projects area, My Contributions includes two additional boxes that are not simply about publication |
| - | * visibility of lifecycle | + | |
| - | * easier management of revisions | + | |
| - | ---- | + | ^ Additional project box ^ What it shows ^ Why it matters ^ |
| + | | **Requests to join** | Requests you submitted to join a project. | Helps you see whether a membership request is still pending or has already been processed. | | ||
| + | | **My invitations** | Invitations you received to join projects. | Helps you follow collaboration opportunities that other project leaders sent to you. | | ||
| - | ==== Structure ==== | ||
| - | Items are usually organised by: | + | These extra project boxes make the Projects contribution area especially rich, because it combines both publication tracking and community participation tracking. It shows that projects in HORTUS |
| - | * type (resource, project, event, metadata) | ||
| - | * status (draft, pending, approved, published) | ||
| - | ---- | + | ====Typical lifecycle logic==== |
| - | ==== How to read lifecycle | + | A simple way to understand My Contributions is to read it as a lifecycle |
| - | Each item shows: | + | ^ 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. | | ||
| - | * current status | + | 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. |
| - | * required actions (if any) | + | |
| - | * history | + | |
| - | ---- | + | ====Why this feature is important for researchers==== |
| - | ==== Typical lifecycle logic ==== | + | For scholars, My Contributions is particularly reassuring because it makes platform workflows transparent. |
| - | * Create item → Draft | + | Instead of seeing HORTUS as a place where content disappears into a black box after submission, users can see that contributions follow clear stages |
| - | * Submit → Pending | + | |
| - | * Review → Approved / Rejected | + | |
| - | * If approved → Published | + | |
| - | * If rejected → revise | + | |
| - | ---- | + | In practical terms, My Contributions helps a young researcher to: |
| + | * resume unfinished work without losing track of it | ||
| + | * know whether a submitted item is still pending | ||
| + | * understand when a contribution needs attention | ||
| + | * follow project-related collaboration signals | ||
| + | * experience HORTUS as a platform with visible, governed, and structured research workflows | ||
| - | ===== 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.1775557207.txt.gz · Last modified: by savino.frisardi
