All topics Knowledge Base

Submit more ePublishing systems? Please use this template!^?

[Edit]Evaluated Systems

1. Open Journal Systems OJS (University of British Columbia and Simon Fraser University)
2. HathiTrust Digital Library (collaboration of 26 United States research institutions)
3. Connexions & Rhaptos (Rice University)
4. GNU EPrints (University of Southampton)

[Edit]Recommendations

• You want to give simple and fast access to publications, which are already reviewed, formatted and ready for being published with a minimum of workflow processes? GNU EPrints can fulfill this function.

• You want to display the whole workflow (from author-indicated submission to the final archiving) and provide expandability and an easy installation? Here we can recommend the Open Journal Systems.

• You need and extensive and deep going adaptability? DPubS^? can fulfil this request.

• You want to use RDF features (i.e. for more sophisticated bibliometric and referencing functionalities)? In this case, we recommend Hyperjournal^? (Sesame RDF Engine) and Topaz^? (Mulgara RDF Engine) hier zu nennen

[Edit]Audience

1. scientific libraries e.g. the Humboldt-Universität zu Berlin
2. scientific associations e.g. the Max-Planck-Society
3. university press e.g. Universitätsverlag Göttingen
4. faculties e.g. faculty of law
5. individual researchers/scientists e.g. Laurent Romary, Stephen Hawking
6. commercal hosting-/serviceprovider e.g. KOBV,GBV, Copernicus
7. commercal provider of ePublishing software e.g. Avedas, PKP

[Edit]Selective Criteria

• shared interest of the audience: open access availability of knowledge in an electronical way via internet
• standard features: peer review management, client access for final documents
• special features: APIs for the communication of the ePublishing systems with for instance institutional repositories, websites, portals, eLearning management systems, content management systemen and digital asset management systems
• not proprietary -> open source
• for scientific and academic publishing
• ePublishing systems are mostly integrated into a bigger IT infrastructure
• non-profit settings in the front

[Edit]Annotations

• The easiest form of APIs are batch im-/exports, documents are brought in and out via batch processing
• Regarding the APIs most systems support the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), thus a clustered search via OAI compliant repositorien is possible as well as genauso wie die allocation of an open API for metadata extraction. The support of OAI-PMH is in this case twice as useful. The other APIs in the list of attributes, with which every system was evaluated are not a quarter as popular. The "eduSource Communication Layer (ECL)" and Java-related "JSR-170" attracted interest as well. Both protocols manage the content-related communication between repository-systemen. It's not really sure, if one of the tested systems really supports ECl. JSR-170 will potentially be supported by DiVA and Topaz because every other application is not programmed in Java but in PHP, Phyton oder Perl.
• DPubS and Open Journal System both support the expandability of the programming code. In DPubS this is achieved through the integration of Perl-Code in a special index, which is part of the modular and service-oriented architecture. In Open Journal Systems the extension is achieved through a well-defined plugin-API for PHP developers.

Evaluation Criteria^?

source (https://wiki.library.jhu.edu/download/attachments/22964/Open+Source+ePublishing+Systems+White+Paper.pdf?version=1)

Last changed: 10.02.2011 15:46 (CID: 581) by Maxie Putlitz -