Products

The Project Surfliner team is collaboratively developing a number of products. All the products are also named after historic intra-California train routes.

Comet

Comet is a staff-facing digital object management platform based on Hyrax, a front-end application that provides a user interface for common repository features.

Comet was named after the Sacramento Northern Train that operated between Chico to San Francisco via Sacramento from about 1928 to 1940.

Comet Implementation Status can be found here.

Product Owner: Gabriela Montoya (UCSD) | Tech Lead: tamsin johnson (UCSB)

Lark

Lark is a shared authority control platform and API.

Lark was named after the Southern Pacific Lark Train that operated overnight between Los Angeles and San Francisco via San Luis Obispo from 1941 to April 1968.

Product Owner: Arwen Hutt (UCSD) | Tech Lead: Margaret Kibi (UCSB)

Orange Empire

Orange Empire is shared IIIF services; it uses the Cantaloupe Image Server.

Orange Empire was named after the Pacific Electric train that operated between Los Angeles and Redlands from 1914 to 1929.

Product Owner: Michael Stuart (UCSD) | Tech Lead: Matt Critchlow (UCSD)

Shoreline

Shoreline is a geospatial materials platform based on GeoBlacklight.

Shoreline was named after the Southern Pacific train that ran between Los Angeles and San Francisco between 1927 and 1931.

Product Owner: Amy Work (UCSD) | Tech Lead: Alexandra Dunn (UCSB)

Starlight

Starlight is an exhibits platform based on Spotlight.

Starlight was named after Southern Pacific Starlight Train that operated overnight between Los Angeles and San Francisco from October 1949 to July 1957.

Product Owner: Chrissy Rissmeyer (UCSB) | Tech Lead: Matt Critchlow (UCSD)

Superskunk

Superskunk is Comet's metadata API; used by other platforms to read metadata in real time.

Superskunk was named after the California Western Railroad, popularly called the Skunk Train ("Super Skunk"), that runs from Fort Bragg to Willits starting from 1965 to the present.

Product Owner: TBD | Tech Lead: TBD

Tidewater

Tidewater is an OAI-PMH endpoint that uses configurable metadata.

Tidewater was named after the Tidewater Southern Railway which was a short line railroad in Central California that ran from 1910 to 1987.

Product Owner: TBD | Tech Lead: TBD