Comet Sprint 47 / Daylight Sprint 19 Review (Sept. 17, 2025 – Oct. 6, 2025)

Fall Workcycle: Sprint 1, Sept 17-Oct 6, 2025

What were the goals of Comet Sprint 47 / Daylight Sprint 19

1. Complete a connected Daylight, Comet, Lark, IIIF, etc., including Daylight production deployment patterns
   a. Daylight/ADRL Lite component registry infrastructure & deployment flow is finalized
   b. Content can be published from Comet to ADRL Lite
   c. Component for Complex Objects
   e. IIIF works for all dependent products
2. Comet MVP Features
   a. Search API endpoint behaves as expected
   b. Remaining API endpoints for images and downloads are done
   c. Validate a disaster recovery plan
3. Environments
   a. Application reliability (particularly Bitnami dependencies and RabbitMQ performance)
4. Reduce Technical Debt
   a. Move off Bitnami
   b. Pull out memcached

What is the milestone that this sprint is supporting?

1. Complete a connected Discovery Prototype (Daylight, Comet, Lark, IIIF, etc.), including Daylight production deployment patterns
2. Continue to implement remaining core Comet features in MVP
3. Validate completed features for Comet that are in MVP scope

Accomplishments of Comet Sprint 47 / Daylight Sprint 19

1. Discovery Prototype (ADRL Lite)
   a. Continued development on components focuses on enhancing functionality and integration with API endpoints.
   b. Improved keyword search behavior
   c. Progress on preparing other Surfliner services to support downloads and IIIF viewing in discovery
2. Complete core Comet features
   a. Made progress toward separating edit, delete, and publish permissions
   b. Addressed issue with Bulkrax imports showing inconsistent results (some files remained pending or lacked characterization, and worker containers occasionally restarted due to suspected out-of-memory (OOM) issues, likely related to FITS processing inside the container).
   c. Established a unified approach for handling IIIF images and file downloads, where Cantaloupe and ADRL Lite both use non-versioned FileMetadata IDs validated through Superskunk for authorization and version resolution
   d. Fixed issue with Solr indexing intermittently failing for objects in a pending state, preventing them from appearing in search results
   e. Established a backup policy for Comet, confirming reliable backup and restoration of production databases (Rails and metadata) and outlining options for S3 redundancy and auditing based on available resources and desired risk tolerance

What’s next?
We're focusing on three key areas. For Comet, we'll work on maintaining component "order" in Bulkrax imports. For Daylight, we'll be adding support for component and subcollection pages. Additionally, we'll be working toward production readiness for Lark and resolving record identifier-to-label resolution across both Comet and Daylight/ADRL Lite.

GitLab link: https://gitlab.com/groups/surfliner/-/cadences/2068118/iterations/2672495