Feature Wiki

Information about planned and released features

Tabs

Publish as OER-Button for Objects

1 Initial Problem

Currently, the publishing of OER from ILIAS can only be initiated implicitely by choosing an appropriate copyright licence. This is less than intuitive for authors of learning content.

Additionally, authors might not always be aware that choosing a licence leads to their content being published. On the 'Metadata'-tab of objects one is at least warned about this (with an easily ignorable modal), but if the licence is e.g. chosen on creation of File objects there is no such indication at all.

2 Conceptual Summary

There should be an explicit 'Publish as OER'-button on the LOM Digest of objects, which shows their publishing status and offers related actions.

Manual publishing should be compatible to the OER Harvester, but they should be considered mutually exclusive. It should be easy to switch between the two options, but there is no need to specially consider the user experience for the case where both are used in parallel.

Maybe: only fully automated publishing for the OER Harvester, no editorial step?

3 User Interface Modifications

3.1 List of Affected Views

  • Metadata > LOM in repository objects
  • Administration > System Settings and Maintenance > General Settings > Cron Jobs > OER Harvester > Edit
  • Administration > Search and Find > Metadata > Copyright & OER > Publishing (new subtab)

3.2 User Interface Details

All the settings of the OER Harvester should be moved to a new subtab 'Publishing' in the LOM Administration, along with a 'Enable manual publishing' checkbox.

Better label for checkbox? Maybe also move the OAI-PMH settings there?

Mock ups!

If enabled in the Administration, the LOM Digest screen of eligible objects (i.e. harvestable by the OER Harvester) should offer a 'Publish as OER'-button. This button opens a modal showing the publishing status of the object, and context-dependent actions.

  • Unpublished: Not yet entered into the publishing workflow.
    • Action Submit for Review: links the object in the Harvesting-Category, creates a public access export (exactly like the harvesting-part of the OER Harvester). Deactivated if an invalid copyright is selected.
  • Under Review: The object has been submitted for review, but is not yet published via the OAI-PMH interface.
    • Action Publish: Compiles the object's LOM set for the OAI-PMH interface (exactly like the publishing-part of the OER Harvester), moves the object to the Publishing-Category.
    • Action Reject: Deletes the object from the Harvesting-Category, the object has again the status Unpublished. Only offered in the Harvesting-Category.
    • Action Withdraw: Same as Reject, but only offered outside the Harvesting-Category.
  • Published: The object is made available via the OAI-PMH interface.
    • Action Withdraw: Same as above, but also removes the object from the OAI-PMH interface.

Use the new nomenclature (Harvesting-Category = Editorial something?), what about fully automatic publishing, show only two statuses?

3.3 New User Interface Concepts

No new UI concepts needed.

3.4 Accessibility Implications

No 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

-

4.3 Privacy

No privacy implications.

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}

  • {Test case number linked to Testrail} : {test case title}

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

Last edited: 7. Mar 2025, 13:51, Schmitz, Tim [tschmitz]