Comet Sprint 46 / Daylight Sprint 18 / Lark Sprint Review (July 30, 2025-August 18, 2025

Summer Workcycle: Sprint 3, July 30-August 18

What were the goals of Comet Sprint 46 / Daylight Sprint 18 / Lark Sprint 18?

1. Discovery Prototype (ADRL Lite):
   a. Complete API work for facets, images, manifests
   b. Complete component work that is not blocked on API development (i.e., IIIF Viewer)
2. Stabilize new QA & Sandbox environments
3. Complete Comet Features (derived from shared remaining MVP feature list)
   a. Configurable metadata schema - nested resources
   b. Access Controls - Refine requirements and implement user/group access controls
   c. Review Complex Object Requirements for ordering on import
4. Infrastructure Decisions & Priority Review
   a. Release strategy
   b. Preview environments - Priority assessment for this work relative to core product features.

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 46 / Daylight Sprint 18 / Lark Sprint 18:

1. Discovery Prototype (ADRL Lite)
   1. Continued IIIF (Universal Viewer) implementation work: reviewed IIIF viewers and tools used by other UC campuses; began a Mirador 3 proof-of-concept (paused).
   2. Integrated the Facet Menu component with the API endpoint.
2. QA Environment Stability
   1. We made substantial progress on application reliability, especially with respect to ingest functionality and performance. Environments using new configurations are much more stable.
   2. In addition to ensuring stability, we’ve been able to document and share performance baselines to give us insight into what real production workloads look/feel like. This helps us answer questions like how many large TIFFs can I process in an importer and how long might it take.
3. Complete core Comet features
   1. Fixed Import Problems
      1. Resolved issues where bulk imports would sometimes fail or get stuck by increasing memory for processing
      2. Fixed errors that prevented items from being properly indexed and searchable
   2. Improved User Access Controls
      1. Discussed basic user roles and group permissions so different people can have appropriate access levels
      2. Set foundation for controlling who can view or edit materials
   3. Enhanced Display and Information
      1. Fixed how object types are displayed to show user-friendly names instead of technical codes
      2. Ensured all item properties and details show up properly on both individual item and collection pages
      3. Improved how the system handles technical file information to prevent data loss
   4. Resolved System Reliability Issues
      1. Fixed importers that incorrectly showed as “complete” when work was still pending
      2. Eliminated unnecessary system loading that was causing errors
      3. Strengthened file processing to handle complex metadata mapping
4. Things we needed to address that couldn’t wait
   a. We have been using third-party Helm charts for services such as Solr, PostgreSQL, Redis, and Memcached. These charts were written and maintained by Bitnami. Bitnami has now been purchased by Broadcom, which is discontinuing these community charts (https://gitlab.com/surfliner/surfliner/-/issues/1929). This has created a large amount of unplanned work as we determine alternatives and begin migrating services.

What’s next?
This was the last sprint of the workcycle and the team will be taking time to synthesize the results and outcome. We’ll be performing a critical path review across all products before the start of our next workcycle. This will be essential to closing MVP feature gaps.

GitLab link: https://gitlab.com/surfliner/surfliner/-/cadences/2065753/iterations/2603192