Child pages
  • Workspace for Nuxeo-to-Omeka S connector

This is a public wiki space. All contents are publicly accessible unless page restrictions are in place.

Skip to end of metadata
Go to start of metadata

This workspace summarizes activities related to developing a connector between Omeka S and the UC Shared DAMS (Nuxeo).

Planning resources

Use cases

A Nuxeo-to-Omeka S connector would allow campus libraries to centrally manage digital assets in Nuxeo -- while selectively importing copies of content into Omeka S. Omeka S can then be configured to provide tailored, customized, and/or mediated access to the content.

The UC Riverside Library has identified a range of use cases that can be supported by Omeka S:

  • Publishing small-scale digital collections that can be made available for public access, on either a long-term or temporary basis.

  • Publishing content that requires mediated or restricted access, and can be made available to designated users for a limited timeframe (e.g., access approved by a third party, terms/rules of use agreement, etc).

  • Publishing content that can be made available to authenticated users (e.g., UCR affiliates).

  • Publishing research collections managed by UCR faculty members.

  • Publishing digital exhibitions or customized views of particular collections.

  • Publishing collections managed on the behalf of partner organizations, such as community archives.

The UC Irvine Libraries has also identified a range of use cases for Omeka S, summarized in the following draft document: Mediated-access-needs-UCI-OmekaS.pdf

Envisioned functionality for the connector

The initial envisioned functionality is similar to a prototype and predecessor connector, developed by the UC Santa Cruz Library for use with Omeka Classic (NuxeoLink plugin):

  • The connector would ideally take the form of an Omeka S module. We anticipate that it would initially be developed and prototyped as a set of scripts that utilizes both the Omeka S API and Nuxeo API.

  • The initial functionality would support pushing of content from Nuxeo to Omeka S. Users would ideally be able to customize the connector in the following ways: 

    • Specify Nuxeo source (e.g., project folder)

    • Specify Omeka S endpoint (e.g., an item set)

    • Specify what Nuxeo-managed media metadata and files should be copied over (e.g., thumbnails, service copies, high-resolution files)

  • Additional functionality that the connector could eventually support:

    • Options to specify concatenating data from multiple Nuxeo fields into a single Omeka field

    • Option push content from Omeka S to Nuxeo

    • Option to synch content between Omeka S to Nuxeo

Next steps

Q4 2020-Q1 2021

  • Convene a broader conversation with UC campus libraries utilizing both Nuxeo and Omeka S, to further explore the idea of the connector, gauge interest in its use, and coalesce around high level functional requirements.

  • Initiate a collaborative investigation and design phase:
    • Test and evaluate Omeka S functions
    • Gather and synthesize campus library requirements for the connector
    • Investigate how other existing Omeka connectors work, and how configurations and mappings are supported (e.g., Omeka Classic NuxeoLink plug-in; Omeka S DSpace and Fedora Connector modules)
    • Sketch out a proposed design and buildout plan
  • Identify campus library developer and product manager resources, to co-develop the connector.

  • No labels