...
Required? | User Story |
---|---|
Catalogers | |
As a cataloger, I want to be able to search across multiple authorities. | |
As a cataloger, I want the display of data in the editing app to follow a consistent and predictable format. | |
Developers | |
As an application developer, I want a reliable source of data, such that, I am able to fulfill all search requests. | |
As a cache developer, I want to store all or significant portion of authoritative data locally. | |
As a developer, I want to control how data is searched. | |
As a developer, I want to control what data is returned to and displayed in the end user application (e.g. extended context). | |
As a developer, I want to control the format of data the editing application receives for the selection widget. | |
As a cache developer, I want to update cached data as changes are made to the authoritative source data. | |
Producers | |
As a producer, I want to make my data available for download. | |
As a producer, I want consumers of my data to use the most up to date version of the data. | |
As a producer, I want to provide a change management API that provides information on changes to terms in the dataset (e.g. new, deleted, changed, deprecated, moved, split, merged, etc.). |
Common External Search Format/Ontology
Required? | User Story |
---|---|
Catalogers | |
As a cataloger, I want to know that data drawn from multiple authorities have the same meaning. | |
Developers | |
As a developer, I want to use the same code to process data coming from multiple authorities. | |
As a developer, I want to support searching across multiple authorities. | |
Producers | |
As a producer, I want data alignment between authorities. | |
As a producer, I want to provide a mapping of my data to a community supported search ontology. | |
As a producer, I want to have an internal representation of my data that may be different from other authority providers. |
Auto-fill Batch processing
...
Required? | User Story |
---|---|
Catalogers | |
As a cataloger, I want to load data in a reconciliation program (e.g. open refine) and apply changes across multiple entities (e.g. works, instances, etc.) | |
As a cataloger, I want to be able to filter potential choices by date range. | |
Developers | |
Producers | |
As a producer, I want to support an API that allows my data to work with popular reconciliation programs (e.g. open refine) |
Common External Search Format/Ontology
Required? | User Story | |
---|---|---|
Catalogers | As a cataloger, I want to know that data drawn from multiple authorities have the same meaning. | |
Developers | As a developer, I want to use the same code to process data coming from multiple authorities. | As a developer, I want to support searching across multiple authorities. |
Producers | ||
As a producer, I want data alignment between authorities. | As a producer, I want to provide a mapping of my data to a community supported search ontology. | As a producer, I want to have an internal representation of my data that may be different from other authority providers.