...
| Required? | User Story |
|---|---|
| Catalogers | |
| As a cataloger, I want to edit an entity (e.g. work, instance, etc.) and add metadata about the entity from authoritative sources (e.g. LCNAF, OCLC FAST, etc.). | |
| As a cataloger, I know exactly the authoritative term I want to add as metadata about an entity. | |
| As a cataloger, I know the start of the label of the authoritative term I want to add as metadata about an entity. | |
| As a cataloger, I know some keywords that will help me locate and select an authoritative term to add as metadata about an entity. | |
| As a cataloger, I want search results to contain highly relevant terms for my keyword search. | |
| As a cataloger, I want to know which fields were searched that produced the search results for keyword search. | |
| As a cataloger, I want to see context about an authoritative term that helps with disambiguation and increases the accuracy of selecting the correct authoritative term. | |
| 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. | |
| As a cataloger, I want search results to be returned quickly, such that, performance times do not detract from the cataloging workflow. | |
As a cataloger, I want to be able to request additional search results if what I am looking for isn't 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. | |
...