emory ▪ notre dame ▪ oregon state ▪ virginia tech the ockham project and digital library...
Post on 03-Jan-2016
213 Views
Preview:
TRANSCRIPT
emory ▪ notre dame ▪ oregon state ▪ virginia tech
The OCKHAM ProjectAnd Digital Library Services
Registries
emory ▪ notre dame ▪ oregon state ▪ virginia tech
• History and Context of the OCKHAM Initiative
• The funded NSF/NSDL Grant
• OCKHAM Services
• OCKHAM Registry
• Future OCKHAM
emory ▪ notre dame ▪ oregon state ▪ virginia tech
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Four Goals:
1) Reference Model
2) New Services (including registry)
3) Adoption of Services / Registry
4) Dissemination and Community Building
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Reference Model
DLServicesRegistry Service ProviderService Accepter
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Initial OCKHAM Services
1) Digital Library Services Registry
2) Alerting Service
3) Browsing Service
4) Harvest-to-Query Service
5) Conversion Service
6) Cataloging Service
7) Pathfinding Service
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Harvest-to-Query (H2Q)
OAI
OAI
OAI
Z39.50SRUSRW
emory ▪ notre dame ▪ oregon state ▪ virginia tech
P2P Registry(aka Distributed Registry)
•Digital Library Services Registry•DNS for Digital Library Services•Distributed to promote extensibility and scalability•Uses IESR Metadata Model•Enables Machine-to-Machine Functionality
•Service-to-Service•Auto-discovery•Intrastructure
emory ▪ notre dame ▪ oregon state ▪ virginia tech
OCKHAM Registry
Architecture Overview
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Design Goals
• Broad compatibility with existing technologies: OAI, Z39.50, Http
• Modular design to allow extensibility
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Registry Architecture
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Data LayerRelational Db & OJB• Synchronized• Database
Interchangeability• Ease of development
Lucene• Fast indexing• “on the fly” indexing• Flexible query engine
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Interface LayerCurrent Interfaces• Struts powered J2ee
interface • OAICat - OAI-PMH 2.0
Future Interfaces• SRU/W • Z39.50
Output Formats• Html• XML
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Clients• Web browser• OAI-PMH • Z39.50• Any web enabled
application.
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Network Layer• JXTA provides low level
network functionality– Peer identification and
discovery– Transport layer
• PeerManager provides modular application level functionality
– Load Management– Client/Server Modules
• Main Registry Modules– URL Server– Harvester Client
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Using OAI For Propagating Data
• A peer can query any other peer and receive an incremental update
• Queries are based on the latest record modification date for the peer’s local copy of the set
• Subsequent queries will use the new latest record modification date
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Hierarchal Network Topology
Topology Requirements• Data must propagate to all
peers• Compensation for inherent
instability of P2P networks• Scalable structure• Low overhead• DNS for Digital Library
Services
emory ▪ notre dame ▪ oregon state ▪ virginia tech
Put the pieces together
emory ▪ notre dame ▪ oregon state ▪ virginia tech
OCKHAM Future
•Expand the DLSR Community and Use•Explore and build DLSR-aware tools and services•Examine personal use of the DLSR•Continue to collaborate with IESR
top related