Comet Sprint 51 / Daylight Sprint 23 Review (Feb. 11, 2026–March 2, 2026)

Winter Workcycle: Sprint 2, Feb. 11, 2026–March 2, 2026

What was the goal of the Comet Sprint 51 / Daylight Sprint 23 (Winter 2026, Sprint 2)? 

Advance discovery integration (so we deliver a connected system at the end of the workcycle) and unblock production data migrations.

Agile process notes 

1. Made a sprint rollover playbook to give us a little more planning time for sprint end/start  
2. The rollover end time was used to help get remaining reviews done and clear QA items
3. Clear signal (objective and subjective) that this is a good improvement
4. Even with some folks attending the Code4Lib conference, we felt this was very useful! 

What is the milestone that this sprint is supporting? 

1. What is the milestone that this sprint is supporting? 
2. Discovery Integration 
   1. Publishing from Comet to discovery prototype (immediate scope is images for simple objects)
   2. Preparing for UCSD discovery development/integration
      1. Plan: Implement end-to-end features in discovery prototype, then modularize to make it usable for multiple environments. We’ve already done a lot of adjacent work to enable this (filetsets, superskunk metadata, collections).
3. Discovery Development
   1. Moving requirements forward to complex object, collections/sub-collections
   2. Understanding API behavior
4. Comet Operational Stability
   1. Advancing operational stability through reliable ingest, workflows, and publishing controls
5. Finalizing Disaster Recovery
   1. Comet database restores
6. Sending metadata to EZID (upon approval for simple ark metadata and does not include the later-stage publication metadata)

Accomplishments of Comet Sprint 51 / Daylight Sprint 23 (Winter 2026, Sprint 2) 

1. Discovery Integration (Margaret)
   1. Initial ADRL Lite work to harvest records published from Comet
   2. Initial Superskunk metadata implementation to support ADRL Lite
   3. Overall architecture and strategy for parallel UCSB / UCSD / shared discovery development
2. Discovery Development (Alissa)
   1. Exploration of API; focusing on collections and complex objects
   2. Improving usability; Improved pagination and facet display. New list result display options. A user can now select list view or gallery view. The breadcrumb menu’s collection link takes the user to the beginning of a collection page
3. Comet Operational Stability (Margaret, Gabriela)
   1. MVP Ingest Blockers
      1. Finished image selection logic in the IIIF viewer to prioritize Service-Files over other fileUse types, with sensible fallback behavior (for images)
      2. Aligned thumbnail generation with the same file preference logic
   2. New Bugs
      1. Fixed metadata export so component objects within compound objects are included in spreadsheets
      2. Resolved workflow dashboard issues where task links were broken and paging did not update results
      3. Fixed Bulkrax importer error preventing collection creation during batch ingest
   3. Additional Enhancements
      1. Added support for complex metadata fields in batch export, preserving existing ingest structure
      2. Enabled publish/unpublish controls for collections
      3. Ensured ADRL Lite is available as a publishing target in Comet
      4. Removed outdated visibility labels (added new labels in Sprint 1)
      5. Added redirects to a login page when attempting to access any page in Comet.
4. Finalizing disaster recovery (Alex and Michael C.)
   1. Documented and implemented database backup and recovery strategy
   2. Improved durability of data retention and storage

What’s next? [if applicable]

• Complete integration and publishing from Comet to ADRL Lite (with the scope note above)
  • Focused work around controlled value labels

GitLab link:https://gitlab.com/groups/surfliner/-/cadences/2070290/iterations/2724391