Sprint Review

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

Comet

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

Comet

Comet Sprint 37/ Daylight Sprint 9/ Lark Sprint 12 Review

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

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

Comet Sprint 32 / Daylight Sprint 4 Review (March 27–April 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 (March 13, 2024–March 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 29 / Daylight Sprint 1 Review (February 14–February 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.

Comet

Comet Sprint 28 (October 18, 2023–November 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 (October 4, 2023–October 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 (September 20, 2023–October 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 Sprint 25 (September 6, 2023 – September 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

Shoreline

Comet Shoreline Pipeline MVP - Offcycle Summer 2023

The goal of these two offcycle sprints during the 2023 summer was to get the pipeline for ingesting into Comet and publishing to Shoreline working. We can successfully ingest to Comet and publish to Shoreline!

Comet

Comet Sprint 24 (May 3, 2023 – May 16, 2023)

What was the goal of Sprint 24? * To complete the work that we had scoped for the new permission structure (Visibility model) for Objects. There are now different levels to choose from, and these permissions are global (i.e they also impact other systems that this object will appear in)

Comet

Comet Sprint 23 (April 19, 2023 – May 2, 2023)

What was the goal of Sprint 23? To continue and complete the critical dependency update work for Comet (Hyrax Ruby 3.2) and to obtain alignment on the baseline stock “Visibility” model for Comet. There is more work to be done to get the Bulkrax Exporter to work, and there

Comet

Comet Sprint 22 (April 5, 2023 – April 18, 2023)

What was the goal of Sprint 22? In our last posting, we shared that we wanted to focus our efforts on the Ruby and Rails upgrades for all Surfliner products. The upgrades were completed for Lark, Shoreline, and Starlight, but Comet’s upgrade is still in progress. While there is

Comet

Comet Sprint 21 (March 15 - April 4, 2023)

What was the goal of Sprint 21? For the first two Surfliner Spring Workcycle sprints, we felt that it was important to work on technical debt and maintenance issues, most especially the Ruby and Rails upgrades for all Surfliner products. For the maintenance tasks, it should be noted that the

Comet

Comet Sprint 20 (December 2 - December 20, 2022)

What was the goal of Sprint 20? The goal of this Sprint was to continue work on batch ingest and export, and tying in ingest through Comet into the geospatial platform, Shoreline. Accomplishments of Sprint 20: * Updated the GBL1.0 to Aardvark JSON converter to meet Shoreline needs * Produced a

Comet

Comet Sprint 19 (November 16 - November 29, 2022)

What was the goal of Sprint 19? The goal for the overall work cycle is to shore up batch work for ingest and extend it to get batch round trip working so that you can do an export of batch metadata in some format, make changes in the exported format

Comet

Comet Sprint 18 (November 3 - November 15, 2022)

What was the goal of Sprint 18? The goal for this Sprint (for the overall work cycle) is to shore up batch work for ingest and extend it to get batch round trip working so that you can do an export of batch metadata in some format, make changes in

Comet

Comet Sprint 17 (August 3 - August 16, 2022)

What was the goal of Sprint 17? * Pushing collections to the OAI endpoint (tidewater) and making the set harvestable from OAI * IIIF Image Server (Cantaloupe) wired into staging and production environments for each campus * Workflow-driven “publish” from Comet to the Shoreline geodata platform What is the milestone that this sprint

Comet

Comet: Sprint 16 (July 20, 2022 –August 2, 2022)

What was the goal of Sprint 16? * Editing and adding descriptive and other user defined metadata for existing objects * Running workflow and event triggered work (characterization, access derivatives) * Assigning permanent identifiers (primarily interested in the short term in ARKs as canonical IDs) * Publishing that content to a public access platform

Comet

Comet: Sprint 15 (July 6, 2022 - July 19, 2022)

What was the goal of Sprint 15? * Adding/editing descriptive and other user defined metadata * Running workflow and event triggered work (characterization) * Assigning permanent identifiers (ARKs) * Publishing to a public access platform (OAI, IIIF, Shoreline) What is the milestone that this sprint is supporting? To have a robust publish lifecycle

Comet

Comet: Sprint 14 (June 22, 2022 - July 6, 2022)

What was the goal of Sprint 14? * Uploading content singularly and in batch * Editing and adding descriptive and other user defined metadata for existing objects * Running workflow and event triggered work (characterization, access derivatives) * Assigning permanent identifiers (primarily interested in the short term in ARKs as canonical IDs) * Publishing that

Starlight

Starlight: Sprint 13 (April 13- 26, 2022)

What was the goal of Sprint 13? The Surfliner team has been experimenting with regular dedicated off-cycle sprints to focus on maintenance, upgrades, and new features for in-production products such as Starlight (in production since 2019). The goals of Sprint 13 were a combination of all of these things. A

Shoreline

Shoreline: Sprint 24 (March 2-15, 2022)

(This session was not recorded) What was the goal of Sprint 24? For Sprint 24, the following goals were set: * Determine the formatting of the URL in the CSV to support downloads of original datasets * Continue getting UCLA up to speed on Surfliner devops work * Update Geoserver to 2.19.