| 1 | <?xml version="1.0" encoding="UTF-8" ?>
|
|---|
| 2 | <Elements>
|
|---|
| 3 | <!-- for now, only security related elements are available to add into the collection's config file
|
|---|
| 4 | using GLI's collection ConfigFileEditor that's available for GS3.
|
|---|
| 5 | See http://wiki.greenstone.org/doku.php?id=en:user:authentication
|
|---|
| 6 | and especially http://wiki.greenstone.org/doku.php?id=en:user_advanced:security
|
|---|
| 7 | -->
|
|---|
| 8 |
|
|---|
| 9 | <!-- Leave the elements in this file in this order for now.
|
|---|
| 10 | Code using this file (ConfigFileEditor.java) is dependent on ordering for ease of coding.
|
|---|
| 11 | -->
|
|---|
| 12 |
|
|---|
| 13 | <!-- element for hiding a collection -->
|
|---|
| 14 | <metadata name="public">false</metadata>
|
|---|
| 15 |
|
|---|
| 16 | <!-- element to make the entire collection private except for specified group(s) -->
|
|---|
| 17 | <security scope="collection" default_access="private">
|
|---|
| 18 | <exception>
|
|---|
| 19 | <group name="TYPE-GROUP-NAME-HERE"/>
|
|---|
| 20 | <!--<group name="KEEP-ADDING-ANOTHER-OF-THESE-TO-GIVE-ACCESS-TO-AN-ADDITIONAL-GROUP"/>-->
|
|---|
| 21 | </exception>
|
|---|
| 22 | </security>
|
|---|
| 23 |
|
|---|
| 24 | <!-- element to make all docs in collection private except for specified group(s).
|
|---|
| 25 | Can browse and search in collection, but docs found by browsing/searching can't be viewed -->
|
|---|
| 26 | <security scope="document" default_access="private">
|
|---|
| 27 | <exception>
|
|---|
| 28 | <group name="TYPE-GROUP-NAME-HERE"/>
|
|---|
| 29 | <!--<group name="KEEP-ADDING-ANOTHER-OF-THESE-TO-GIVE-ACCESS-TO-AN-ADDITIONAL-GROUP"/>-->
|
|---|
| 30 | </exception>
|
|---|
| 31 | </security>
|
|---|
| 32 |
|
|---|
| 33 | <!-- Make certain collection's docs private: except being some carefully defined set(s) of docs,
|
|---|
| 34 | which should then be made accessible only to the groups specified here as having access to
|
|---|
| 35 | those documentset(s).
|
|---|
| 36 | If different documentSets should be accessible to different groups, then define multipe
|
|---|
| 37 | <exception> elements here, each referencing the different docset(s) that exception pertains to.
|
|---|
| 38 | -->
|
|---|
| 39 | <security scope="document" default_access="public">
|
|---|
| 40 |
|
|---|
| 41 | <exception>
|
|---|
| 42 | <documentSet name="INVENT-A-RESTRICTED-DOCSET-NAME-HERE"/>
|
|---|
| 43 | <!--<documentSet name="CAN-HAVE-ADDITIONAL-DOCSETS"/>-->
|
|---|
| 44 | <group name="TYPE-GROUP-NAME-THAT-SHOULD-HAVE-ACCESS-TO-RESTRICTED-DOCSET(S)"/>
|
|---|
| 45 | <!--<group name="ADD-ANOTHER-OF-THESE-TO-GIVE-AN-ADDITIONAL-GROUP-ACCESS-TO-THE-SAME-DOCSET(S)"/>-->
|
|---|
| 46 | </exception>
|
|---|
| 47 |
|
|---|
| 48 | <documentSet name="REPEAT-INVENTED-RESTRICTED-DOCSET-NAME-HERE">
|
|---|
| 49 | <match type="match" field="TYPE-HERE-THE-METADATA-FIELD-NAME-WHOSE-VALUE-SHOULD-MATCH">TYPE-HERE-THE-METADATA-VALUE-THAT-SHOULD-EXACTLY-MATCH</match>
|
|---|
| 50 | <!--<match type="regex" field="TYPE-METADATA-FIELD-NAME">TYPE-HERE-THE-SO-CALLED-REGEX-PATTERN-THAT-THE-METADATA-VALUE-SHOULD-MATCH</match>-->
|
|---|
| 51 | <!--<match>TYPE-THE-DOC-IDENTIFIER-OF-RESTRICTED-DOC-HERE</match>-->
|
|---|
| 52 |
|
|---|
| 53 | <!--ADD AS MANY <match> elements as you like to define this documentSet-->
|
|---|
| 54 |
|
|---|
| 55 | </documentSet>
|
|---|
| 56 | </security>
|
|---|
| 57 |
|
|---|
| 58 | </Elements>
|
|---|
