Comet Sprint 42/ Daylight Sprint 14/ Lark Sprint 17 Review (Apr 23

Comet Sprint 42/ Daylight Sprint 14/ Lark Sprint 17

In today’s recording, you will hear a reference to ADRL Lite. The following provides a brief explanation of what it entails.

Unlike many digital asset management systems, Comet is a purely staff-facing platform. Authorized staff use Comet to manage digital objects and associated metadata, but to make that content available to patrons, they need to publish it to a discovery system. The intent is for Comet to eventually publish content to any number of other systems, both internal and external—for discovery and access, but also for other purposes such as preservation.

While with Daylight, the Surfliner team has been working on shared components that could be re-used in multiple discovery systems, we’ve also been working on integrating those components into a complete discovery platform, along with the necessary back-end APIs to provide search results and display information on individual records. This first-generation Surfliner/Comet discovery platform is what we’ve been calling “ADRL Lite”, since the goal for its initial deployment is to let UCSB retire the legacy Alexandria Digital Research Library, migrating that content into Comet; but it’s also the prototype for future discovery systems we build to give patrons access to content managed in Comet—including the system we’ll be building out later this year for UCSD, to support moving from UCSD’s current DAMS to Comet—and we expect nearly all the work we do on ADRL Lite to carry over directly to those systems.

What were the goal of Comet Sprint 42 / Daylight Sprint 14 / Lark Sprint 17?

Comet: Setting up Comet and Lark seed data and wrapping up nested resources work, finalizing requirements for QA and production environments, and retiring the old staging environments.

Daylight: Complete more enhancements of accessibility and responsiveness for components.

What is the milestone that this sprint is supporting?

Comet: Getting file replacement/updates working properly, addressing outstanding bulk import issues, resolving outstanding unreliable tests, as well as identifying high-values tests

Daylight: Preparing for future integrations with API endpoints that support a connected Daylight

Accomplishments of Comet Sprint 42 / Daylight Sprint 14 / Lark Sprint 17:

Comet:

File characterization is now updated whenever a fileSet is replaced.
Resolved Bulkrax ingest with fileSet error
Fixed issue with the automated Comet test suite fails (unreadable schema in config/metadata)
Reconfigured Hyrax to use local FITS
Improved RabbitMQ connection to be more reliable and performant in test
Ported VersionedShrine to upstream Valkyrie-shrine
Publishing from Comet to Shoreline is working again (downgraded geoserver)

Daylight:

Quicklinks Component: Added an initial README for user guidance, and reviewed accessibility requirements
Results Complex Pager Component: Implemented responsive behavior and enhanced accessibility with semantic HTML, ARIA attributes, improved tabbing, and color contrast
Results List Component: Confirmed accessibility compliance and added ARIA roles to improve inclusivity
Results Applied Parameters Component: Ensured elements stack on smaller screens, along with accessibility updates
Results Simple Pager Component: Enhanced accessibility with ARIA roles and verified keyboard navigation
Advanced work on our Figma design system

What’s next?

Comet:
Completing our environment design efforts, and moving forward with essential Comet work based on the feature matrix and backlog prioritization

Daylight:
Preparing for future integrations with API endpoints that support a connected Daylight

GitLab link: https://gitlab.com/surfliner/surfliner/-/cadences/2062403/iterations/2541238