Feature/#138 metadata generic textapi

Feature

Summary

This MR provides extended sections of the metadata on each level (Collection, Manifest, Item).

It also takes care of the project specific metadata object optionally given in the manifest object.

All the item data is passed down now to the metadata component as opposed to before, where just certain fields have been extracted.

The image license and corresponding notes are displayed now as well.

Does the result of the MR comply to our "definition of done"?

• Unit tests passed
• Code reviewed
• Acceptance criteria met
• Functional tests passed
• Non-Functional requirements met
• Product Owner accepts the User Story

Documentation

• I updated the README (if applicable)
• I provided my functions with appropriate documentation
• I adjusted other parts of the documentation (if applicable)

Tests

Are we able to test this new feature?

• Yes, everything can be done via unit tests.
• Yes, you can test by following these steps:

switch the entrypoints:

• ahikar collection: "https://ahikar-dev.sub.uni-goettingen.de/api/textapi/ahikar/arabic-karshuni/collection.json"
• ahikar manifest: "https://ahikar-dev.sub.uni-goettingen.de/api/textapi/ahikar/arabic-karshuni/3r177/manifest.json"
• sampledata: https://subugoe.pages.gwdg.de/emo/backend/sampledata/collection.json

and take a look at the metadata panel

• No, it is not possible.

Changelog

• I added a statement to the CHANGELOG.

Related Tickets

Add all related issues and especially those to be closed.

Related

Closes

Closes #${138}

Logs and Screenshots

/cc Mathias Göbel, Frank Schneider, Michelle Weidling