Islandora has too many Type vocabularies.

[rosiel]

This is a discussion ticket.

If I create an islandora object, I have two places to say "what type it is": "Resource Type" field, optional

And "Model" (under "System"), mandatory:

If I select "Image" on both, I get (abridged jsonld):

  "@graph": [
    {
      "@id": "http://localhost:8000/node/1?_format=jsonld",
      "@type": [
        "http://pcdm.org/models#Object",
        "http://purl.org/coar/resource_type/c_c513"
      ],
...
      "http://purl.org/dc/terms/type": [
        {
          "@id": "http://localhost:8000/taxonomy/term/5?_format=jsonld"
        }
      ],
    },
...
    {
      "@id": "http://localhost:8000/taxonomy/term/5?_format=jsonld",
      "@type": [
        "http://schema.org/Thing"
      ]
    }
  ]
}

The "Resource Type" is supposed to be, IIUC, the "metadata" declaration of what kind of thing it is - similar to typeOfResource in MODS, coming from a controlled list. The list I have from MIG is here, and it looks similar but not exactly like the existing Resource Types available. If they're supposed to be the same list, then we have URIs available in that link to do the sameAs. (Above, taxonomy/term/5 is "Image" in the Resource Types vocabulary).

The "Model" field relates to what happens with derivatives, context, etc. It seems to be doing something special in the JSONLD - not only is it mapping its value to @type instead of a "normal" predicate, it's swapping out taxonomy/term/24 for its external URI, http://purl.org/coar/resource_type/c_c513.

Is this swapping-out a thing that we can do in the mapping yml?

Choosing the same thing twice is a nonsensical UI. Three times, if you count:

1. choose a resource type "image"
2. choose a model "image"
3. choose "image" from the available media types

Can we make the user pick a model first, then pre-populate the sensible resource type?

Or could we merge the two taxonomies so the terms so the resourceTypes are the actionable elements?

[dannylamb]

I usually defer to you on questions like this :blush:

So there's a lot of Drupal technicalities there that could definitely be smoothed over, and some we're stuck waiting for fixes on. Number 3 for example, we've got to let you choose between image and file media depending on if you want to upload a jpeg/png/gif or a tiff. Being able to make a Tiff as an Image media would then let us collapse that decision in the UI.

As for 1 and 2, it's mostly a separation between what the system needs and what/how you choose to describe it. If we can reasonably collapse them, that'd be good. Just keep in mind there's no guarantee people will use the "Resource Type" field, but they MUST use the "Model" field. So we should probably base things off that when shortcutting these choices in the UI.

Also, FWIW, we're getting close to webform/multi-step ingest type stuff here (which is good!)

[Natkeeran]

@rosiel If feel this question has been reasonably answered, please consider closing this ticket.