Metadata Database for Metadata Suggestions

1 Initial Problem

In Metadata section (for any object) Keywords are entered manually and this can create typos and / or simply who inserts the keyworks might not remember what to enter.

2 Conceptual Summary

It should be possibe to have a database/catalogue with all the desired keywords. The administrators could create a list of the keywords so that the editors - when adding a keyword - receive a suggestion (like a search) of the possible keyworks. In this way the editors can make controlled choices for the keywords.

3 User Interface Modifications

3.1 List of Affected Views

• Metadata » Quick Edit
• Administration » Metadata

3.2 User Interface Details

{ needs to be completed }

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 Privacy Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Truppa, Ilario [ilario.truppa]
• Maintainer:  Meyer, Stefan [smeyer]
  
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• This Feature Request has been suspended by final customer. It will be updated when we receive new information.

9 Discussion

Killing, Alexander [alex], 8 Nov 2020: I added Stefan as the maintainer. The feature requests currently lacks a lot of specification, so I think it is not Jour Fixe ready. Mainly we need a specification of the screens that should manage the keywords in the administration. But also the implications on the regular keyword editing screen need additional specification. Would we use additional dropdowns, autocomplete or other means to enter the data?

Truppa, Ilario [ilario.truppa], 23 Nov 2020: We added a video in order to explain where to insert this new function suggesting also how it should work. Hope it is clear enough. We wait for your feedback.

Kunkel, Matthias [mkunkel], 29 APR 2021 : The general idea of providing a defined vocabulary of keywords that can easily be reused is very good and highly appreciated by the Product Manager. We could even think about a setting that does only allow the usage of keywords from a defined list and not to add them manually.
But I am not sure if the reuse of the data collection component is a good idea. A form like known from the Custom Metadata editing would almost be sufficient. What really could be of great value is an import of a list of keywords as text file to avoid entering a couple of keywords by hand.

10 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}.