Custom Metadata: Grouping metadata fields (tuple)

1 Initial Problem

At the moment it is not possible to group metadata fields. This can become a problem when the metadata comes in “tuples” or in arrays of “tuples”, eg. in case of the CampusConnect course lecturer(s):

"lecturers": { "type":"array", "items": { "type":"object", "properties": { "firstName": {"type":"string"}, "lastName": {"type":"string"}

(Source: https://github.com/freeit/ecs/blob/master/campusconnect/schemas/cc_courses.schema.json)

In this case we can have several lectureres for a course, all with first and lastname. Searchable eg. in the Category for Huge Amount of Data should be something like “lecturer“ (as one “fuzzy“ field), of course.

2 Conceptual Summary

We do not have clear and ready solution for how to solve this in ILIAS. It might either be an option to groups incoming metadata fields during import, so that the lectures first and last name are saved in one (array) field of a metadata field called lecturer. Or a solution could emerge via the possiblity to “virtually” group metadata fields in the custom metadata presentation subtab.

We are asking the maintainer for input on this and hope that a viable solution will emerge.

(We want to stress, though, that the solution should be “compatible” with Custom Metadata: Array handling.)

3 User Interface Modifications

3.1 List of Affected Views

Tbd.

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

• …

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