IDs and LOD Discussion

From CETAF Identifiers Wiki
Revision as of 07:55, 17 October 2017 by Anton Güntsch (Talk | contribs) (CETAF collection data index)

Jump to: navigation, search

In 2016 and 2017, the ISTC decided that improving LOD capabilities of CETAF Stable Identifiers for collection objects should become a priority. This involves primarily

  • activities for improving links from collection metadata to external resources and concepts and
  • implementation of a working CETAF collection data index prototype as a basis for advanced inference mechanisms.

Ideas, discussions, and outcomes linked to these targets will be documented on this page. Please feel free to add your thoughts / comments / results below. More information about the CETAF identifier initiative is available on the main wikipage.

Improving links to external resources

BGBM: we started to discuss how to enrich our (rdf) metadata and concluded that we will start with looking closer at collectors. Our first step will be to export collector names and collector IDs from our herbarium management system (JACQ) and sort them by frequency of use. We will then setup a spreadsheet with columns for ...

  • collector name
  • local collector ID BGBM
  • link to example specimen(s)
  • external resource: wikidata
  • external resource: HUH
  • external resource VIAF
  • problem flag

... and ask a student assistant to search for collectors in wikidata / HUH / VIAF and enter the (URI) identifiers.

By starting with frequent collectors we hope to be able to achieve a wide coverage with reasonable efforts. It would be great if other herbaria could also start to work into this spreadsheet. In this case we would probably just have to add more fields for local collector IDs.

The same workflow could be implemented for geographic features.

CETAF collection data index

BGBM: As a first step, we would like to create a raw list of available CETAF stable IDs. If correctly mapped, all IDs should be accessible via the GBIF API. Based on this list we would then try to harvest the RDF metadata directly from CETAF institutions.