Document management
This guide explains the document hierarchy and the basic data management actions.
Dataspace
The user is always working within the dataspace. A dataspace consists of two applications:
- the end-user application
- the administration application which only administration users have access to
This guide provides the end-user perspective; see Administration guides for the administrator perspective.
Document hierarchy
The basic structure of resources in an application is analogous to the file system, but built using RDF resources and relationships between them instead. There is a hierarchy of containers (folders), which are collections of items (files) as well as sub-containers (sub-folders). Both containers and items are documents. Items cannot contain other documents.
The first level of resources in a container is referred to as its children (of which that container is the parent, while all levels down the hierarchy are collectively referred to as descendants.
When a user logs in, the application loads its root container (unless a specific URI was requested). From there, users can navigate down the resource hierarchy, starting with children of the root container. At any moment there is only one current document per page, on which actions can be performed: it can be viewed, edited etc.
Manage documents
The following actions can also be performed using the command line interface.
| Action | Description | CLI script |
|---|---|---|
| Create | Create a new child document by clicking the Create button on the left of the navbar | create-container.sh create-item.sh |
| Edit | Open the current document editing form by clicking the Edit button in the middle section of the navbar bar | put.sh |
| Delete | Delete the current document by clicking the Delete in the action bar (the right section of the navbar) | delete.sh |