Read-only LOM view

1 Initial Problem

Currently, the only place where users without write-permission can see (parts of) the LOM of objects in on their info screen. It is planned to abandon the info screen in the mid term, see Abandon Info Page.

Additionally, usability tests have shown that 'Metadata' is overly broad as a designator, especially as the 'Metadata'-tab has gotten more and more important for OER scenarios. When asked to select a license for an object, the 'Metadata'-tab was far from the first place where people looked.

2 Conceptual Summary

The subtabs included in the 'Metadata'-tab should be split between two new tabs. A new read-only view should be added, which should contain about the same information that is currently in the LOM sections on the info page:

The LOM sections on the Info Page should be removed.

Note that because of the related feature Allow Deactivation of LOM-Tab/Subtab, the new Content Sharing tab would be deactivatable in the Metadata administration.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

Instead of one tab 'Metadata', objects should carry two tabs 'Content Sharing' and 'Organizational Metadata'.

'Organizational Metadata' should contain, as appropriate, the subtabs 'Custom Metadata', 'Manage Custom Metadata Sets', 'Export Files', and 'Taxonomy Assignment'/'Taxonomy Definition'/'Taxonomy Settings'. These subtabs should only be offered when they are applicable, as they are now inside of 'Metadata'. If none of these subtabs are available, 'Organizational Metadata' is not shown.

'Content Sharing' should contain the old 'LOM' subtab as 'Edit LOM', as well as a new subtab 'Info'. 'Info' should show a selection of LOM Elements mirroring the LOM Digest, along with a download button of the public access export file (see Public Access Export Files for All Objects), similar to the LOM sections on the info page.

Everything but 'Info' in 'Content Sharing' should continue to require write-permission, but 'Info' (and by extension 'Content Sharing') should be availabe with read-permission.

3.3 New User Interface Concepts

-

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

Small changes will be necessary in all components which support LOM, Custom Metadata or Taxonomies.

The LOM related logic will be removed from ilObjectMetaDataGUI, which is a step in the right direction to clean up the relationship between the components MetaData and ILIASObject.

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}

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