(Page 4)

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

Shoreline

Shoreline has launched!

We now have a Shoreline product available online, which we are calling Geodata. The UCSB instance is here: http://geodata.library.ucsb.edu The UCSD instance is here: https://geodata.ucsd.edu This is the Minimum Viable Product (MVP), so it doesn't have full branding and doesn't have many features

UC Santa Barbara Library Impact Report

The Project Surfliner collaboration was featured in the latest UC Santa Barbara Library Impact Report. To download the full report, please visit www.library.ucsb.edu/annual-reports.

Project Surfliner: Building the Tracks before the Train (CNI Spring 2020)

Project Surfliner: Building the Tracks before the Train (presentation at CNI Spring 2020 Virtual Membership Meeting) Tim Marconi Director, Technology and Digital Experience University of California, San Diego Chrissy Rissmeyer Director, Digital Library Development University of California, Santa Barbara In November 2018, the University of California (UC) San Diego and

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

Shoreline

Shoreline: Kickoff Meeting (January 29, 2020)

Shoreline is a geospatial materials platform based on GeoBlacklight, and is named after the Southern Pacific train that ran between Los Angeles and San Francisco from 1927 until 1931. What has happened up to now? In Fall 2019, the Shoreline team prepared for the product’s first development cycle (which

Samvera Connect 2019 Poster

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 containerization of

Surfliner: Update: August 7-21 Sprint Cycle

Hi Surfliner stakeholders, experts, and interested parties! Quick update on the restarting of sprints this week: Orange Empire: Orange Empire is an IT Operations-focused project to get a IIIF (International Image Interoperability Framework) server stood up, run reliably in multiple environments, and explore how we can leverage that technology within

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 global

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.

Sprint Review

Starlight: Sprint 4 (March 25-April 5, 2019)

What was the goal of Sprint 4? Get the Starlight code deployed to our both campus staging servers and UCSB production servers, testing new features in staging environment, theming, and setting up Shibboleth. What is the milestone that this sprint is supporting? Milestone 1 is to have an initial instance

Sprint Review

Lark: Sprint 4 (March 25-April 5, 2019)

What was the goal of Sprint 4? The sprint had two main goals: First and foremost, we set out to complete cloud-native deployments Lark into both campus’s environments. Second, we wanted to take our first steps toward configurable metadata models. This a key design goal and deliverable for the

Sprint Review

Starlight: Sprint 3 (March 11-22, 2019)

What was the goal of Sprint 3? Get the Starlight code deployed to our both campus staging servers and UCSB production servers, supporting single sign on with Shibboleth, and improving the test suite. What is the milestone that this sprint is supporting? Milestone 1 is to have an initial instance

Lark

Lark: Sprint 3 (March 11-22, 2019)

What is the goal of sprint 3? The sprint’s focus was on three areas: * Deployment * Documentation * Support expanded labels What is the milestone that this sprint is supporting? Milestone 1 is to have an initial stand-alone platform where we can create, edit, and retrieve authority records. Accomplishments of Sprint

Roles

What is a Product Owner?

Let’s start with the who. Who are the product owners? Currently, we have two products that we’re working on: Lark (the authority records platform) and Starlight (the digital exhibits platform). Each product has a product owner -- for Lark, it’s me (Jessica Hilt, UCSD) and Starlight, it’

Sprint Review

Lark: Sprint 2 (February 25-March 8, 2019, 2019)

What is the goal of sprint 2? We hoped to get to our first milestone -- an initial stand-alone platform where we can create, edit, and retrieve authority records. We did achieve this goal and we’re currently waiting to deploy. What is the milestone that this sprint is supporting?