Comet Sprint 52 / Daylight Sprint 25 Review (Mar. 3, 2026–March 23, 2026)

Winter Workcycle: Mar. 3, 2026–Mar. 23, 2026

What was the goal of the Comet Sprint 52 / Daylight Sprint 24 (Winter 2026, Sprint 3)? 

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

What is the milestone that this sprint is supporting? 

1. Discovery Integration 
   1. Publishing from Comet to discovery prototype
   2. Preparing for UCSD discovery development/integration
2. Discovery Development
   1. Exploration into advancing front-end development
3. Comet Metadata and Display Consistency
   1. Improving the consistency and reliability of how metadata and content are handled and displayed across Comet. This work ensures that what users see, export, or manage behaves in a more predictable and aligned way throughout the system.
4. Finalizing Disaster Recovery
   1. Finalize UCSB backup/restore strategy for Comet databases
5. Supporting Surfliner deployment at UCSC

Accomplishments of Comet Sprint 53 / Daylight Sprint 25

1. Discovery Integration
   1. Collections and works (including filesets and files) can now be published from Comet to discovery
   2. ADRL Lite codebase folded into the Surfliner monorepo in prep for sharing / customization across campuses
   3. New name chosen for discovery prototype known until now as “ADRL Lite”: “Golden Gate”
2. Discovery Development
   1. Exploration completed on utilizing component lifecycles for the object page.
   2. Successfully explored creating a full tree of object/collection members using the Members API
   3. Explored additional ways to gather metadata from Members API vs. using the Resources API
   4. Explored how to implement a “slideshow” version of members data (akin to how UCSD DAMS4 “components” currently work)
   5. Planned a path forward for allowing campuses to customize the CSS of shared MFEs
3. Comet Metadata and Display Consistency
   1. Metadata & Authority Handling
      1. Refactored authority handling into the shared SurflinerSchema layer
      2. Introduced a new #authority_for(property) method for retrieving authority objects
      3. Updated behavior to return nil instead of raising errors, reducing exception handling in the codebase
   2. Controlled Vocabulary Display
      1. Updated Object and Collection show pages to display both Label (human-readable value) URI (controlled vocabulary reference)
   3. IIIF Viewer Improvements
      1. Implemented fallback logic for image display in the IIIF viewer
         1. ServiceFile → IntermediateFile → OriginalFile
      2. Fixed issues where TIFF and some JPEG images were not rendering in the viewer 
   4. Thumbnail Generation Fixes
      1. Resolved inconsistent thumbnail creation for TIFF images
      2. Improved reliability of derivative generation for TIFF format
   5. CSV Export Improvements
      1. Fixed arbitrary row ordering in exported CSVs for Collections, Objects, FileSets, and files
      2. Ensured exports are structured in a consistent, usable order for downstream workflows
4. Finalizing disaster recovery
   1. Replaced deprecated backup feature with cloud plugin
5. Supporting Surfliner deployment at UCSC
   1. Met with UCSC team to validate their deployment strategy and discuss timelines

What’s next?

• Discovery integration
  • Unpublishing
  • Renaming ADRL Lite to Golden Gate
  • Modularizing Golden Gate for campus-specific customization
• Discovery development
  • Updating Golden Gate to share controlled vocabulary display label lookup logic and data with Comet
• Comet Metadata and Display Consistency
  • Loading TSVs of authorities into both Comet and discovery platforms
  • Improved support for very long lists of authorities
• Finalizing Disaster Recovery
  • Finalizing and formally documenting UCSB process for Comet database backups and disaster recovery
• Sending metadata to EZID

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