Combined Lark & Starlight Sprint Review Recording: March 8, 2019 

What was the goal of Sprint 2?
Get the Starlight code deployed to our local staging servers, set up support single sign on with Shibboleth, continuing work on uploading and displaying PDFs as exhibit objects, and improving the test suite.

What is the milestone that this sprint is supporting?
Milestone 1 is to have an initial instance of the Spotlight platform in production for both campuses.

Accomplishments of Sprint 2:
We built an initial implementation of authentication support for Shibboleth. While this is not yet deployed to a staging server as we had hoped, the functionality and configuration is in place for us to do so

We added the ability to generate sitemaps for the application upon deployment, which also triggers a ping to major search engines like Google and Bing to crawl the site.

We have added the ability to integrate Google Analytics into a Starlight application by supplying the necessary configuration.

We built a Solr docker service that we can use, and share, for both Starlight and Lark. This allows us to do CI testing in Gitlab for both projects. This included contributions from both Lark and Starlight teams.

We upgraded the Starlight application to Rails 5.2, the most current available stable version. This included migrating the test suite, along with a variety of other configuration changes. This prepares Starlight well for an eventual upgrade to Rails 6, which will be out in the next few months.

We continued to work on setting support for uploading PDF as exhibit objects though have not been able to close these tickets since they have not been deployed to our local environments for testing.

Did we do everything we set out to accomplish?
Nope. Getting Shibboleth setup at UCSB has been a blocker, but we have both a backup plan and have pulled in some additional help on campus to help get the blocker cleared. That being said, our primary goal for Sprint 3 is to get Starlight deployed to production for UCSB and deployed to staging for UCSD. This means that we will be working things like branding, in addition to closing out the remaining tickets from Sprint 2 and finishing up the work related to supporting PDFs as exhibit objects.

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