A Survey and Evaluation A Survey and Evaluation of Open-Source of Open-Source Electronic Publishing Electronic Publishing Systems Systems Mark Cyzyk Mark Cyzyk Library Digital Programs Library Digital Programs Group Group The Sheridan Libraries The Sheridan Libraries Johns Hopkins University Johns Hopkins University
23
Embed
A Survey and Evaluation of Open-Source Electronic Publishing Systems Mark Cyzyk Library Digital Programs Group The Sheridan Libraries Johns Hopkins University.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
A Survey and Evaluation of A Survey and Evaluation of Open-Source Electronic Open-Source Electronic
Publishing SystemsPublishing Systems
Mark CyzykMark CyzykLibrary Digital Programs GroupLibrary Digital Programs Group
The Sheridan LibrariesThe Sheridan LibrariesJohns Hopkins UniversityJohns Hopkins University
DPubS (Digital Publishing System) (Cornell and DPubS (Digital Publishing System) (Cornell and Penn State) Penn State) GNU EPrints (University of Southampton) Hyperjournal (Net7 and University of Pisa)Open Journal System (University of British Columbia and Simon Fraser University)
Broad Areas of EvaluationBroad Areas of Evaluation
Institutional affiliation and other indicators Institutional affiliation and other indicators of the viability of the open-source projectof the viability of the open-source project
Technical requirements, maintenance, scalability, and documented APIs
Submission, peer review management, and administrative functions
Access, formats, and electronic commerce functions
Institutional affiliation and other Institutional affiliation and other indicators of the viability of the indicators of the viability of the
open-source projectopen-source project
Name of systemName of systemCurrent version of systemCurrent version of systemTested version of systemTested version of systemURL of project homepageURL of project homepageInstitutional affiliationInstitutional affiliationAge of projectAge of projectNotes on long-term viability of projectNotes on long-term viability of projectDegree of deploymentDegree of deploymentType of open-source licenseType of open-source licenseLicensing notesLicensing notesOther documentation (Webliography)Other documentation (Webliography)
Technical requirements, Technical requirements, maintenance, scalability, and maintenance, scalability, and
documented APIsdocumented APIs
Local install or ASP?Local install or ASP?Operating system requirementsOperating system requirementsHardware requirementsHardware requirementsApplication server requirementsApplication server requirementsPrimary programming languagePrimary programming languageAuxiliary programming languageAuxiliary programming languageApplication frameworkApplication frameworkDatabase server requirementsDatabase server requirementsOther software requirementsOther software requirementsRequired skillsRequired skillsInternal backup and restore functionsInternal backup and restore functionsScalability: ApplicationScalability: ApplicationScalability: DataScalability: DataAPI: Batch ingestAPI: Batch ingestAPI: Batch ingest formatsAPI: Batch ingest formatsAPI: Batch exportAPI: Batch exportAPI: Batch export formatsAPI: Batch export formatsAPI: Support for JSR 170API: Support for JSR 170API: Support for OAI harvestingAPI: Support for OAI harvestingAPI: Support for eduSource API: Support for eduSource Communication Layer (ECL)Communication Layer (ECL)API: Support for other Web servicesAPI: Support for other Web servicesSecurity notesSecurity notes
Submission, peer review Submission, peer review management, and administrative management, and administrative
functionsfunctions
Support for multiple, discrete publicationsSupport for multiple, discrete publications
Context-sensitive Help supportContext-sensitive Help support
Three Worthy MentionsThree Worthy Mentions
Connexions/RhaptosConnexions/Rhaptos
DiVADiVA
TopazTopaz
DPubS (2.0)DPubS (2.0)
Strengths: Strengths: – Very well architectedVery well architected– Highly customizable – custom metadata schemas, UI Highly customizable – custom metadata schemas, UI
configurations, file formatsconfigurations, file formats– Provision of subscription servicesProvision of subscription services
Weaknesses:Weaknesses:– Difficult to installDifficult to install– Primitive Perl scripts for backend administrationPrimitive Perl scripts for backend administration– Incomplete documentationIncomplete documentation– Publications must be in final form. No modeling of Publications must be in final form. No modeling of
peer review process.peer review process.
GNU EPrintsGNU EPrints
StrengthsStrengths– Runs on multiple platforms, including WindowsRuns on multiple platforms, including Windows– Many features are customizable on a per publication Many features are customizable on a per publication
basisbasis– Easy, author-initiated submissionEasy, author-initiated submission– Large deployment and user communityLarge deployment and user community
WeaknessesWeaknesses– Installation and administration via command-line Perl Installation and administration via command-line Perl
scriptsscripts– Does not seek to model the peer review processDoes not seek to model the peer review process
HyperjournalHyperjournal
StrengthsStrengths– Visually appealing and user-friendly GUIVisually appealing and user-friendly GUI– RDF backend – “contextualization” features allow RDF backend – “contextualization” features allow
users to jump between relevant articlesusers to jump between relevant articles– Editorial workflow completely customizableEditorial workflow completely customizable– Administrative roles can be addedAdministrative roles can be added
WeaknessesWeaknesses– A challenge to installA challenge to install– No full text indexing engineNo full text indexing engine– Supports only a single publication per application Supports only a single publication per application
instanceinstance
Open Journal SystemOpen Journal System
StrengthsStrengths– Runs on multiple platforms/Web serversRuns on multiple platforms/Web servers– Easy to installEasy to install– Comprehensive and clear documentationComprehensive and clear documentation– Support for multiple, discrete publicationsSupport for multiple, discrete publications– Each publication is separately skinnableEach publication is separately skinnable– Highly extensible via a well-defined plug-in APIHighly extensible via a well-defined plug-in API– Large deployment and an active developer and user communityLarge deployment and an active developer and user community– Models the entire peer review processModels the entire peer review process– Well-thought-out administrative roles and default workflowWell-thought-out administrative roles and default workflow– Its selection of bibliographic “reading tools” is interestingIts selection of bibliographic “reading tools” is interesting
Open Journal SystemOpen Journal System
WeaknessesWeaknesses– Hard to think of any!Hard to think of any!– Add support for external authentication Add support for external authentication
service, e.g., CAS, Shibboleth?service, e.g., CAS, Shibboleth?– Add support for persistent storage in a Add support for persistent storage in a
Platform independence should not be neglected.Platform independence should not be neglected.One inherits the flaws of external libraries and One inherits the flaws of external libraries and frameworks. Choose with care.frameworks. Choose with care.Installation procedures must be simple and Installation procedures must be simple and flawless.flawless.Don’t wake the SysAdmin: “Slap a GUI on that Don’t wake the SysAdmin: “Slap a GUI on that XML!” -- and push application administration out, XML!” -- and push application administration out, as much as possible, to select users.as much as possible, to select users.Documentation must be concise, complete, and Documentation must be concise, complete, and comprehensive. “I can’t guess what you’re comprehensive. “I can’t guess what you’re thinking.”thinking.”