What is the goal of sprint 1?
The sprint’s focus was on establishing an initial direction and architecture for the project. As a push goal, we hoped to get to our first milestone -- an initial stand-alone platform where we can create, edit, and retrieve authority records. It was a push goal because this is the very first sprint so we didn’t know what we might be able to accomplish right out of the gate. It also was a push because setting up infrastructure can be full of surprises! Our sprint was truncated because of the Code4Lib conference. All of the UC San Diego development team and most of the Santa Barbara team was at the conference. It did mean that people met face-to-face though.
What is the milestone that this sprint is supporting?
The Milestone 1 is to have an initial stand-alone platform where we can create, edit, and retrieve authority records.
Accomplishments of Sprint 1:
Devops - This was a bit of a combination goal with Starlight. Configure the integrated Continuous Integration to build, test, and deploy code to build and test each change automatically.
Storage - Select a preliminary persistence technology for index, current data, and events.
Initial Concept Model - Create a model that has some form of human-readable documentation and a machine readable description of the model. Define the base set of relationships to external authorities and vocabularies and document the human readable and specify the machine readable form.
Event Log - Log creation of new authority records in an append-only log. This log will track all changes to records in the Lark system.
Did we do everything we set out to accomplish?
No! We currently can not update an existing authority record through an API with a serialized format in a way that conforms to the base concept model. We do expect that to be accomplished in Sprint 2.
Our goal of Sprint 2 is to deploy a basic authority platform to staging, create a base agent, and update the authority records.