hortus:workspace:documents
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hortus:workspace:documents [2026/04/07 10:41] – savino.frisardi | hortus:workspace:documents [2026/04/08 12:08] (current) – savino.frisardi | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| Use Create Document when you want your document to be more than a loose file. The wizard lets you attach metadata and references from the start. Depending on the route you choose, you may work from a GROBID-assisted path, a manual path, a multiple-upload path, or a DOI/ | Use Create Document when you want your document to be more than a loose file. The wizard lets you attach metadata and references from the start. Depending on the route you choose, you may work from a GROBID-assisted path, a manual path, a multiple-upload path, or a DOI/ | ||
| - | To create a document: | ||
| - | * open a folder | ||
| - | * use the creation action | ||
| - | * upload or create content | ||
| - | Documents can represent: | ||
| - | |||
| - | * research drafts | ||
| - | * datasets | ||
| - | * working files | ||
| - | * materials for publication | ||
| {{: | {{: | ||
| + | ^ Wizard stage ^ What you do there ^ Why it matters ^ | ||
| + | | **Entry point / source choice** | Choose how the document should be created or ingested. | The path determines how much metadata can be extracted automatically. | | ||
| + | | **Metadata selection** | Choose the metadata structure that will describe the document. | This supports later discovery, reuse, and publication. | | ||
| + | | **Metadata input** | Complete the required descriptive fields. | The document becomes a better research object rather than a generic file. | | ||
| + | | **Success state** | Finish the wizard and confirm the created document. | The item can then be opened, shared, discussed, versioned, or later published. | | ||
| + | |||
| ---- | ---- | ||
| - | ===== Document detail page ===== | + | ===== Document detail page and version control===== |
| Each document has a structured detail page. | Each document has a structured detail page. | ||
| Line 43: | Line 39: | ||
| * version history | * version history | ||
| * actions (share, edit, delete) | * actions (share, edit, delete) | ||
| + | |||
| + | The detail page is where the document stops behaving like a simple file and starts behaving like a managed research object. The detail page collects the Overview, Metadata, Documents, Discussions, | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ^ Document detail action ^ Typical use ^ Outcome ^ | ||
| + | | **Upload new version** | When the document has changed but should remain the same evolving object. | A new version is added while previous ones remain part of the record. | | ||
| + | | **Create public link / get URL** | When you need a stable shareable pointer rather than a manual navigation explanation. | The platform generates a link you can copy and reuse. | | ||
| + | | **Open Discussions** | When the document itself needs contextual comments or clarifications. | Discussion remains attached to the object instead of becoming detached email traffic. | | ||
| + | | **Open References** | When you want to keep external or related references in one place. | The document stays connected to its scholarly context. | | ||
| ---- | ---- | ||
| Line 57: | Line 63: | ||
| * support collaborative editing | * support collaborative editing | ||
| - | ---- | + | {{: |
| ==== Best practices ==== | ==== Best practices ==== | ||
| Line 64: | Line 71: | ||
| * keep meaningful version notes | * keep meaningful version notes | ||
| * avoid unnecessary versions | * avoid unnecessary versions | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Workspace and publication ===== | ||
| - | |||
| - | My Workspace is often the starting point for publication. | ||
| - | |||
| - | Typical workflow: | ||
| - | |||
| - | * create or upload document | ||
| - | * organise in folders | ||
| - | * enrich with metadata | ||
| - | * prepare for submission | ||
| - | * publish through Marketplace or Projects | ||
| - | |||
| - | This connects Workspace to the **publication lifecycle**. | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Practical usage scenarios ===== | ||
| - | |||
| - | ==== Individual work ==== | ||
| - | |||
| - | * store drafts | ||
| - | * organise research materials | ||
| - | * prepare content before publication | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Collaboration ==== | ||
| - | |||
| - | * share folders with team members | ||
| - | * co-manage documents | ||
| - | * coordinate research outputs | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Publication preparation ==== | ||
| - | |||
| - | * collect files and metadata | ||
| - | * prepare structured outputs | ||
| - | * submit to Marketplace | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Best practices ===== | ||
| - | |||
| - | * organise folders logically | ||
| - | * use clear naming conventions | ||
| - | * manage permissions carefully | ||
| - | * keep documents updated | ||
| - | * integrate workspace with publication workflows | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Summary ===== | ||
| - | |||
| - | My Workspace is: | ||
| - | |||
| - | * a structured research environment | ||
| - | * a collaboration tool | ||
| - | * a preparation area for publication | ||
| - | |||
| - | It supports: | ||
| - | |||
| - | * organisation | ||
| - | * sharing | ||
| - | * versioning | ||
| - | * integration with HORTUS workflows | ||
| ---- | ---- | ||
hortus/workspace/documents.1775551283.txt.gz · Last modified: by savino.frisardi