Show Advanced KnowledgeHide Advanced Knowledge

Improved Re-Use of Existing Keywords

1 Initial Problem

Re-using existing keywords in a blog is not well supported. At the time being, all already used keywords are presented below the keyword input form, see screenshot below. But you have to type every existing keyword into to the input again - instead of just clicking on one of them.

2 Conceptual Summary

The screen for adding and removing keywords should allow to add other keywords (that exists already in the blog) easily by clicking on them. This will add them immediatelly to the list of already assigned keywords. Additionally, the already assigned keywords should also be presented as tags but with an additional 'x' for deletion - like known from the Long Menu question type. To distinguish easily between assigned and other keywords, I recommend to assign a different CSS class to the other keywords (not assigned yet), e.g. presenting them in grey.

3 User Interface Modifications

3.1 List of Affected Views

Existing screens:

• Blog » blog posting » Edit keywords (Screen-ID: copg/pg/)

New screens:

• none

3.2 User Interface Details

Modified UI elements:

• tag UI element:
  • supports click action to be added to existing list of keywords
• keyword input element:
  • only offering to be added (no remove action)

Added UI elements:

• removable tag UI element (as known from Long Menu question)

Removed UI elements:

• multiple input UI element (or adding and removing assigned keywords)

For arrangement of UI elements and new or changed text representation, please see screenshot.

3.3 New User Interface Concepts

No completely new user interface elements will be introduces. But it would be highly appreciated if the used UI elements could be transformed into the centralised UI framework.

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: Kunkel, Matthias [mkunkel]
• Maintainer: Killing, Alexander [alex]
• 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.

• ILIAS-Verein

7 Discussion

ILIAS_LM 2016-03-31
I can affirm the need of this feature by my clients.

Amstutz, Timon [amstutz] 2016-05-20: Stackoverflow and many other popular sites use a "Tag-Input" for this behaviour (selecting Tabs of a given Set). In ILIAS we also make use of a library servicing this need (Tag-Input with typeahead in Tag-Input KS Pipeline). Currently the Tag-Input in ILIAS is only used to select from an exsiting set, but we could also think about extending that to add new values with the same input.

Kunkel, Matthias [mkunkel], Oct 12, 2016: I have updated this feature request and adapted it to the new page structure. Screenshot and requested description are added to chap. 2.

Kruse, Fabian [Fabian], 13.10.2016: I support this request. I would consider removing one or two of the bylines, as the concept is pretty self-explaining. (I find myself clicking on the tags all the time until I remember that this won’t actually do anything.)

Related: When the tag list is very long, it can be annoying to search for an entry. So an auto-complete for the text-entry field could also be helpful. What do you think?

Mela, Alix [ILIAS_LM] 2016-10-13
@Kruse, Fabian [Fabian]:
Yes, autocomplete, like WordPress!
+1

Killing, Alexander [alex], 31 Mar 2017: I support the general request. But I think having forms in the UI would be some kind of precondition. And then the implementation of the input element would not necessarily fall under my maintenance.

Kunkel, Matthias [mkunkel], April 04, 2017: Product manager supports request.

Seiler, Yvonne [yvseiler], April 04, 2017: I've made some mockups, how it could look like with the Tag-Input (see comment of Timon Amstutz above).

• Adding a keyword could be possible with "Enter" (our prefered command) or "Semicolon" and "Comma" too (all three options are possible).
• Mockup 1-3: Our prefered solution (other keywords are listed in dropdown).
• Mockup 4-5: If "Other keywords" shall be visible as "bubbles", the keyword which was clicked should be automatically insert into the input field and should disappear in the list "Other keywords".
• Mockup 6-7: Proposal if "Other keywords" should be categorised (lots of keywords) in "Popular tags" and "All tags". Needs a decision about when a keyword gets the "Popular" state.

JourFixe, ILIAS [jourfixe], April 10, 2017: We highly appreciate this suggestion and schedule it for 5.3. A general Kitchen Sink implementation for TagInput could probably implemented by Studer+Raimann and added to the Kitchen Sink. Such a general UI element would then be re-used  by Alexander for the current request.

Bogen, Christian [bogen], May 31, 2017: It seems I’ve created a (semi-)duplicate: Autocompleted tag search and assignment :)

Kunkel, Matthias [mkunkel], August 24, 2017: Due to missing manpower for implementing the new UI element we have to postpone this feature to 5.4. New Release Status is 'Suggested for 5.4'.

JourFixe, ILIAS [jourfixe], September 11, 2017: We still want to have this feature in ILIAS. But we wait for a final version of the TagInput that could be re-used in the blog. The discussion about this UI element is still ongoing.

JourFixe, ILIAS [jourfixe], 18 DEC 2017: We highly appreciate this request and schedule it for 5.4. The necessary TagInput UI element is now available, see above.

8 Implementation

Test Cases

Test cases completed at 29 OCT by Zenzen, Enrico [ezenzen]

• C1925: Einen Blogbeitrag mit Schlagwörter versehen
• C24959: Wiederverwenden von Schlagwörtern

Approval

Approved at 17 OCT 2018 by Kunkel, Matthias [mkunkel]