Page History
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Introduction
With DSpace you can describe digital objects such as text files, audio, video or data to facilitate easy retrieval and high quality search results. These descriptions are organized into metadata fields that each have a specific designation. For example: dc.title stores the title of an object, while dc.subject is reserved for subject keywords.
...
The DSpace Submission forms, defined in the inputsubmission-forms.xml file, allows the inclusion of value pairs that can be organized in lists in order to populate dropdowns or other multiple choice elements. If you explore the default inputsubmission-forms.xml file, you can see that a number of such value pair lists are already pre defined.
...
DSpace uses the simple choice management to provide a controlled list of language tags. Out of the box DSpace comes with a list of ISO language tags. You can add further language lists or use the provided one to let submitters tag languages of metadata fields. Take a look at the part of this documentation about the configuration of the Submission User Interface. This feature is currently supported in JSPUI only.
Hierarchical Taxonomies and Controlled Vocabularies
The value pairs system works well for short and flat lists of choices. DSpace offers a second way of structuring and managing more complex, hierarchical controlled vocabularies. In contrast to the value pairs system, these controlled vocabularies are managed in separate XML files in the [dspace]/config/controlled-vocabularies/ directory instead of being entered straight into inputsubmission-forms.xml
The taxonomies are described in XML according to this structure:
...
You are free to use any application you want to create your controlled vocabularies. A simple text editor should be enough for small projects. Bigger projects will require more complex tools. You may use Protegé to create your taxonomies, save them as OWL and then use a XML Stylesheet (XSLT) to transform your documents to the appropriate format. Future enhancements to this add-on should make it compatible with standard schemas such as OWL or RDF.
Default Hierarchical Controlled Vocabularies
By default, DSpace includes two out-of-the-box hierarchical controlled vocabularies in the [dspace]/config/controlled-vocabularies/ directory.
- nsi - nsi.xml - The Norwegian Science Index (in the Norweigen language)
- srsc - srsc.xml - Swedish Research Subject Categories (in the English language, with notes in Swedish)
You may create your own hierarchical controlled vocabulary by using either of those as a model. All valid hierarchical vocabularies should align with the "controlledvocabulary.xsd" schedule available in that same directory.
Enabling / Disabling a Hierarchical Controlled Vocabulary
To enable a hierarchical controlled vocabulary, simply configure it's usage in one (or more) of your fields in your "submission-forms.xml" (as documented below).
To disable a hierarchical controlled vocabulary, simply remove it from all your fields in your "submission-forms.xml". You can also disable all controlled vocabularies by commenting out the "DSpaceControlledVocabulary" plugin in "authority.cfg":
| Code Block | ||
|---|---|---|
| ||
plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = \
org.dspace.content.authority.DCInputAuthority, \
org.dspace.content.authority.DSpaceControlledVocabulary |
How to invoke a controlled vocabulary from
...
submission-forms.xml
Vocabularies need to be associated with the correspondent DC metadata fields. Edit the file [dspace]/config/inputsubmission-forms.xml and place a "vocabulary" tag under the "field" element that you want to control. Set value of the "vocabulary" element to the name of the file that contains the vocabulary, leaving out the extension (the add-on will only load files with extension "*.xml"). For example:
...
The vocabulary element has an optional boolean attribute closed that can be used to force input only with the Javascript of controlled-vocabulary add-on. The default behaviour (i.e. without this attribute) is closed="false". This allows the user to enter values as free text in addition to selecting them from the controlled vocabulary.
The following vocabularies are currently available by default:
...
.
...
Authority Control: Enhancing DSpace metadata fields with Authority Keys
...
The fact that this functionality deals with external sources of authority makes it inherently different from the functionality for controlled vocabularies. Another difference is that the authority control is asserted everywhere metadata values are changed, including unattended/batch submission, SWORD package submission, and the administrative UI.
How it looks in the DSpace user interface
The difference between an authority controlled metadata field and a non-authority controlled metadata field can be seen in the Edit interface for an accepted item.
This example shows a value for an author name that has been linked with an authority key. The green thumb represents the associated confidence value "Accepted": This authority value has been confirmed as accurate by an interactive user or authoritative policy.
How it works
TODO
Original source:
...
Overview
Content Tools