Option for querying other ILIAS installations / repositories / referatories

1 Initial Problem

Once ILIAS installations can provide metadata (for example for objects with a cc license) for external inquiries (see Metadata interface for querying by referatories), other ILIAS installations should also be able to enlist the metadata for these objects within the search engine.

Sobald es möglich ist, dass ILIAS-Installationen Metadaten (für z.B. Objekte unter einer CC-Lizenz) für externe Abfragen (z.B. von Bildungsservern) bereit stellen können, sollten auch andere ILIAS-Installationen in der Lage sein, die Metadaten für diese Objekte in der Suche anzuzeigen.

2 Conceptual Summary

The metadata originated from external sources are being made available through a daily working Cronjob within the Lucene search engine. One can adapt the settings in the administration towards which ILIAS installation should be retrieved. Further repositories or referatories shall be clearly identified by the specifications mentioned. For reasons of performance it is expedient to always read only new or slightly changed metadata and to update the search engine accordingly.
Furthermore, there should be restrictions when reading metadata from other sources. This way, one can select according to certain subjects, cc licenses or status.

Über einen in der Regel täglich abzuarbeitenden Cronjob stehen die aus externen Quellen stammenden Metadaten in der (Lucene-)Suche zur Verfügung. In der Administration kann eingestellt werden, welche ILIAS-Installationen abgefragt werden sollen. Auch weitere Repositorien oder Referatorien sollen unter Angabe verwendeter Spezifikationen angegeben werden können. Aus Performanzgründen ist es sinnvoll, stets nur neue oder veränderte Metadaten einlesen zu können und die Suche entsprechend zu aktualisieren.
Ferner sollen beim Einlesen von Metadaten anderer Quellen Einschränkungen möglich sein. So muss nach bestimmten Fachgebieten, CC-Lizenzen oder Status selektiert werden könnnen.

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

Tödt, Alexandra [atoedt] 2022-10-05: Please provide a mock-up how this could be presented in the search result list. How are permissions and offline status dealt with? What happens if users click on a search result? Is she taken to that installation? What is presented at the path? 

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