Skip to content

Requesting an Authority

E. Lynette Rayle edited this page Jul 9, 2019 · 3 revisions

Process for requesting a new authority in the context of the implementation process

Creating a connection to a vocabulary is a multi-step process with some steps performed by the requesting metadata specialists and some performed by the technical team. This describes the process and basic order of who does what when.

By metadata team...

  • Request a New Dataset for Sinopia and add the following information
    • identify a primary coordinator to shepherd the authority through the creation and maintenance process (if there are disagreements, this person will serve as the arbiter making the final judgement on how best to support the authority)
    • identify URL to downloadable RDF
    • (optionally, if available) identify URL to documentation on API for working with linked data using a direct connection to the authority

NOTE: For most authorities, caching is preferred over direct access to allow for refinement of indexing and extended context provided to users. But it is good to know if an authority has the option for direct connection.

By technical team...

  • If possible, make a direct connection to the authority (available for only a few authorities)
  • If not possible to direct connect or to allow more control, download authority RDF and cache triples in the LD4P authority caching system
  • Configure basic access to the authority through QA lookup system

By primary coordinator... (Steven Folsom can help you with how to do this documentation)

  • work with others to develop consensus on the information described below for the authority tab in the spreadsheet
  • create/refine the tab for the authority in Indexing of External Data for Look-ups (spreadsheet)
    • (Col A) define entities for sub-setting the search results (e.g. person, organization, etc.)
    • (Col B) define ldpath to important data for indexing or display
    • (Col C) indicate which data should be in the index (influences search results); see also Col F
    • (Col D) indicate which data should be included in the extended context displayed to users through the UI to aid in the accurate selection of an entity
    • (Col F) provide additional notes on indexing process that will be used to refine search results

By technical team...

  • refine the indexing process in the data cache layer based on Col C and Col F
  • refine the data returned from the data cache layer based on the extended context identified in Col D
  • refine the QA normalization layer to return data based on the extended context identified in Col D

By metadata team...