Comet Sprint 36/ Daylight Sprint 8/ Lark Sprint 11 Review

Alissa Pierce -

What was the goal of Comet Sprint 36, Daylight Sprint 8, Lark Sprint 11?

Daylight: The goal was to enhance component development for Daylight, Surfliner’s front-end solution, by building out additional components needed for a clone of a Blacklight styled app.Comet: The focus remained on enhancing key functionalities, refining user workflows and improving bulk management processes, particularly around the Bulkrax ingest and object handling.

Lark: Continue to develop deployment strategies.

What is the milestone that this sprint is supporting?

Daylight: This sprint supports the milestone of delivering a clone of the Blacklight app using Daylight components. Demonstrating the flexibility and portability of a micro frontend’s component-based architecture.

Comet: The sprint supports the milestone of enhancing object and collection handling, improving the user experience, performance and stability.

Lark: Preparing a deployment to ensure readiness and identify needed tasks.

Accomplishments of Sprint Comet Sprint 36, Daylight Sprint 8, Lark Sprint 11: 

Daylight: Despite an unexpected challenge of the official Blacklight app demo being down, Daylight made great progress:

  • Updated the bundler to ensure all pages, not just the index, are copied over during a build.
  • Ensured component elements were nestable.
  • Developed new components including:
    • Object Component (Metadata only)
    • Result-Item Component
    • Pagination Component
    • Prev-Next Component
    • Filter Component
    • Facet-Item Component
    • Button Component
  • Created a Search Results prototype page.
  • Created an Object Display prototype page.
  • Discussed the use of directory paths for component registration.

Comet:

  • Enabled batch publish/unpublish functionality from the objects page.
  • Removed the ability to Add Another Title from collection administration pages.
  • Resolved issues when saving additional fields in collection creation.
  • Completed allowing ARK creation (but not modification) from Bulkrax ingest.
  • Ensured filtering by “Publish Status” functions correctly.

Lark: We identified a critical task that needs to be addressed prior to deployment.

Did we do everything we set out to accomplish?

Daylight: Yes, all planned tasks were completed, including significant component enhancements and the successful demonstration of Daylight's capability to render complex page layouts like the Blacklight clone.

Comet: Yes, key issues were resolved, and performance improvements were made, setting the stage for further enhancements in the upcoming sprints.

Lark: Yes, the team identified necessary tasks needed for a production deployment.

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