Different Fields for LOM Digest

1 Initial Problem

The LOM Digest form does not offer all fields that are regularly needed when filling out LOM, especially when the installation is connected to an OER referatory, see Metadata interface for querying by referatories.

Conversely, the LOM Digest does contain a seldomly used input for Typical Learning Time. 

2 Conceptual Summary

The LOM Digest should offer inputs for

Configured vocabularies should be offered here as well, see Infrastructure for Adding Metadata from Controlled Vocabularies.

The Digest should not offer an input for Typical Learning Time. However, it should remain a part of Educational in the Full LOM Metadata Editor and can still be set. It should just lose its place in the front row. 

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

The LOM Digest Form offers a new section 'Classification', containing a dropdown 'Learning Resource Type' and a text input 'Discipline' (which writes to the first Classification > Taxon Path > Taxon > Entry in LOM).

The section 'Authors' is renamed to contributors, and obtains a text input 'Publisher' (which writes to the first Lifecycle > Contribute with role 'Publisher' > Entity in LOM).

All of these inputs take into account the configured controlled vocabularies, and behave like described in Infrastructure for Adding Metadata from Controlled Vocabularies for the full editors. The entries for 'Learning Resource Type' are taken from all active vocabularies for the correpsonding LOM element.

'Discipline' and 'Publisher' offer either a free text input (if no vocabulary is configured for the corresponding LOM element), a dropdown with values from controlled vocabularies (if one of the vocabularies does not allow custom input), or a choice between the two via a radio input.

Further, the section 'Typical Learning Time' is removed from the LOM Digest form (but is still offered in the full LOM editor).

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

-

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