Comet Sprint 38/ Daylight Sprint 10/ Lark Sprint 13 Review

What were the goals of Comet Sprint 38/ Daylight Sprint 10/ Lark Sprint 13?

Comet: We have a number of bugs which have been identified in Bulkrax; we would like to fix these and/or confirm that earlier fixes work. There are a lot of discussions we are hoping to have regarding production stability and staging environments, which we hope will produce more actionable tickets for later in the workcycle.

Daylight: We would like to build interactivity between components, focusing on progressive enhancement for demos etc.

Lark: Merging some of the related work around deploying it to production, and ideally (by the end) at least be able to seed some data into Lark through a CI task.

What is the milestone that this sprint is supporting?

Comet: Continue the ongoing analysis of the stability and performance of our staging and production environments, while conducting comprehensive testing of large collections and FileSets via Bulkrax to identify and address any existing issues.

Daylight: This sprint supports the milestone of establishing a shared component library by focusing on building interactivity between components and ensuring progressive enhancement.

Lark: Providing a demo-able API for Lark which can be used to evaluate its current status and what future work is needed.

Accomplishments of this Sprint

Comet

• Fixed the issue with the Bulkrax Importer ignoring user supplied Source IDs.
  • Issue was caused by UTF-8 Unicode BOM (byte order mark); support has now been added
• Users can now filter statistics on the user Dashboard by a date range
• Improved the deployment stability/reliability by deploying RabbitMQ external to the cluster

Daylight

• Created a visual diagram to identify shared elements and reusable patterns across the app’s pages.
• Began establishing baseline accessibility standards for all shared components.
• Held discussions to ensure solid backend-to-frontend communication for shared components through an API.
• Began to program interactivity between components so that components can be updated when users interact with the page.

Lark

• Completed the initial migration to Rails.

Did we do everything we set out to accomplish?

Comet: Yes, the team continues to refine the import process, and is making good progress narrowing the definition of what it means to be in production.

Daylight: Yes, we continue to make progress developing a shared component library by identifying commonly reused components, refining interactivity between the components and documenting what we’ve discovered.

Lark: We got the initial Lark Rails conversion done, which was the main thing we hoped to accomplish. We are still working on the follow-up work which has fallen out of that.

GitLab link: https://gitlab.com/surfliner/surfliner/-/milestones/118