1 / 24

The DPubS Development Project: Building an Open Source Electronic Publishing System

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….

sammya
Download Presentation

The DPubS Development Project: Building an Open Source Electronic Publishing System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. DPubSDigital 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.

  3. Evolution of DPubS • Origins in Cornell Computer Science department, mid-90s • NCSTRL—Networked Computer Science Technical Report Library (1995-98) • Project Euclid development, 2000-2003 • DPubS development project, 2004-2006

  4. 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

  5. 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

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

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

  8. SOAP REST Direct I/O SOAP REST Direct I/O Index Service Service X DPubS Services HTTP Request:…verb=verbName&version=2.0 Response:XML

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

  10. 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

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

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

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

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

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

  16. 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

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

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

  19. DPubS • http://dpubs.org • dwr4@cornell.edu • Center for Innovative Publishing • http://cip.cornell.edu

More Related