Comet Sprint 39/ Daylight Sprint 11/ Lark Sprint 14 Review

What were the goals of Comet Sprint 39/ Daylight Sprint 11/ Lark Sprint 14?

Comet: QA Bulkrax bug fixes. Issues around the updates/deletes. Take action on production stability, staging environments decisions, and DevOps-related issues FITS/Kaniko etc).

Daylight: Continue to build interactivity between components, focusing on progressive enhancement for demos for search and results components, sorting 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: The continuation of rethinking our environment configurations, and conducting comprehensive testing of large collections and FileSets via Bulkrax to identify and resolve any existing issues.

Daylight: Establishment of a shared component library. With a focus on building interactivity between components and ensuring progressive enhancement and furthering API requirements documentation.

Lark: Being able to test Lark with real data and survey the scope of related work.

Accomplishments of Comet Sprint 39/ Daylight Sprint 11/ Lark Sprint 14 

Comet

• Team members met and agreed on a seed dataset that is to be shared between review, demo and sandbox environments.
• Team members decided that review environments will be generated on demand rather than automatically.
• Sorted out registry issues in CI.
• For Bulkrax imports, the Import status no longer shows “Validated” immediately after clicking "Create and Validate". Users now see “Validation Pending”.

Daylight

• Enhanced interactivity between search and results components.
• Refactored multiple components (Results-Simple-Pager, results-top-pager, results-list, object-metadata, search-bar).
• Completed onboarding tasks: "Hello World" component and local dev setup.
• Added API documentation and assisted with CI updates.

Lark

• Fixed issues with deploying Lark which were discovered after the migration to Rails.
• Refactored JSON‐LD API behaviors so that they could be shared between Superskunk and Lark.

Did we do everything we set out to accomplish? 

Comet: The team continues to make good progress. We will continue with our discussions in regard to the stability of the staging and productions environments, as well as testing memory issues with large ingests.

Daylight: We continue to make progress developing a shared component library. Onboarding was successful, API documentation was expanded, and interactivity between components was improved with a focus on progressive enhancement, particularly for search and results functionality.

Lark: We made reasonable progress towards our goal of being able to ingest data into Lark by the end of the workcycle.

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