Rosetta DPS Configuration Guide


The Web Curator Tool is able to archive harvests to the Rosetta Digital Preservation System (DPS). The National Library of New Zealand currently uses Rosetta DPS for archiving their harvests from WCT.

This guide shows how to deploy and configure an instance of Web Curator Tool to work with Rosetta DPS.

Contents of this document

Following this introduction, the Rosetta DPS Configuration Guide includes the following sections:

  • Wayback Vs OpenWayback - Covers the Wayback options.
  • Installation - Covers installing Wayback.
  • Configuration - Covers configuring Wayback.
  • Wayback as a Review Tool in WCT - Covers configuring Wayback for use as a review tool in the Web Curator Tool.
  • Testing - Covers testing the Wayback installation.
  • More information - Provides some links for more information.

All configuration for this integration is inside ``. (This file is located in `/<path to tomcat>/webapps/wct-store/WEB-INF/classes/`.

Configuration steps

Enable Rosetta DPS archiving

# The archive type to use for this installation (one of: fileArchive, omsArchive, dpsArchive).

Configure the Rosetta Server


Set your access restriction codes

#OMS Codes (Rosetta)

Custom deposit form configuration

DPSArchive uses the following two parameters to determine whether a custom deposit form needs to be displayed before submitting an HTML Serial harvest. Configure the following parameters to reflect:

  • The name of the agency that would normally harvest/ingest HTML serials
  • The Dublin Core Type that would represent the target for an HTML serial

If there are more than one value for each of these, separate them using comma.

dpsArchive.htmlSerials.agencyNames=Electronic Serials Harvesting

URLs that WCT Core would use to display the custom deposit form for each of the target types, separated by comma. A note on the format of this URL:

  • If WCT Core and WCT Digital Asset Store are deployed in the same Tomcat instance, use a relative URL.

  • If they are deployed in different machines or Tomcat instances, use absolute URL based on WCT DAS’ host/port.

  • The material flow ID for each of the target types, separated by comma. There should be one entry for each target type defined above.

  • The IE Entity Type for each of the target types, separated by comma. There should be one entry for each target type defined above.


User Interface adjustment

In the event that multiple targetDCTypes are added (as per above), then they need to be made available through the user interface.

User interface types

  • Configuration for this list of types is inside wct-core-lists.xml. (This file is located in /<path to tomcat>/webapps/wct/WEB-INF/classes/).

  • The value should match the targetDCType set in

    <bean id="dublinCoreTypesList" class="org.webcurator.core.common.WCTTreeSet" abstract="false" singleton="true" lazy-init="default" autowire="default"  dependency-check="default">
        <constructor-arg index="0" type="java.util.List">
            <value>Interactive Resource</value>
            <value>Moving Image</value>
        <constructor-arg index="1" type="int">

More information

The following guides can provide additional information: