...
| Required? | User Story |
|---|---|
| Catalogers | |
| MUST HAVE | As a cataloger, I want to edit an entity (e.g. work, instance, etc.) and add a link to an external URI from an external authoritative sources (e.g. LCNAF, OCLC FAST, etc.). |
| MUST HAVE | As a cataloger, I want to edit an entity (e.g. work, instance, etc.) and display a label from an external authoritative sources (e.g. LCNAF, OCLC FAST, etc.). |
| MUST HAVE | As a cataloger, I want to be able to enter the exact external authoritative label and get the URI from the external authority linked to the entity being edited. This applies when there is a unique authoritative term. |
| MUST HAVE | As a cataloger, I want to start typing a known external authoritative label and get the URI from the external authority linked to the entity being edited. This is left anchored type-ahead. |
| MUST HAVE | As a cataloger, I want to start typing a known variant external authoritative label and get the URI of the authoritative label linked to the entity being edited. |
| MUST HAVE | As a cataloger, I want additional information in the search that indicates that the term listed has a variant that matches the keyword typed. |
| MUST HAVE | As a cataloger, I want to type in the alternate identifier (e.g. Q label in wikidata, ISNI label, organization code etc.) and get the URI for those entities. |
| OPTIONAL | As a cataloger, I want to be able to search for a broader term in a hierarchy and get a list of narrower terms from which to select. NOTE: Some systems have seen performance issues in actual implementations. Catalogers generally know what they are looking for. |
| OPTIONAL | As a cataloger, I want to be able to see broader and narrower terms when the authority is hierarchical. |
| OPTIONAL | As a cataloger, I want to be able to step into broader or narrower terms when the authority is hierarchical. |
| As a cataloger, when I am unable to find what I'm looking for in an authority lookup, I want to be able to search an authority source in an external site by clicking on a link to its native search UI. | |
| As a cataloger, I know some keywords that will help me locate and select an authoritative term to add as metadata about an entity. (Christine asks: does this mean "As a cataloger, I know some keywords that aren't name strings that may help me locate and select an authoritative term?") | |
| As a cataloger, I want search results to contain highly relevant terms for my keyword search. | |
| As a cataloger, I want to see, for each entity that appears in results of my keyword search, which of the fields that were searched triggered its inclusion in those results. | |
| As a cataloger, I want to see contextual information about an authoritative term that distinguishes it from other, similar-looking terms, to help me to select the correct authoritative term and to recognize false positives. | |
| As a cataloger, I want to be able to filter search results to a specific date range for a field on the authoritative term (e.g. birth date, death date, floruit, etc.). | |
| As a cataloger, I want to be able to filter search results to a specific class type (e.g. a corporate body). | |
| As a cataloger, I want to be able to filter search results to a specific language. (Christine asks: does this mean "As a cataloger, I want to see labels and other strings tagged with my preferred language when viewing search results"? And/or "As a cataloger, I want to prioritize search results based on strings tagged with my preferred language"? Or something else?) | |
| As a cataloger, I want search results to be returned quickly, so that I can catalog efficiently. | |
As a cataloger, I want to be able to request additional search results if what I am looking for isn't visible in the current set of results displayed. | |
| As a cataloger, I want to determine whether the entity I'm searching for doesn't exist in the resource that I'm searching. | |
| Developers | |
| As a developer, I want one field in the authoritative term to be a human readable, meaningful representation of the term that can be displayed to users to identify the term for selection. | |
| As a developer, I want to receive a permanent URI for each term to uniquely identify the term. | |
| As a developer, I want to provide a widget that enables a cataloger to select a term from an authoritative source using left anchored autocomplete. | |
| As a developer, I want to provide a widget that enables a cataloger to type in keywords and see a list of terms sorted in rank order. | |
| As a developer, I want to provide additional information about terms to facilitate the accuracy of selection. | |
| As a developer, I want to quickly show search results to users (e.g. sub-second, specific threshold TBD) | |
| As a developer, I want to receive pagination information with search results, such that, I can request the next page of results. | |
| As a developer, I want data to be returned as linked data allowing for configurations that map ontologies to a normalized json format. | |
| As a developer, I want data to be returned in the same format from all authorities (e.g. normalized json, json-ld, or something else) | |
| As a developer, I want to be able to fulfill all search requests. (e.g. source authorities respond to all requests with excellent uptime) | |
| As a developer, I want to update cached labels and URIs as changes are made to the authoritative source data. | |
| Providers | |
| As a provider, I want my data to be used. | |
| As a provider, I want my data to be used accurately. | |
| As a provider, I want to support the creation of application widgets that provide access to our data. | |
| As a provider, I want our API(s) to be performant (e.g. sub-second queries, specific threshold TBD) | |
| As a provider, I want access to our data to be available 24-7 with occasional outages for maintenance that will be announced in advance. | |
...