Custom Metadata: (Better) support for controlled vocabularies / import of subject headings authority files

1 Initial Problem

We would like to see the possibility to base custom metadata (keyword/tag) fields on authority files to both help users with the input and to control the used vocabulary. 

This would for example be helpful when using ILIAS as a kind of OER repository (somethings University of Stuttgart is pondering in the context of a new edition of the Library of Labs (LiLA)) as “folksonomies” are generally undesirable in a scenario like this—and many others.

Means to underly the actual authority file with a kind of “thesaurus” to help users find the correct “translations” of their “own” keywords to the ones from the authority files seem like a good idea, too.

2 Conceptual Summary

As we do not have final concept already, we ask for the maintainers help on this.

Some notes:

• It should be either possible to maintain a keyword (and “thesauraus“) list in directly ILIAS or …
• It should be possible to import (and update) contents from an authority file
• The choice between the two cases has to be made when creating the MD field
• The possibility to switch between the two cases afterwards seems unnecessary
• An autocomplete mechanism (for users) such as it already has been described in Autocompleted tag search and assignment in the context of the Category for Huge Amount of Data seems desirable

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Bogen, Christian [bogen]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.