(Quick Reference)

1 Introduction - Reference Documentation

Authors: Lucien van Wouw

Version: 1.4

1 Introduction

The object repository should is a service oriented framework. It offers a collection of services:
  • ftp upload of files to a staging area (temporary storage)
  • ingesting those files and related metadata into persistent storage
  • image, audio and video derivative generation
  • accepts custom made derivatives of any content type
  • persistent identifier creation by calling a PID webservice. Here persistent URLs become available that resolve to the stored resource and compound object locations
  • anonymous and account controlled dissemination of the resources via HTTP and FTP
  • exports compound objects by via METS and PDF
  • an administration interface plus account system to manage the above services and access policies

Purpose of this documentation

This document will describe two aspects as outlined in this sketch:
  • What it is: on the left side are the service levels placed in context. A description of them should make clear how the framework handles the digital information you supply to it.
  • How to operate it: on the right is the administration panel where you manage your content. A guide will help you control it.

1.1 Change Log

Current release, version 1.4

  • Access to repository resources can be set for user accounts. Access policies are applicable to these accounts.
  • Specific resources and their download limits and expiration dates can be assigned to such accounts

Version 1.3

  • Restructured the documentation to include architecture
  • Double key authentication is required for delete actions
  • Embargo support

Version 1.2

  • the structure of compound objects can be expressed in the processing instruction: file order and a group identifier
  • based on this structure; it is possible to export METS and PDF files on the fly via dissemination
  • a PID can be set for the group identifier
  • instructions can be recreated after an ingest
  • pid lookup is possible at the "stored objects" panel
  • read only FTP access to the master and derivatives for administrative accounts

Deprecated: CPADMIN accounts can no longer be set via the administration interface. Contact the administrator of to distribute such privileged accounts.

Version 1.1

  • Derivative production of audiovideo
  • Custom policies can change the default 'closed' access for masters to open and restricted
  • Deletion of masters and derivatives are removable via an instruction
  • Content and usage statistics are available on the main dashboard

Version 1.0.1

The administration interface has links in the footer to:
  • Build info showing the most recent changes
  • For reporting bugs and feature request please visit Jira

Version 1.0

First release

1.2 Milestones

Milestones (until June 2013)

June 2012Maintain code on GitHubreleased
July 2012Documentation of object repository designreleased
July - November 2012 (August Vacation period)Derivative production for videoreleased
July - November 2012 (August Vacation period)Derivative production for audioreleased
July 2012oauth2 administrative Interfacereleased
July 2012Captcha to administrative Interfacereplaced by separate authentication procedure & released
July 2012Add IPv6 compatibility to Infrastructure and softwarereleased
July 2012Maintain and support helpdeskreleased
July 2012Documenting the Object repository infrastructurereleased
September 2012Content and usage statisticsreleased
November 2012Secure Key-based delivery of content ( e.g. for webshop and other external clients )released
September 2012‘delete-files’ and/or ‘delete-collections’released
December 2012Documentation on how to setup an object repositorypending
February 2013METS to pdf converterreleased
April 2013guest ftp accountspending

1.3 Roadmap

Although not planned, the following services are investigated for inclusion in the object repository.

Integrity assurance service

The object-repository needs a further integrity validation of stored master material. This involves random checksum calculations on files; and repairing invalid information.

File identification and validation service

A service that invokes Fido, JHOVE and PRONOM for file identification to assist determining and verifying a given content type.