CLAW Linked Data use cases

[mrmiguez]

Hi all,

Wanted to get some of these down while they're still on my mind. Also it seemed cleaner to start a new issue just for use cases, rather than piggyback on the CLAW MVP issue:

• Support for controlled vocabularies published as linked data:

  • Auto populate (auto suggest) terms within a given namespace. For example, if I select http://id.loc.gov/vocabulary/graphicMaterials as a subject namespace... suggest terms from TGM as I type. Likewise if I select the same namespace for a genre field, only suggest the terms in TGM classed as genres.
  • Ability to import & meaningfully work with more boutique vocabs published as RDF. Like the FISH Building Materials Thesaurus: http://www.heritagedata.org/blog/vocabularies-provided/
  • Scan supplied or linked RDF vocabs for features defined in the relationships.
    • If a vocabulary offers multi-language support, allow me to see which languages are offered, and select which ones I would like indexed.
    • For a thesaurus described in RDF maybe use the hierarchy of the thesaurus to generate a new discovery-layer/browse page for objects.

• Use object description to embed RDFa into the HTML for the object's view pages

• Be aware of linked data elements inside of objects

  • If I have a resource encoded in TEI, and the markup includes elements to link to VIAF or LCNAF authorities.... maybe those authorities within the object can be pulled out into the object's descriptive record

I don't know how much of that makes sense.

[uconnjeustis]

@mrmiguez Thanks for starting the conversation on issues. Omeka has a neat feature that allows you to plug in various controlled vocabularies such as fast or lcsh. Building on your thoughts, it would be really nice to be able to "plug and play" with a variety of linked controlled vocabularies. I've started another issues thread to gather a list of those vocabularies. This would be a great modular approach as the vocabularies vary across uses and institutions.

[alehman-loc]

Everything seems sensible so far. I agree with the plug and play for different vocabularies - is there a file format that we could use with a standard importer of some sort? I don't know much about these vocabularies.

My use case builds off of the RDF UI Use Case Thread because I'd like to see a conditional workflow for entity creation that allows you to "pause" ingest of metadata to go create a basic person/place/thing/event entity to link to your original record. For example, if I have an image of an event which has not been "cataloged" or "created" yet, which I want to attribute to a photographer who does not yet have an authority file, I'd like to be able to create those events and people with ease. You said to ask for unicorns.

[uconnjeustis]

Islandora-CLAW/CLAW 489 has been created. Please refer to this issue and add remarks as necessary.

@mrmiguez We're hoping to join the CLAW calls to discuss these. If you have any remarks, feel free to continue the discussion here or add remarks to this CLAW issue.