...
- Caching 1
- Downloads - cache management synchronization
- Caching 2
- Notification of updates when entity descriptions change, or at least ability to search by dates/types of changes
- Deprecations - mechanism to state that this term is replaced by another term - how do end users know that the term is no longer valid
- Reconciliation
- entity reconciliation
- Accuracy 1
- identify you have the authority you want - got the right john smith
- How do humans choose between two similar but distinct entities?
- Accuracy 1 2
- right information to search and display - need an easy way to define
- moving to linked data - which attributes to include for each entity
- May need more context some times
- Rank ordering so results are displayed with first results as best result
- Listed alphabetically
- Option for left anchored search
- Which labels to display when multiple labels - across languages and scripts and kinds of names
- Can users personalize how the data comes back?
- API approach
- API - focus first on retrieval by REST before search and browse
- browsing with context when know what you are looking for and a good amount of time, catalogers know what they are looking for
- searching to discover when you don't know what you are looking for
- One service doesn't fit all needs. Suggest, Search, Browse - each serve different needs
- Data Related
- Which data elements are unique or intended to be unique?
- Which data elements are intended for end users (such as library users browsing a collection) and which are intended primarily for internal use
- Suggest SKOS ontology (Avoid talking about modeling for years) and
- Suggest JSON-LD for format
- Dealing with errors
- more consistent and granular error reporting to determine the source of the error
- Other
- indexing - connections of relationships between entities
- suggest 2.0 document
- Learning from users
- Use cases
- Versioning of authorities - and how is it surfaced through API
- Learning how something has changed and knowing what to do in response
- Rank ordering - being able to manage and choose the context of your query where context is provenance, community recommendations, relationships, etc
- Presence or absence of connections to other entities; making choices based on interconnectedness and fullness of data
- what is the impact on APIs with respect to deprecations
- reconciliation - reconcile more than just adjunct works and references to outside data and across languages
- concerns with sameas connections between data that may not be accurate
- reconciliation - why isn't this just the openrefine API; implemented and well understood
- responsivity for autocomplete
- to enable local authorities to participate by implementing the API - allow local to define a narrower term to a broader
- - discovery of (and enrollment in) new authorities
- handling different data models (the organization of the returned data handling different syntaxes
- server side pagination vs client side
- pagination: expanding set of results; turning off pagination to get all results
- standards-based
...