Publishing Plugin Content as OER

1 Initial Problem

Currently, which object types are harvested and published as OER by the OER Harvester (and with what metadata) is controlled solely by the MetaData component. This makes it impossible to make use of the existing infrastructure to publish content from non-standard ILIAS components.

2 Conceptual Summary

The MetaData component should offer an interface to other components so that they can register more object types to be harvested.

That interface should also allow appending the download links published with objects, such that not only standard export files can be published, but also content in a platform-agnostic format. This would also allow in the future e.g. standard ILIAS Learning Modules to be published along with HTML exports, or Files with their actual files.

3 User Interface Modifications

3.1 List of Affected Views

No changes to the UI.

3.2 User Interface Details

-

3.3 New User Interface Concepts

-

3.4 Accessibility Implications

-

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

The implementation of this feature should make use of the new component mechanism to collect implementations of an interface supplied by MetaData.

4.3 Privacy

If other components choose to include download links to files potentially containing personal data in the publishing, they should note that in their respective privacy documentation.

4.4 Security

No foreseeable security implications.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Schmitz, Tim [tschmitz]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.