Development

Design notes

Notes from planning meeting 7th January: summary notes

A nascent list of motivating scenarios, based on experiences from ICM1, and expectations for ICM2.

sprint 1 aim: to stress design and produce an end-to-end minimal data api server.

sprint 2 aim: end-to-end core functionality of the API, using ICM1 data.

Sprint 2 review Issues from sprint2 and input for sprint3

Sprint 3 aim: deployable implementation sufficient for HPI sprint 1

Sprint 4 aim: support HPI sprint 2, fill in some missing capabilities

sprint 5 support property paths and improved @search for HPI