Documentation: Consider how to model skos concept schemes in Islandora

[acoburn]

This is _not_ for the MVP, but some people (e.g. me) may want to model concept hierarchies in Fedora and publish them as linked data. For example: locally-defined subjects and entities that are not present in Getty or LoC. It would probably be natural to model these using SKOS.

[DiegoPino]

@acoburn good news. It's core in Drupal. We just need to make the UI a little prettier and enable some type/consistency checking. Already testing schema:Book here 😄 with some skos concepts. Needs some work of course. We could add some use cases and ideas for the UI

[ruebot]

This is a great thing for us at York. @deantiquate might have some thoughts about this. If you want to work on use cases @acoburn, I think we would be game.

[ruebot]

Might as well tag @akosavic too so it is on her radar.

[acoburn]

@ruebot at the moment, we have two use cases. Following linked data best practices, we are making extensive use of URIs in our metadata (things, not strings). This is particularly true for subject fields dcterms:subject but also for many other predicates.

The two use cases we currently have are:

• The name/subject/entity does not exist in a commonly available vocabulary (e.g. it's not in LoC or Getty). This is particularly the case for less well-known individuals or corporate entities. It is also the case for subjects that we want to model that are more narrowly defined than what might exist in LoC.
• The name/subject/entity that we want to use is insufficient. For instance, for a particular Native American collection that we manage, the LoC entries use language to describe the name/subject/entity that is inconsistent with how native groups describe that same name/subject/entity. In this case, we'd model a skos:Concept and use owl:sameAs to link it to the external vocabulary.

In both cases, the resources that form these concept schemes would be publicly available as linked data (HTML/RDFa and JSON-LD)

[cmharlow]

Sorry to jump in, but FWIW, we're (we == Cornell == primarily me right now) working on a kind of "authorities/context class entities" infrastructure + store (using Vitro 1.8 w/a public Fuseki side care instance) at Cornell to handle this type of question for our various Fedora 3 + 4 instances (mostly but not always feeding into various Hydra stacks), a Dspace instance, SharedShelf instance, couple of Bepress instances, our MARC cataloging $0s (looking to FOLIO + creating an authority control module based on this stack), the LD4L BIBFRAME URI recon/generation work during MARC21 to LD4L BF conversion, etc. If at all of interest to yall, I've be very much interested in attending a call to discuss modeling ideas/approaches for these + possible areas of work overlap. Totes okay if not of interest though - this is a bigger thing in some ways for us.

[cmharlow]

Just, not a call in the next 2 weeks (if that even happens) bc i'm in the middle of the LD4All BIBFRApocalypse. And thanks to @ruebot for showing me this thread. I'll be follow yall's work with interest, as always. +1 you guys.