Sprint Review

A collection of 84 posts

Comet

Comet: Sprint 1 (Mar 31 – Apr 13, 2021)

What was the goal of Sprint 1? To deploy a full stack and save a “work” in a staging capacity with minimal metadata. We will measure success as: being able to deposit something with a title without the stack throwing an error at us. What is the milestone that this

DevOps

DevOps: Sprint 5 (January 27-February 9, 2021)

Note: We did not record a formal sprint review because the nature of the work accomplished is not something that translates well to a demo. What was the goal of Sprint 5? Sprint 5 was scheduled as a discrete sprint when we were off workcycle. We wanted to get both

Shoreline

Shoreline: Sprint 20 (Dec. 2-15, 2020)

(This session was not recorded) What was the goal of Sprint 20? For Sprint 20, the following goals were set: * Document the purpose of Shoreline * Make changes to the ingest script based on the modified metadata workflow that uses a CSV and ISO XML * Test CSV to ISO XML script

Shoreline

Shoreline: Sprint 19 (Nov. 12 - Dec. 1)

This session was not recorded. What was the goal of Sprint 19? For Sprint 19, the following goals were set: * Finalize an enhanced, improved metadata workflow methodology that speeds up editing and quality control * Document the purpose of Shoreline * Check how changes to bounding boxes are affected by changes to

Shoreline

Shoreline: Sprint 18 (Oct. 21 - Nov. 10)

This session was not recorded. What was the goal of Sprint 18? For Sprint 18, the following goals were set: * Develop an enhanced, improved metadata workflow that speeds up editing and quality control * Document the purpose of Shoreline * Check how changes to bounding boxes are affected by changes to shapefile

Shoreline

Shoreline: Sprint 17 (October 7-20, 2020)

