Scope for Custom Metadata

This feature request is a part of the Calendar Revision.

1 Initial Problem

Global Custom Metadata are visible for all types of assigned objects throuout ILIAS even if they are only needed in specific categories.

2 Conceptual Summary

Administrators can set specific scopes for Custom Metadata. Scopes can be defined for the location in the repository by selecting one or multiple container objects (course, categories etc.).

• If objects are moved in other categories without this metadata set, the respective metadata set is not shown not are the values that were entered. 
• If objects are moved back to a category with metadata set, info screen shows metadata again: the metadata were not removed just hidden.
• If objects potentially carrying the metadata set is moved into a part of the tree where this metadata set is applicable then the metadata set will be shown according to the settings in the administration. There will be no values because they have never been entered.

3 User Interface Modifications

3.1 List of Affected Views

• Administration > Metadata > Datasets > Form shown after Action: Edit 
• Administration > Metadata > Datasets
• Administration > Didactic Templates  > Table 

3.2 User Interface Details

"Edit Data Set"-Form gets a new option to limit the scope of application of custom metadata sets to certain sub-trees.
This is to be modeled after the identical workflow in Administration > Didactical Templates > Action:  Settings.

The table "Custom Metadata Sets" get another column "Scope" which shows scope of this custom metadata set. 

We feel the need to establish this as a pattern and thus suggest to amend the table "Available didactic Templates", too: 

• Add "Scope"-Coulmn to this table to show that this templeate has a limited scope. 

3.3 New User Interface Concepts

If available, the new Repository Selector should be used here.

4 Technical Information

The search engine will not be able to respect the activation / deactivation of Custom Metadata. 

5 Contact

• Author of the Request: Seiler, Yvonne [yvseiler], Amstutz, Timon [amstutz]
• 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

Kunkel, Matthias [mkunkel], MAR 201, 2017: I support this request. But I would like to have a revised UI element for select / reset the scope in the form. The current presentation of one link below the other is not the very best. Does the new repository selector offer a better solution? And will it come for 5.3?

Amstutz, Timon [amstutz], MAR 23, 2017: The revised UI-Element linked above is part of an other project. If this project fails to implement this new componant, we are heavily interested to support it. We are also interested in collaboratively revising the currently incomplete proposal JF ready. However for this we would need help from a maintainer making heavy use of it (such as alex). 

JourFixe, ILIAS [jourfixe], March 27, 2017: We highly appreciate this suggestion and schedule it for 5.3.

8 Implementation

Test Cases

Test cases completed on 2017-08-10 by Tödt, Alexandra [atoedt]

• 18622: Gültigkeitsbereich für benutzerdefinierte Metadatensätze festlegen
• 18623: Kurs mit in ihrem Gültigkeitsbereich beschränkten Metadaten versehen 
• 18630: Metafizierten Kurs ausserhalb des Gültigkeitsbereiches verschieben

Approval

Approved at 11. August 2017 by Amstutz, Timon [amstutz].