Comet Sprint 42/ Daylight Sprint 14/ Lark Sprint 17 Review (Apr 23 – May 12, 2025)

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

Comet

Comet Sprint 41/ Daylight Sprint 13/ Lark Sprint 16 Review (Apr 2, 2025 – Apr 21, 2025)

What were the goal of Comet Sprint 41 / Daylight Sprint 13 / Lark Sprint 16? Daylight: Maturing our components so that they’ll be ready for connectivity in order to get the lifecycle and ecosystem fully presentable and demoable. Lark: Set up Lark and Comet seed data and share JSON-LD serialization

End of Workcycle

Winter 2025 End-of-Workcycle Update for Stakeholders

End of workcycle review for all products that were on sprint during the Winter 2025 workcycle. For each product, we will answer the following questions and give a high-level stakeholder-focused demo. 1. What was the goal of the workcycle? 2. What were the accomplishments of the workcycle? 3. Did we

Comet

Comet Sprint 40/ Daylight Sprint 12/ Lark Sprint 15 Review (Feb 26, 2025 – Mar 10, 2025)

What were the goals of Comet Sprint 40 / Daylight Sprint 12 / Lark Sprint 15? 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

Comet

Comet Sprint 39/ Daylight Sprint 11/ Lark Sprint 14 Review (Feb 12, 2025 – Feb 24, 2025)

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

Comet

Comet Sprint 38/ Daylight Sprint 10/ Lark Sprint 13 Review (Jan 29, 2025 – Feb 10, 2025)

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

Comet

Comet Sprint 37/ Daylight Sprint 9/ Lark Sprint 12 Review (Jan 15, 2025 – Jan 28, 2025)

What were the goals of Comet Sprint 37/ Daylight Sprint 9/ Lark Sprint 12? 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

End of Workcycle

Summer 2024 End-of-Workcycle Update for Stakeholders

End of workcycle review for all products that were on sprint during the Summer 2024 workcycle. For each product, we will answer the following questions and give a high-level stakeholder-focused demo. * What was the goal of the workcycle? * What were the accomplishments of the workcycle? * Did we do everything we

Comet

Comet Sprint 36/ Daylight Sprint 8/ Lark Sprint 11 Review (Aug 28, 2024 – Sep 10, 2024)

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,

Daylight

Comet Sprint 35/ Daylight Sprint 7/ Lark Sprint 10 (Aug 7, 2024 – Aug 27, 2024)

What were the goals of Comet Sprint 35/ Daylight Sprint 7/ Lark Sprint 10? Daylight: The focus was on component development, particularly components that would make up a clone of the Blacklight demo app. Comet: The primary goal was to enhance the filtering capabilities, improve metadata handling, and optimize performance

Comet Sprint 34 / Daylight Sprint 6 / Lark Sprint 9 Review (Jul 24, 2024 – Aug 6, 2024)

What were the goals of Comet Sprint 34 / Daylight Sprint 6 / Lark Sprint 9? Comet: The primary goal was to demo the collection metadata functionalities. Daylight: The focus was on setting up and documenting a local developer work environment. Lark: The aim was a demo deployment. What is the milestone

Comet Sprint 33 / Daylight Sprint 5 / Lark Sprint 8 Review (Jul 10, 2024 – Jul 23, 2024)

What was the goal of Comet Sprint 33 / Daylight Sprint 5 / Lark Sprint 8? Comet: The primary aim was to resolve inconsistencies on the Object’s list display tabs. Daylight: The primary deliverable for this summer's work cycle is an example of Daylight's micro frontend component usage and during this

Winter 2024 End-of-Workcycle Update for Stakeholders

End of workcycle review for all products that were on sprint during the Winter 2024 workcycle. For each product, we will answer the following questions and give a high-level stakeholder-focused demo. 1. What was the goal of the workcycle? 2. What were the accomplishments of the workcycle? 3. Did we

Comet

Comet Sprint 32 / Daylight Sprint 4 Review (Mar 27, 2024 – Apr 16, 2024)

What was the goal of Comet Sprint 32 / Daylight Sprint 4? Comet: The primary deliverable for this workcycle was to facilitate bulk export functionality in order to begin refining round-tripping procedures. Daylight: To demo a broad infrastructure for building small micro frontends for discovery purposes and gluing them together over

