Comet Sprint 58 / Daylight Sprint 30 Review (Aug. 2, 2026 – Aug. 21, 2026)

What was the goal of the Comet Sprint 58 / Daylight Sprint 30

Implement high-priority discovery features for UCSB (post launch) and for UCSD; continue to support Comet production and UCSD data migration features.

What is the milestone that this sprint is supporting? 

1. Discovery Integration 
2. Discovery Development
3. Comet Migration Readiness
4. Infrastructure and Workflow Resilience

Accomplishments of Comet Sprint 58 / Daylight Sprint 30

1. Discovery Integration
   1. Shared vs discrete schema strategy (short and long term)
   2. Controlled vocabulary strategy
   3. API performance improvements for large result sets
2. Discovery Development
   1. Removed unused footer component that triggered errors in the deployment logs
   2. Bug fixes; continued work to clean up UCSB collection member displays and bettering behavior to display 404 page, if user attempts to explore ARKs that are not available 
   3. UCSD Discovery Demo
      1. Downloads list:
         1. Updated the Object view to include a “Downloads” list for objects with service files
      2. Collection Landing page improvements:
         1. Updated search page to allow for the display of items within a specific collection
         2. Updated the “From the collection” section to display vibrant panels instead of simple links
      3. Complex Object view:
         1. Updated Complex Object view to display as a manual carousel that allows users to navigate through an object’s subcomponents (children) via a pager or link tree.
         2. The CO update includes support for showing multiple instances of Universal Viewer (e.g., for COs with multiple images)
         3. Added permalinks for subcomponents
3. Comet
   1. Gating publishing without approval (in QA)
   2. Exporter support for technical metadata (in QA)
   3. Recursive Publishing / Unpublishing of child objects
   4. Change the downloads controller to not be File Use based
   5. Fix issue with visibility flags
   6. DOI requirements synthesis
4. Shoreline
   1. Forward progress on fixing a publication issue (consumer can no longer fetch files from Comet)
   2. Strategy and testing for moving geo objects between comet projects and understanding implications especially for publication (essentially being able to move between a combined approve + publish step and one that treats those actions independently.
   3. Exploratory testing for open index map support and requirements formation. 
5. Infrastructure and Workflow Resilience
   1. Investigation of rake tasks to support bulk republish from comet to shoreline (possibly other platforms)
   2. UCSB exploring Solr 9 deployment options

What’s next?

• Fall 2026 Workcycle Prioritization & Planning

GitLab link: https://gitlab.com/surfliner/surfliner/-/cadences/3075211/iterations/3931225