Fixes for embedded Mirador viewer

[mspalti]

Description

Fixes a few minor bugs involving the embedded Mirador viewer.

Instructions for Reviewers

Bug 1: Currently you can remove or add the mirador viewer by only removing or adding the dspace.iiif.enabled field from the Item. Toggling the value to true or false has no effect. This PR makes it possible to show/hide the viewer by updating the field value.

Bug 2: For sites that support the IIIF Content Search API it's extremely useful to pass the DSpace query to the viewer. The query is obtained from the Angular route history. The current implementation doesn't work for searches executed from new community and collection pages and is updated here to support all route paths that include a query parameter.

Bug 3: When embedding the viewer we see errors in console. This PR should eliminate those errors.

You can test by adding dspace.iiif.enabled to an item and toggling the value to true and false to verify that the viewer is correctly enabled and disabled.

IIIF Content Search can't be tested directly, but if you view an IIIF-enabled item from a list of search results on a community page you should see the query term in the iframe URL. (If you also add iiif.search.enabled to the item metadata the query term will appear in the viewer.)

Console should be clear of errors.

List of changes in this PR:

• iiif-item-utils is updated to address the first two bugs listed above
• The mirador component and template are modified to use the DsSafeUrl pipe when adding the URL to the Mirador iframe. This fixes the unsafe resource url error in console that was triggered when using an observable.
• A minor change to the mirador config.default.js fixes a second console error

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[github-actions]

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

[EikLoe]

Hi @mspalti ,
thanks for the PR. Could you remove the merge conflicts, so I can test it?

[mspalti]

Hi @EikLoe ,
I think this is ready for review. Sorry not to get to it sooner.

[mspalti]

Just a quick on testing the search query.

To verify it is working the item metadata must include iiif.search.enabled=true. I was mistaken above when I said that the query will appear in the iframe url even if search is not enabled.

[github-actions]

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

[mspalti]

The important bug appears to be resolved by #5541

I'll submit another PR for two other minor issues mentioned above.