There was no recording made of this session. What was the goal of Sprint 17? For Sprint 17, the following goals were set: * Get a signal out of GeoServer and Solr to determine status (functioning vs. offline) * Fix the GeoServer stability issue * Determine metadata principles for Shoreline (handling original metadata;

DevOps

DevOps: Sprint 4 (July 29-August 11, 2020)

Note: We did not record a formal sprint review because the nature of the work accomplished is not something that translates well to a demo. What was the goal of Sprint 4? Sprint 4 was the last sprint of the Summer 2020 workcycle. The top priority of this sprint was

Shoreline

Shoreline: Sprint 16 (July 29 - August 11, 2020)

What was the goal of Sprint 16? For Sprint 16, the following goals were set: * Finalize short-term workflow for ingesting data into UCSB and UCSD Geodata * Determine the look and feel of UCSB Geodata * Add rights metadata field to Geodata interface * Determine stakeholder priorities for next development cycle * Add QA/

DevOps

DevOps: Sprint 3 (July 15-28, 2020)

Note: We did not record a formal sprint review because the nature of the work accomplished is not something that translates well to a demo. What was the goal of Sprint 3? The goals of sprint 3 were to finish consolidating the duplicate shell scripts and the Starlight deploy pipelines,

Shoreline

Shoreline: Sprint 15 (July 15-28, 2020)

What was the goal of Sprint 15? For Sprint 15, the following goals were set: * Continue meetings with stakeholders to update them on the progress of Shoreline and to hear their thoughts about new features; * Review input from stakeholders at both campuses; * Diagram workflows at CU Boulder and Cornell following

DevOps

DevOps: Sprint 2 (July 1-14, 2020)

Note: We did not record a formal sprint review because the nature of the work accomplished is not something that translates well to a demo. What was the goal of Sprint 2? There wasn’t really a specific goal for this sprint outside of working through the outstanding DevOps issues

Shoreline

Shoreline: Sprint 14 (July 1-14, 2020)

What was the goal of Sprint 14? The goals of this sprint include: * Meet with stakeholders to update them on the progress of Shoreline and to hear their thoughts about new features * Speak with other institutions about their ingest workflows * Diagram workflows at CU Boulder and Cornell following meetings with

DevOps

DevOps: Sprint 1 (June 17-30, 2020)

Note: We did not record a formal sprint review because the nature of the work accomplished is not something that translates well to a demo. What was the goal of Sprint 1? There wasn’t really a specific goal for this sprint outside of working through the outstanding DevOps issues

Shoreline

Shoreline: Sprint 13 (June 17-30, 2020)

What was the goal of Sprint 13? To gather information from stakeholders at UCSB and UCSD as well as learn about how other institutions ingest data into their GeoBlacklight instances.  Also, to discuss possible object storage locations, both for short term and long term. What is the milestone that this

Sprint Review

Shoreline: Sprint 12 (April 1-14, 2020)

What was the goal of Sprint 12? The goals for the sprint included: * Deploy both UCSD and UCSB production instances * Enable submission of the contact form to campus-specified emails * Determine metadata workflows prior to ingesting materials * Document the ingest process What is the milestone that this sprint is supporting? This

Sprint Review

Shoreline: Sprint 11 (March 18-31, 2020)

What was the goal of Sprint 11? The goals for the sprint included: * Perform a Gap Analysis on Shoreline now that objects can be ingested * Finalize the branding of campus instances * Finalize the contact form functionality of campus instances * Determine metadata workflows as we begin to ingest data * Enable download

Sprint Review

Shoreline: Sprint 10 (March 4-17, 2020)

What was the goal of Sprint 10? The goals for the sprint included: * Ingesting objects into Shoreline * Discussing metadata workflows for ingest * Discussing platform architecture * Reviewing the Gap Analysis document once objects are ingested What is the milestone that this sprint is supporting? This sprint is supporting the development of

Sprint Review

Shoreline: Sprint 9 (Feb. 19 - Mar. 3, 2020)

What was the goal of Sprint 9? The goals for the sprint included: * Ingesting objects into Shoreline * Exploring the options for Shoreline architecture * Enabling local campus branding * Implementing local branding for the two campuses * Discussing how permanent IDs are handled Much of the work continued to be exploratory during this

Sprint Review

Shoreline: Sprint 8 (Feb. 5 - 18, 2020)

What was the goal of Sprint 8? Sprint 8 was the initial development sprint for Shoreline.  The goals for the sprint included: * Deploying Shoreline to UCSB and UCSD staging servers * Exploring how objects can be ingested into Shoreline * Creating a contact link * Discussing how local campus branding can be enabled

Sprint Review

Starlight Sprints 9 & 10 (August 7 - September 3, 2019)

What was the goal of Sprints 9 & 10? Goals for Sprints 9 & 10 included continued bug and theming work, including the development of a new Surfliner theme and support for getting UCSD’s instance deployed in a production environment. Additionally, these sprints included laying the groundwork for the

Sprint Review

Starlight: Sprint 8 (July 22–August 2, 2019)

What was the goal of Sprint 8? To resolve many of the bugs and theming issue reported since the Starlight code was deployed for feedback at both campuses, to continue associated user testing, and to work on outstanding maintenance work. What is the milestone that this sprint is supporting? Milestone

Starlight

Starlight: Sprints 6 & 7 (April 22 - May 18, 2019)

What was the goal of Sprints 6 & 7? The ultimate goal of these sprints to have the code at a place where stakeholders could begin working in their respective installations. To get there, this required additional testing and bug fixes, campus theme refinement (including the ability to apply a

Sprint Review

Lark: Sprints 6 & 7 (April 22 - May 18, 2019)

GitLab links: https://gitlab.com/surfliner/surfliner/-/milestones/17 https://gitlab.com/surfliner/surfliner/-/milestones/14

Starlight

Starlight: Sprint 5 (April 8-19, 2019)

What was the goal of Sprint 5? Testing in staging environment at both campuses, bug fixes, theming (including the ability to apply a global theme), and getting Shibboleth configured for UCSB. What is the milestone that this sprint is supporting? Milestone 1 is to have an initial instance of the

Lark

Lark: Sprint 5 (April 8-19, 2019)

What is the goal of sprint 5? The sprint’s focus was on integrating the Postgresql persistence layer and Helm/Kubernetes deployment. What is the milestone that this sprint is supporting? The Milestone 1 is to have an initial stand-alone platform where we can create, edit, and retrieve authority records.