Comet

Comet Sprint 31 / Daylight Sprint 3 Review (Mar 13, 2024 – Mar 26, 2024)

What was the goal of Comet Sprint 31 / Daylight Sprint 3? Comet: The primary objective for this workcycle remains consistent: to further refine the bulk export functionality and gather input from stakeholders in order to shift focus to round-tripping procedures. Daylight: The objective was to continue technical discussions and exploratory

Comet

Comet Sprint 30 / Daylight Sprint 2 Review (Feb 28, 2024 – Mar 12, 2024)

What was the goal of Comet Sprint 30 / Daylight Sprint 2 Comet: The goal was to continue refinement of bulk export functionality to solicit stakeholder input before turning attentions on round-tripping procedures. Daylight: The goal was to continue to engage in technical dialogues and exploratory activities concerning the various microfrontends

Comet

Comet Sprint 29 / Daylight Sprint 1 Review (Feb 14, 2024 – Feb 27, 2024)

What was the goal of Comet Sprint 29 / Daylight Sprint 1 Comet: The primary aim was to facilitate bulk export functionality to solicit stakeholder input prior to refining round-tripping procedures. Daylight: The focus was on engaging in technical dialogues and exploratory activities within the team concerning micro frontends for discovery.

Meeting

Prioritization Exercise for 2024 (Results)

The Surfliner Project team convened for a second year on February 6, 2024, for the Surfliner 2024 Prioritization Exercise, employing the “20/20 Vision” prioritization exercise. This session focused on refining the project’s high-level epics and aligning them with strategic objectives. Prior to the exercise, the Tech Leads and

End of Workcycle

Fall 2023 End-of-Workcycle Update for Stakeholders

End of workcycle review for all products that were on sprint during the Fall 2023 workcycle. For each product, we will answer the following questions and give a high-level stakeholder-focused demo. 1. What was the goal of the workcycle? 2. What were the accomplishments of the workcycle? 3. Did we

Shoreline

Shoreline Sprints 27, 28, 29, 30

What was the goal? Sprints 27, 28, 29, and 30 were a part of the Fall 2023 Workcycle. The following goals were set: * Support ingest and display of georeferenced GeoTIFFs. * Resolve bugs around URLS on Shoreline and unpublishing/republishing content. * Support Comet in making bulk ingest of content rock solid.

Comet

Comet Sprint 28 (Oct 18, 2023 – Nov 7, 2023)

What was the goal of Sprint 28? Continuing the workcycle’s theme of making the bulk ingest process as substantial as possible, especially through stakeholder feedback What is the milestone that this sprint is supporting? Ingest of geospatial data and ADRL data in bulk Accomplishments of Sprint 28: * Ensured that

Comet

Comet Sprint 27 (Oct 4, 2023 – Oct 17, 2023)

What was the goal of Sprint 27? A continuation of making the bulk ingest process as rock solid as possible, especially through stakeholder feedback What is the milestone that this sprint is supporting? Ingesting geospatial data and ADRL data in bulk. Accomplishments of Sprint 27: * Users can now add and

Comet

Comet Sprint 26 (Sep 20, 2023 – Oct 3, 2023)

What was the goal of Sprint 26? To continue work on making the bulk ingest process as rock solid as possible. What is the milestone that this sprint is supporting? Ingesting geospatial data and UCSB's ADRL data in bulk. Accomplishments of Sprint 26 The big thing that happened during this

Comet

Comet Workflow Workshop (September 21, 2023)

The Surfliner Project team noticed the need for an in-depth workshop to provide some insights into how Comet’s workflow engine works and can be adapted to new domains. To explore this, we proposed exploring a workflow like digital image capture in a digitalization lab and/or research data to

Comet

Comet Sprint 25 (Sep 6, 2023 – Sep 19, 2023)

What was the goal of Sprint 25? To make the batch import process as rock solid as possible. Both campuses are very interested in ingesting data into Comet. UCSB is interested in ingesting their ADRL data, and UCSD is interested in supporting geospatial ingest. In general, we are interested in