1	DPubS An Open Source Electronic Publishing System David Ruddy DLF Fall Forum October 25, 2004
2	DPubS Development Project Generalizing and extending software developed for Project Euclid Goal: to provide lower-cost publishing alternatives for scholarly communications Partner: Penn State University Libraries Two year project Ithaca meeting, Oct 2004
3	DPubS History Early Dienst development (1994-95) NCSTRL—Networked Computer Science Technical Report Library (1995-98) CUL digital collections (1997-2000) CUL electronic publishing Project Euclid (2000— )
4	DPubS Development Since 2000 Extensive additions to all services Subscription Service developed Flexible access control options OAI 2.0 compliance E-Commerce (pay-per-view) Full-text searching Subscriber/publisher usage statistics Referral Service Reference linking processes, DOI registration, remote db lookup processes…
5	DPubS services & APIs
6	DPubS Document Request
7
8	Project Development Goals Generalization of the software Creation of administrative interfaces Development of editorial management services Addition of interoperability with Institutional Repositories
9	Generalization of the Software Design a more flexible User Interface Service using XML/XSLT Abstract the underlying configuration metadata within DPubS, allowing a more flexible range of hierarchical structures Flexible collection building Additional document types
10
11	User Interface Redesign Move user interface customization out of core code and into XSLT stylesheets Make use of XML pipelines
12	DPubS XML Dataflow
13	Goals of Metadata Service Redesign Rationalize where and how configuration metadata is stored and accessed Build support for more flexible groupings and hierarchical displays Support a richer, more extensible object metadata model for defining document structure
14	“Publications” and “Collections” Publications: Content objects Predictable structures, defined by an XML schema For example: Serials Proceedings Monographs Collections: Relationships among content objects and other collections Flexible structures Multiple structures, involving the same objects, must be possible
15	Creation of Administrative Interfaces Create web interfaces to manage administrative processes Configuring new publication, load content, load subscription data, troubleshooting access problems, etc. Goals Simplify administrative tasks Lower staff costs Reduce risk
16	Development of Editorial Management Services Support manuscript management and peer review activities Manuscript submission Reviewing Document tracking Organization of publications Publishing content (“making public”)
17
18	Editorial Mtg. Challenges Complexity and peculiarity of publisher workflows Access controls Must be group based Authors, editors (head, associates, editorial boards), reviewers, administrative staff Keeping tools (within a single service) operationally independent Functionality must be easily extended
19	Interoperability with Institutional Repositories A DPubS extension Identified IRs: DSpace, Fedora DPubS becomes an application layer on top of IR DPubS Repository Service functions as an API for input/output to IR
20
21	DPubS and Institutional Repositories DPubS vs. Institutional Repository? Why interoperate with an IR? That may be where the content is Division of labor: publishing vs. archiving Ability of both parties to focus on a more narrowly defined set of functionality Interoperability will require cooperation and support of IR
22	DPubS Web site: http://dpubs.org Production implementation: http://projecteuclid.org Questions? David Ruddy <dwr4@cornell.edu>