What was the goal of Sprint 17? * Pushing collections to the OAI endpoint (tidewater) and making the set harvestable from OAI * IIIF Image Server (Cantaloupe) wired into staging and production environments for each campus * Workflow-driven “publish” from Comet to the Shoreline geodata platform What is the milestone that this sprint

What was the goal of Sprint 16? * Editing and adding descriptive and other user defined metadata for existing objects * Running workflow and event triggered work (characterization, access derivatives) * Assigning permanent identifiers (primarily interested in the short term in ARKs as canonical IDs) * Publishing that content to a public access platform

What was the goal of Sprint 15? * Adding/editing descriptive and other user defined metadata * Running workflow and event triggered work (characterization) * Assigning permanent identifiers (ARKs) * Publishing to a public access platform (OAI, IIIF, Shoreline) What is the milestone that this sprint is supporting? To have a robust publish lifecycle

Note: This session was not recorded What was the goal of Sprint 13? * Documentation of work done already in the work cycle. Leave things in as clean a state as possible before we break for several months * Set up meetings to address key questions and concerns before we break * Complete

What was the goal of Sprint 12? Continuation of work for Comet API and MQ What is the milestone that this sprint is supporting? Deployment of Tidewater in staging and production environments and showing that data can be consumed with a consumer script Accomplishments of Sprint 12: Comet: * Can generate

Note: This session was not recorded What was the goal of Sprint 11? Comet API and MQ What is the milestone that this sprint is supporting? Implementing Comet’s metadata API and integrating with a message broker (RabbitMQ). Accomplishments of Sprint 11: * Schema loader support that is not dependent on

Note: This session was not recorded What was the goal of Sprint 9? To wrap up the collection processes that are close to being done as well as to wrap up the batch upload process which is the most critical focus at this point for UCSB. The Comet Feature List

What was the goal of Sprint 8? * Support for collections processes * Batch upload * Finalize the Comet Feature List document What is the milestone that this sprint is supporting? The focus was the continued work on the support for collections processes, (which is an MVP item for us), as well as

What was the goal of Sprint 7? Tying off loose ends on collections support and the default workflow as well as getting started on the batch ingest UI. What is the milestone that this sprint is supporting? We finally have the default workflow completely working. We can now push Objects

What was the goal of Sprint 6? * Continuing work for Collections support * Tying up loose ends for work on file download and the default workflow * Subject matter specialists (SMEs) prep for batch workflow What is the milestone that this sprint is supporting? Getting started on batch ingest work and getting

What was the goal of Sprint 5? Workflows, support for collections, EZID minting configuration for UCSD, file download. What is the milestone that this sprint is supporting? Getting workflows into the code base so that we can iterate on it, and as a first step, moving individual objects through a

What was the goal of Sprint 4? To close the loop on FileSets and Collections and to be able to demonstrate those relationships. Configurable metadata was a top priority for this Sprint, and a schema loader was implemented such that a coded metadata config file is readable and configurable based

What was the goal of Sprint 3? Customizable metadata... * that meets our current needs. * that allows for separate per campus metadata configurations. * that drives how object metadata gets stored and indexed. What is the milestone that this sprint is supporting? We have a barebones UCSB metadata config file that is

What was the goal of Sprint 2? 1. Get staging and production deployments up for Comet. * To be able to do this at both campuses. 2. Configure the object storage backend. * Actual deposited files should go into an S3 compatible object store. 3. Configure user authentication using Google Authentication services.