The API of relates to the strategy of the National Library of Finland (NLF), where openness is one of the corner stones. In addition the Open National Library policy (under work) and Digital Humanism policy include openness and interfaces for the key services as a main targets for the years ahead.
In addition for the modern user, API is needed in order for the user to find their own ways how to utilize the cultural heritage material. API enables connecting different services and maybe even creation of new kinds of services and products.
APIOps joint project to collaborately develop an API idea of the National Library of Finland. Aim is to:
- define API Model Canvas or two for the case and
- provide Swagger 2.0 based descriptions for the APIs and
- mockup servers for prototyping
Of course for APIOPS as a whole, one aim is to learn by doing.
- 6.2.2016: APIOps Monthly Jam
- 20.2.2016: Get and describe first developer use case
- 6.3.2016: APIOps Monthly Jam: Finalize MVP version of API Model Canvas & Finalize Design of MVP API
- 2.4.2016: APIOps Monthly Jam: Implement good enough mockup responses and launch API in Heroku
- 17.5.2016: Suggest APIOps Jam in API Days 2016 in Tampere. Get ideas for API usage and get developer feedback.
- 1.6.2016: Package all for 'sales'
- Tuula Pääkkönen: client and responsible for API Model Canvas
- Ohad: lean startup expert, business models
- Jarkko Moilanen: APItalist, responsible for development process and API design
- Jani Karhunen: developer, one of our API consumers/testers/validator (more needed!)
We use waffle.io for this project: DigiAPI waffle.io
Business models for this case are in wiki: https://github.com/APIOps/Digiapi/wiki/DigiAPI
We utilize user stories as fuel for development. All user stories should be written as new issue with label user story.
Development version of the meta API spec in Swagger 2.0 format
In progress version of the meta API
All API features should be requested as new issue with label feature.