Abandon Multiple Definitions per Term in Glossary

1 Reasons to Abandon Feature

Being able to add mutiple definitions to one term adds inordinate amounts of complexity. Especially the current "Definitions" editing screen is quite strange and unique. Additionally the 1:n relation makes the code and DB structure complex.

We consider these cases (multiple definions for a term) very rare and it is easy to work around this:

• Users can create the same terms more than once instead.
• Migration: If terms had multiple definitions they will be split up into mutliple terms with same title.

2 Technical Information

No technical issues. Code will become much simpler in several places.

3 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

4 Funding

Removing the feature from the ILIAS code base might need funding. If you are interest in funding this request, please add your name and institution to this list.

• ...

5 Discussion

Use the following discussion section to express your objections against this request or your consent to get rid of this feature.

JourFixe, ILIAS [jourfixe], 13 JUN 2022 : We follow the suggestion of the maintainer and abandon the feature to have multiple definitions per term in the glossary with ILIAS 9.

Killing, Alexander [alex], 10 Aug 2022: Definitions currently support LOM metadata. My assumption is, that this is rarely used. Since the definition entities will be "removed" and all data will be attached to the terms internally, we need to decide if the LOM metadata of definitions can be abandoned or needs to be migrated to terms.

6 Implementation

Implemented as described above.

Removed Testcases

There was no test case related to the abandonned feature. Thus no test case was deleted. 

Approval

Approved at 2023-02-02 by Tödt, Alexandra [atoedt]