-
Notifications
You must be signed in to change notification settings - Fork 2
Development Roadmap
Douglas Campbell edited this page Jun 23, 2016
·
2 revisions
API infrastructure
- Indexer extracts records from catalogue system and converts into JSON-LD data
- ElasticSearch record store
- REST application using Java shim
- Kong API service management layer
Metrics
- All catalogue and vocabulary records loaded as JSON-LD
- 80% of Te Papa fields mapped
- Simple typing of records
- Indicative resource endpoints
- Simple querying
- All Te Papa fields mapped
- Embedded object expansion
- Granular record typing
- All resource endpoints defined
- Persistent IDs
- Output formats: JSON, JSON-LD, XML, RDF/XML
- Advanced querying (denormalised records stored in ElasticSearch)
- API key registration and authentication
- API documentation
- Analytics
- Additional functionality to support Te Papa websites and onsite applications
- Media delivery via API
- Hypermedia links
- Authentication options, e.g. OAuth
- Rate limiting
- Dev tools, e.g. interactive demo, SDKs
- Download options (TBD)
- CSV output format
- OAI-PMH
- Integrate external data, e.g. DBPedia, VIAF, LINZ
- Industry-specific data formats, e.g. GIS ISO 19139
- Alternative querying, e.g. geo bounding box
- Access to restricted data for staff
- SPARQL endpoint
- Writeable resource endpoints
- Storage of UCD (User Contributed Data), e.g. transcripts
- Personalisation, e.g. saved searches
API Reference
Development Project