CORE-1967 Initial Local Contexts label display

[psarando]

This PR will add the initial Local Contexts label display to Data Listings and Metadata Templates.

When the metadata for a folder contains a LocalContexts attribute, and a rightsURI sub-attribute with a valid Local Contexts project URI as its value, then the Local Contexts labels for that project will be displayed in the data listing, as well as in metadata templates (such as the DataCite 4.2 template) that have a LocalContexts attribute field.

Each label is also an icon button that opens a dialog which displays the label or notice's descriptive text, along with a larger image of the label, and a link to the Local Contexts project page.

This PR also adds a custom LocalContexts attribute field for metadata templates (such as the DataCite 4.2 template) which displays only a Local Contexts Hub project URI field for the user, and will auto-populate DataCite metadata and child AVUs using the project ID parsed from the URI and the Local Contexts Hub API response (which is also used to display the project's labels below the field).

---

---

---

It's also possible for Local Contexts Hub projects to have sub-projects.

This can also be supported in the DE if the user adds the sub-project's URI to the associated data in the main project's folder:

---

Finally, this is an example Dialog displaying a project's TK Label and associated text:

---

[psarando]

This logic in the Local Contexts Hub project query's onSuccess function synchronizes the labels defined in the project with the DE metadata. It also ensures the other child AVUs required by DataCite v4.2 are included.

The top-level AVU's value is based on suggestions from DataCite's docs.

The required AVU and child AVUs should be like the following:

{
      "attr": "LocalContexts",
      "value": "The \"January Test\" project has Labels and/or Notices applied through the Local Contexts Hub. For more information, refer to the project page: https://sandbox.localcontextshub.org/projects/adcbca87-081a-4e2c-b6af-bff12fe3b7b0",
      "unit": "",
      "avus": [
        {
          "attr": "rightsIdentifier",
          "value": "Traditional Knowledge (TK) Notice",
          "unit": ""
        },
        {
          "attr": "rightsIdentifier",
          "value": "Biocultural (BC) Notice",
          "unit": ""
        },
        {
          "attr": "rightsIdentifier",
          "value": "Attribution Incomplete Notice",
          "unit": ""
        },
        {
          "attr": "rightsURI",
          "value": "https://sandbox.localcontextshub.org/projects/adcbca87-081a-4e2c-b6af-bff12fe3b7b0/",
          "unit": ""
        },
        {
          "attr": "schemeURI",
          "value": "https://localcontexts.org",
          "unit": ""
        },
        {
          "attr": "rightsIdentifierScheme",
          "value": "Local Contexts",
          "unit": ""
        }
      ]
    }

[psarando]

This function is called whenever the user updates the Local Contexts Hub project URI in the form field, and if the URI does not match the rightsURI child AVU's value, then it is updated, and the other child AVUs required by DataCite v4.2 are also included.

[ianmcorvidae]

I saw one small thing but as far as I understood the rest, looks fine to me. The only other thought I had, which it's possible is already in place since I don't think it'd be in this PR anyway, is that given the LocalContexts project URI acts as a required field, I don't know if the template should have a note saying something like "if LocalContexts doesn't apply, use <a different template, I guess just regular DataCite>" just to avoid confusion if someone selects the LocalContexts one in error.

[slr71]

I didn't catch anything.

[psarando]

The only other thought I had, which it's possible is already in place since I don't think it'd be in this PR anyway, is that given the LocalContexts project URI acts as a required field, I don't know if the template should have a note saying something like "if LocalContexts doesn't apply, use <a different template, I guess just regular DataCite>" just to avoid confusion if someone selects the LocalContexts one in error.

So there is a little bit of trickery happening with this custom field in the DataCite template, because the top-level LocalContexts attribute is actually not marked as required, so it is not included by default and the user is not required to add it in their DataCite metadata:

If the user does add the LocalContexts attribute in the template, then it displays the field as required, but it's based on the fact that the rightsURI sub-attribute is required in DataCite metadata, so the custom field is borrowing the validations of that rightsURI sub-attribute.

Here's how it currently looks in prod without this custom component, when a user initially adds the attribute in the template:

The template still defines this attribute with all these sub-attributes, it's just the UI is displaying the simplified custom component for the LocalContexts attribute; and this custom component will be displayed in any metadata template that has a LocalContexts attribute, not just the DataCite template.

This also means all the required sub-attributes will still be included in a CSV download of the template for bulk metadata uploads.

We can also add another metadata template that only has the LocalContexts attribute, for users that only need labels and notices to display for their data, but because the custom component will add all the sub-attributes required by the DataCite template, the user can still use that template later if they need a DOI for their data, and those required attributes will already be there.

I was also thinking the template's description for this attribute could be updated once these changes go live in prod, so it will make sense in both the custom component in the UI, but also in the CSV guide download.

[psarando]

Thanks for the reviews 👍