Autocompleted tag search and assignment

1 Initial Problem

In the context of the workshops and discussions about the Category for Huge Amount of Data we proposed the necessity of an auto-completed tag search and tag assignment both as addition to the tag cloud and as optional replacement (and it was agreed upon that this needs its own feature wiki entry).

We think that the tag cloud alone will not scale with a large number of tags. And we think that both the proposed Concept for Learning Communities and the utiliazation of so called subject headings authority files (German: Schlagwortnormdateien) will quite quickly lead to a larger number of tags. In our opinion the latter is especially interesting when building OER repositories with ILIAS; also see Import of Subject Headings Authority Files. Subject headings authority files ususally contain several hundred thousand (!) entries …

2 Conceptual Summary

We propose to base the ILIAS implementation on what has been proven to work on tag-based sites like eg. Pinboard, a bookmark service (similar to what Delicious once was) that uses tags (and tag groups) to organise huge numbers of booksmarks. The following GIF shows the Pinboard autocomplete implementation employed in the search, it works similarly in the GUI for creating bookmarks, though:

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, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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.

• Universität Stuttgart

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