DSpace#1306 - Implementation that makes it possible to customize thum…

[DanGastardelli]

…bnail descriptions of items, collections and communities

References

Fixes #1306
This change was aimed at #1306 which now allows a detailed description of the thumbnail logo images of items, collections and communities (also recognized by screen readers).

Description

First, logic was created using OnInit in the thumbnail component to bring the value of the thumbnail description to the "alt" text contained in the image tag in the html. Fields were then created for insertion in the creation and editing of communities and collections that allowed the insertion of details about the logos involved and finally the creation of translation keys for these fields.

Instructions for reviewers

First of all, it is necessary to create the "dc.description.thumbnail" metadata in the backend where the test is carried out.

List of changes in this PR:

• Creating logic in the thumbnail component to pull the item thumbnail description (using the onInit function and using variables created to obtain the thumbnail description through the thumbnail object);
• Making conditionals in the html to check if there is a customized description and passing it in the alt of the thumbnail;
• A field was created in the community form and collection form using the new metadata "dc.description.thumbnail" to accept descriptions;
• Functions were created in the collection model and community model that provide thumbnail descriptions of collections and communities;
• In the html of the community page and collection page components, conditionals were inserted and check if there is a customized description and insert the variable with the description in the alternative text.
• The appropriate translation keys "community.form.thumbnail" and "collection.form.thumbnail" were created for the field created for communities and collections (translations made in English, Portuguese and Spanish)

Include guidance on how to test or review your PR.

To test, simply create a collection and community that contains a logo. In the "Thumbnail Description" field, fill in details of this logo and finally inspect the logo or use a screen reader on the logo to validate the description entered. Now as for the items, just insert a bitstream and create the thumb by running filter-media in the backend. After that, go to item editing and go to the bitstream tab and edit the thumbnail description and then go to the item and hover the screen reader over the image or inspect it to see if the description matches the one entered.

[tdonohue]

@DanGastardelli : This dc.description.thumbnail field isn't a valid Qualified Dublin Core field, so I would not recommend adding it. Additionally, this is metadata about the Bitstream (logo), but you appear to be storing this metadata on the Collection.

It's not a great idea to store this on the Collection, as it means that this dc.description.thumbnail field would be shared as Collection description metadata whenever someone accesses the Collection from the REST API (or other machine interfaces like OAI-PMH).

Ideally, it'd be better to store this metadata as simply dc.description (which already exists) on the Bitstream object itself. That'd be much clearer & cleaner than creating a new metadata field to store the information on the Collection.

If it's not possible or easy to store this metadata on the Bitstream itself, then we could consider keeping this metadata on the Collection, but store it in a "hidden" field like dspace.thumbnail.description. This would be better than creating an invalid dc.description field. But, this new field would need to be created though in the dspace/config/registries/dspace-types.xml on the backend.

[github-actions]

Hi @DanGastardelli,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!