...
Use Case: User wants to find the URI of an entity from within a metadata editor
...
| Priority | 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 to see context about an authoritative term that 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, etc.) | |
| As a cataloger, I want to be able to filter search results to a specific class type (e.g. ???) | |
| 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. | |
| 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 over time. | |
| 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 return search results (e.g. sub-second, specific threshold TBD) | |
| Providers | |
| As a provider, I want my data to be used. | |
| 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 catalogers to be able to make an accurate selection. | |
As a user of a metadata editor application, I want to find an entity in an outside authority to use as metadata in a local record.
...