hortus:workspace:overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hortus:workspace:overview [2026/04/07 10:22] – savino.frisardi | hortus:workspace:overview [2026/04/08 12:03] (current) – savino.frisardi | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== hortus: | + | ===== Why HORTUS is more than a generic cloud drive ===== |
| - | ===== Work in My Workspace | + | It is tempting to compare |
| - | Use this section when you need to: | ||
| - | * organise your personal working environment | ||
| - | * manage folders and documents | ||
| - | * share files with others | ||
| - | * work with versioned research materials | ||
| - | Main roles: | + | ^ Generic drive logic ^ HORTUS workspace logic ^ |
| - | * Signed-in users | + | | **Files and folders are usually the end point of the workflow.** | Files and folders are often an intermediate step inside a governed research-output lifecycle. | |
| - | * Contributors / Researchers | + | | **Metadata is often minimal or external to the storage layer.** | Metadata can be attached early and later reused |
| + | | **Sharing is the primary action.** | Sharing is important, but it sits alongside versioning, project context, public links, and publication. | | ||
| + | | **Project structure is usually manual and informal.** | Projects, resources, and workspace materials can be connected in a deliberate, research-oriented way. | | ||
| - | Related sections: | ||
| - | * [[hortus: | ||
| - | * [[hortus: | ||
| - | * [[hortus: | ||
| - | My Workspace is your **private working area** inside HORTUS. | ||
| - | |||
| - | My Workspace is where HORTUS becomes a daily working environment. It combines personal and shared storage, document creation, version-aware files, notifications, | ||
| - | {{: | ||
| - | ---- | ||
| - | |||
| - | ===== Why HORTUS is more than a generic cloud drive ===== | ||
| - | |||
| - | It is tempting to compare My Workspace with a generic storage tool such as Google Drive, but that comparison is incomplete. While it certainly stores files and folders, yet HORTUS also supports the Research Artifact Lifecycle natively: materials are organised, described, shared, versioned, | ||
| - | |||
| - | It provides: | ||
| - | |||
| - | * structured organisation of research materials | ||
| - | * sharing and permission control | ||
| - | * versioning of documents | ||
| - | * integration with publication workflows | ||
| - | * connection with metadata and dissemination | ||
| This makes it part of the **research lifecycle**, | This makes it part of the **research lifecycle**, | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== My Folders: entry point and layout ===== | ||
| - | |||
| - | Open My Workspace and use the left sidebar to enter My Folders. | ||
| - | The folder tree on the left helps you navigate, while the main panel shows the selected folder, its status, its actions, and the documents it contains. | ||
| - | This is the place to build an operational structure that reflects how your research actually unfolds. | ||
| - | |||
| - | {{: | ||
| - | |||
| - | ==== What you find here ==== | ||
| - | |||
| - | * folder structure | ||
| - | * stored documents | ||
| - | * navigation panel | ||
| - | * actions for creating and managing content | ||
| - | |||
| - | |||
| - | ====Folder management features==== | ||
| - | Here are | ||
| - | * Create a new top-level folder from the My Folders area when you need a new working container. | ||
| - | * Create a subfolder when the material belongs under an existing research stream or task. | ||
| - | * Edit a folder to improve the name or description once the research structure becomes clearer. | ||
| - | * Delete a folder only after checking that it is not a shared, active container still holding materials needed by others. | ||
| - | |||
| - | Sharing and permissions | ||
| - | |||
| - | Sharing is the bridge between personal organisation and real collaboration. Instead of emailing files around, invite people into the folder and assign an appropriate general access level. The screenshots show options such as Read Only, Write Own, and Write Any, which indicate a more structured permission model than a simple “shared/ | ||
| - | |||
| - | * Read Only: Users can view and download content but cannot make any changes. | ||
| - | * Write Own: Users can add and edit their own content but cannot modify or delete content created by others. | ||
| - | * Write Any: Users have full editing rights and can modify, delete, or manage all content in the shared space. | ||
| - | |||
| ---- | ---- | ||
hortus/workspace/overview.1775550143.txt.gz · Last modified: by savino.frisardi
