Difference between revisions of "Administration"

From reBiND Documentation
Jump to: navigation, search
(→‎Administration)
(→‎Administration)
Line 5: Line 5:
 
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.
 
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.
  
−
So in order to upload the data document for a new data project, a new collection for the data project has to be created. This can be easily done via the web interface of the eXist server. The Content Administrator needs to login in order to see the admin dashboard of the eXist server, where such an option is available. The collection should have a clear descriptive name, but must only contain small letters (without special characters), digits, underscores or dashes. Within this collection the data document and meta data document can then be uploaded, also via the admin dashboard. Additional files could also uploaded in the collection, like the original data file, the data was extracted from in order to generate the XML document or images and other multimedia objects. For the sake of clarity image and multimedia objects should be placed into special subcollections within the data project collection, like ''images/''. A data project could also contain more than one XML data document, however only one meta data file.
+
In structions 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 would therefore look like this:
+
The collection structure of eXist, showing the unpublished and published project collections is shown below:
 
<pre>
 
<pre>
 
/db/
 
/db/

Revision as of 18:14, 21 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.

In structions 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
             └─ ...
Retrieved from "https://wiki.bgbm.org/rebind_documentation/index.php?title=Administration&oldid=219"