Difference between revisions of "Administration"
LornaMorris (talk | contribs) (→User management) |
LornaMorris (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | ==Administration== | + | ===Administration=== |
An XML document can be uploaded to the eXist database even if the document is not valid according to the schema used. However it is mandatory that the document is well formed, otherwise errors will occur when trying to store the document. | An XML document can be uploaded to the eXist database even if the document is not valid according to the schema used. However it is mandatory that the document is well formed, otherwise errors will occur when trying to store the document. | ||
| Line 47: | Line 47: | ||
In the above example the 'contributing scientist' is allocated to the group 'users', so the /db/unpublished/ directory within the eXist database should be made accessible to the group 'users'. | In the above example the 'contributing scientist' is allocated to the group 'users', so the /db/unpublished/ directory within the eXist database should be made accessible to the group 'users'. | ||
| + | ===Correction Manager=== | ||
==[[Correction Modules]]== | ==[[Correction Modules]]== | ||
Revision as of 18:59, 29 October 2014
Administration
An XML document can be uploaded to the eXist database even if the document is not valid according to the schema used. However it is mandatory that the document is well formed, otherwise errors will occur when trying to store the document.
But before the documents can be stored, a closer look at the collection structure within eXist is needed. The reBiND Framework depends on two collections for managing the different data projects. One of the collections is for the unpublished data projects, which are still being corrected, reviewed or otherwise prepared for publication. The other collection is for the published projects, which can be publicly searched and accessed. Within this document they will be referred to as unpublished and published. Both of these collections are located in the root collection of eXist. Within these collections are the collection for the individual data projects. Having the two collections for unpublished and published data projects makes the security configuration also quite easy, since the security settings for these two collections are automatically inherited by data projects within these.
Instructions on how to create projects via the reBiND user interface have been desctibed in the [Data_upload_to_rebind_framework data archiving section].
The collection structure of eXist, showing the unpublished and published project collections is shown below:
/db/
├─ (eXist default)
├─ unpublished/
│ ├─ (data-project-name 1)/
│ │ ├─ data.xml
│ │ ├─ metadata.xml
│ │ ├─ original-data.xls
│ │ └─ images/
│ │ ├─ image_001.jpg
│ │ ├─ image_002.jpg
│ │ └─ ...
│ └─ (data-project-name 2)/
│ └─ ...
└─ published/
└─ (data-project-name 3)/
├─ data.xml
├─ metadata.xml
├─ original-data.xls
├─ images/
│ ├─ image_001.jpg
│ ├─ image_002.jpg
│ └─ ...
└─ multimedia/
├─ movie1.mov
├─ movie2.avi
└─ ...
The majority of the database administration can be done through the eXist Java webstart client. For example, the client can be used to add new user accounts, modify permissions to different database collections and delete/edit/query the data.
User management
Users can be created via the eXist Java admin client. For example creating a new user for the contributing scientist is shown in the screenshot below.
In the above example the 'contributing scientist' is allocated to the group 'users', so the /db/unpublished/ directory within the eXist database should be made accessible to the group 'users'.
Correction Manager
Correction Modules
- Writing Custom Correction Modules (How to modify the correction configuration file)
- Using a different XML format
- Using a different metadata format (Discussion of different Metadata standards)
