Digital Repository

Making use of handles

Introduction

• Digital Repository launched in June 2007

http://repository.unimelb.edu.au

• Handle Server Setup and Configuration

• DigiTool Server Setup and Configuration

• Handle Service Administration

• Handle Resolution Service

Objectives

Persistent identifiers for

• referencing/citation purposes

• application independence

• integration with existing systems

• reliability

System Infrastructure

repository.unimelb.edu.au

dtl.unimelb.edu.au

dtlt.unimelb.edu.au

One way replication

Handle Servers

app1.lib.unimelb.edu.au

app2.lib.unimelb.edu.au

Handle Server Setup and Configuration

• Handle Servers– app1.lib.unimelb.edu.au [ primary ]– app2.lib.unimelb.edu.au [ replication ]– global ip addresses

• Naming authorities• 10187• 10187.TST

Handle Replication

• Handle Replication– app2.lib.unimelb.edu.au [ replication ]– using Handle Server software replication– acts as a resolution service only, i.e. no

administrative tasks

Handle Server Storage

• Backend storage using MySQL database– more powerful querying capabilities– flexibility in generating and publishing

handles– application development and integration– enables improved disaster recovery, e.g.

backup, restore and replication

Handle Server MySQL Configuration

Handle Server MySQL configuration:

1. create a handle database and tables

2. download mysql jdbc connector and update java classpath

3. update server_config section in config.dct file

4. publish handles

DigiTool Handle Setup and Configuration

• Handle Profile Rulespi_profiles_rules.xml – defines rules and profiles for creating handles

• Handle Publisher Rulespi_publisher_rules.xml – defines rules and profiles for publishing handles

• Handle ConfigurationhandleConfig.properties

hdltool.ini

Handle Profile Rules Example

Example pi_profiles_rules.xml:• Rules<rl:de_rule name="view handle rule"> <usage_type>VIEW</usage_type> <entity_type/> <file_extension/> <relation_type></relation_type> <preservation_level/> <handle>handle_profile</handle></rl:de_rule>

• Profiles<pi_profile name="handle_profile"> <pi_type>handle</pi_type> <pi_preffix required="true">10187</pi_preffix> ...</pi_profile>

Handle Index Mapping

pi_publisher_rules.xml:

<params> <paramsGroup name="handle.indexes.mapping"> <parameter name="stream">201</parameter> <parameter name="stream_manifestation">202</parameter> <parameter name="raw_metadata">203</parameter> <parameter name="formatted_metadata">204</parameter> <parameter name="descriptive_metadata">205</parameter> <parameter name="resource_discovery">206</parameter> </paramsGroup></params>

Generating Handles

• Creation of handle using:– Meditor > Object Services > Create URN– WebIngest Module– Meditor Management > Maintenance >

Generate Persistent Identifier

<object xmlns="http://www.loc.gov/standards/premis">

<objectIdentifier>

<objectIdentifierType>handle</objectIdentifierType>

<objectIdentifierValue>10187/2468</objectIdentifierValue>

</objectIdentifier>

</object>

Publishing Handles

• Publish handle using:– Meditor > Object Services > Publish Persistent

Identifiers– Meditor Management > Maintenance > Publish

Persistent Identifier

Handles in Resource Discovery

• Create new Dublin Core ‘<dc:terms>handle</dc:terms>’ element– allows handle values to be displayed seperately

• Update repository_indexing_schema.xml– allows searching of handles

• Update repository_harvesting_schema.xml– copy premis metadata into dublin core handle

value

• Linking options using Javascript

Handles in OAI Replication

repository_replication.xml<replication name="adt" enable="true"> <rs:set>...</rs:set> <targets> <target type="class"

class_name="com.exlibris.digitool.repository.de.DigitalEntityOAIReplicator"> <format_convertor type="class"

convertor="com.exlibris.digitool.repository.de.De2DCTransformer"> <params> <param

name="xsl_dc2simpleDc">/exlibris/dtl/j3_1/digitool/home/system/xsl/DC2SimpleOAIDC.xsl

</param> <param name="piaddDCHandle">piaddDCHandle.xsl </param> </params></format_convertor> </target> </targets></replication>

Handle Server Administration

• CNRI Handle Administration Tools– available as part of HANDLE.NET software– query, update, modify, remove...etc...

• Meditor– creating, updating and publish handles– cannot unpublish from handle server

• Handle Manager– custom developed tool– create, update, publish, unpublish handles– schedule

Handle Manager

DigiTool Web Services

Repository

Repository API( abstraction layer )

Bibliographic Citation Generator Handle ManagerDigital Repository Web Services

( integration )

Handle Manager HmConfigDocument.xml

<hm_config xmlns='http://manager.handle.unimelb.edu.au/schema/Configuration'><subset_size>30</subset_size><ws_endpoint>http://dtlt.unimelb.edu.au/de_repository_web/services/DigitalEntityExplorer</ws_endpoint><naming_authority>10187</naming_authority><admin_unit>UOM02</admin_unit><x_queries>

<x_query type="xql" set_name="SET1"><x_select from_answer="0" to_answer="10"><element>control</element></x_select><x_where>

<x_condition><type>contains</type><element>mid</element><value>62487</value>

</x_condition> </x_where><x_sort>

<by>pid</by><x_order>desc</x_order>

</x_sort></x_query>

</x_queries></hm_config>

Handle Manager Tasks

• Handle Generator>> au.edu.unimelb.handle.manager.Main HANDLE_GENERATOR config.xml

• Handle Publisher>> au.edu.unimelb.handle.manager.Main HANDLE_PUBLISHER config.xml

• Handle Explorer>> au.edu.unimelb.handle.manager.Main HANDLE_EXPLORER config.xml

• Handle Updater>> au.edu.unimelb.handle.manager.Main HANDLE_EXPLORER config.xml

• Common Features– executed from command line– single mode or batch mode– logging

Research Management System Integration

DigiTool Web Services

Repository

Repository API( abstraction layer )

Bibliographic Citation Generator Handle ManagerDigital Repository Web Services

( integration )

THEMIS ( Research Management System )

Digital Repository Web Services

• Digital Repository Web Services provides:– foundation for integrating the research

management system– used to create, update and delete objects– objects pushed into repository– automated mapping of Dublin Core

metadata between systems

Handle Web Resolution Service

• HANDLE.NET proxy server– Can be used for querying and resolution

• http://repository.unimelb.edu.au/ - primary entry point

• http://app1.lib.unimelb.edu.au:8000/ and http://app2.lib.unimelb.edu.au:8000/ - secondary entry points

• http://hdl.handle.net – global entry point

Handle Resolution Sequence Diagram

Web Client repository.unimelb.edu.au

10187/2043

app1.lib.unimelb.edu.au

dtl.unimelb.edu.au

Rewrite URL

http://app1.lib.unimelb.edu.au:8000/10187/2043?index=206

Resolve handle

http://repository.unimelb.edu.au:80/R/?func=dbin-jump-full&object_id=72915

http://dtl.unimelb.edu.au:80/R/?func=dbin-jump-full&object_id=72915

Rewrite URL

Display metadata

© Copyright The University of Melbourne 2008