Show Advanced KnowledgeHide Advanced Knowledge

Import option / interface for metadata

1 Initial Problem

Metadata are to be partially used even according to LOM standards, if there is no mutual convention regarding the issue of developing subject areas or keyword-lists. There are currently agreements on a European level concerning the specific development of metadata, which have been „broken down“ on a national level (i.e. LOM-de; LOM-es). These standards would have to be undertaken within ILIAS.

Metadaten sind auch nach LOM-Standard nur bedingt zu gebrauchen wenn keine gemeinsame Konvention darüber existiert, wie z.B. eine Sachgebietszuordnung oder Schlagworte ausgestaltet werden könnten. Es gibt nun z.B. auch auf europäischer Ebene Vereinbarungen zur konkreten Ausgestaltung von Metadaten, die auf nationale Ebene ‚heruntergebrochen‘ wurden (Bsp.: LOM-de; LOM-es). Diese Standards müssten in ILIAS übernommen werden können.

2 Conceptual Summary

The concept sets forth that a source can be indicated for a metadata specification through the administration. Once activated, this source can be called upon repeatedly in determined time frames. In case of changes where previously existing subject areas are no longer available, the affected ILIAS objects will be presented with their metadata (integrity check upon updated specifications).
When absorbing the source, the entry forms for metadata may automatically change: free-text fields will transform into selection fields (facilitating the entry); mandatory fields will be highlighted.

Das Konzept sieht vor, dass über die Administration eine Quelle für eine Metadaten-Spezifikation angeben werden kann. Bei Aktivierung wird diese Quelle in festzulegenden Zeitabschnitten wiederholt abgerufen. Sollten sich Änderungen derart ergeben, dass zuvor in der Quelle vorhandene Sachgebiete nicht mehr existieren, werden die betroffenen ILIAS-Objekte mit ihren Metadaten angezeigt (Integritätsprüfung bei aktualisierten Spezifikationen).
Mit der Übernahme der Quelle ändern sich auch Eingabemasken für Metadaten: Freitextfelder werden teils zu Auswahlfeldern (Erleichterung der Eingabe);
Pflichtfelder werden deutlich gekennzeichnet.

Dates to be Supported

The following categories should be supported (whitelist):

• …

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: Kohnle, Uwe [ukohnle]
• 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

Metadata Workshop, July 19, 2017: We discussed Uwe's suggestion at our workshop in Stuttgart and support this requirement. We would like to support

• the import of defined vocabularies / thesauries on installation level as json-objects or xml files (files could be updated via cron-job).
• the use of such defined dates in the metadata administration of each object as autocomplete suggestions for text entry fields (Example: we do not want two fields for 'Keywords', one for text entry another as selection list, but only one input with autocomplete that looks up for existing terms)

Additionally, the metadata administration of ILIAS needs to support the customization of the 'Quick Edit' screen in the Metadata tab which should be tackled in a distinct feature request. This would allow to promote specific but important metadata and increase their use. This requires a whitelist for the metadata that should be supported.

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