The DPubS Development Project: Building an Open Source Electronic Publishing System David Ruddy Cornell University Library

DPubS Digital Publishing System An electronic publishing application that enables…. publishers to organize, manage, present, and deliver both open access and subscription controlled scholarly communications; and users to discover, navigate, and access scholarly content.

Evolution of DPubS Origins in Cornell Computer Science department, mid-90s –NCSTRL—Networked Computer Science Technical Report Library ( ) Project Euclid development, DPubS development project,

Functionality developed for Euclid Full-text format neutral Full-text indexing Flexible access control options for publishers E-Commerce (pay-per-view) OAI 2.0 compliance Usage statistics for subscribers/publishers Reference linking DOI registration Referral Service

Lessons learned from Euclid We must accommodate multiple and mixed business models We must accommodate publishers’ requests for enhancements and greater functionality We must expect, and design for, unanticipated publishers’ requests

DPubS development Mandate: generalize and enhance the Euclid software and release as Open Source Funding period: Development agenda: –Generalize the system –Administrative interfaces –Addition of editorial management tools –Allowing interoperability with institutional repositories, such as Fedora and DSpace

DPubS Services User Interface Service Repository Service Index Service Subscription Service User Registry Service Editorial Service Publisher User Referral Service

Index Service SOAPRESTDirect I/O DPubS Services Service X SOAPRESTDirect I/O HTTP Request: …verb=verbName&version=2.0 Response: XML

DPubS Services User Interface Service Repository Service Index Service Subscription Service User Registry Service Editorial Service Publisher User Referral Service

Generalization of system Redesigned User Interface Service –Move UI customization out of core code –UI now is now xml/xslt driven Employ a more abstract, and configurable, definition of… –Object types (document structures) –Metadata types Allow for “collections”: –Grouping mechanism; may contain publications or other collections

DPubS Services User Interface Service Repository Service Index Service Subscription Service User Registry Service Editorial Service Publisher User Referral Service Collection Service

Administrative interfaces Rationalize production workflow Web interfaces to manage administrative processes Goals: –Definition and simplification of workflows –Lowering production costs –Reduction of risk

DPubS Services User Interface Service Repository Service Index Service Subscription Service User Registry Service Editorial Service Publisher User Referral Service Admin UI Service Collection Service

Editorial management services Support manuscript management and peer review activities –Manuscript submission –Reviewing –Document tracking –Organization of publications –Publishing content (“making public”)

DPubS Services User Interface Service Repository Service Index Service Subscription Service User Registry Service Editorial Service Submission Service Author Publisher User Referral Service Admin UI Service Collection Service

Interoperate with institutional repository systems Identified IRs: DSpace, Fedora Why? –Where the content resides –Division of labor: publishing vs. archiving DPubS becomes an application layer on top of IR –DPubS Repository Service functions as an API to Institutional Repository

DPubS Services User Interface Service Repository Service Index Service Subscription Service User Registry Service Editorial Service Submission Service Author Publisher User Referral Service Admin UI Service Collection Service

Technical requirements Perl, mod_perl, apache, other common OS tools Hardware: Sun and Intel boxes OS: Sun Solaris (9, 10), Linux

DPubS – Center for Innovative Publishing –