130 likes | 223 Views
Initiative for Open Access Journals: Establish new scientific eJournals, promote web-based information management, customizable workflow, digital peer publishing. System includes Peer-Review, LDAP-Auth., User / Document / Content Management, DiPP Services, OAI, SOAP, Fedora Repository, DOI management, and Publication Engine. Various services like Conversion, URN, Distribution, and Hierarchy are offered for efficient journal publication. Contact for more information.
E N D
I n i t i a t i v e f o r O p e n A c c e s s e J o u r n a l s • Fedora-based • Publication-System • for Open Access • eJournals
Mission foundation of new and expansion of existing scientific electronic journals promotion of new methods of web-based cooperative information management customizable workflow within a common publication system fast, open and transparent digital peer publishing
Publication System Peer-Review-System LDAP-Auth :User Management :Document Management :Content Management DiPP-Services OAI SOAP Fedora Repository :Document Conversion :Hierarchy :Content :Metadata :URN Management Components and Middleware
:Review engine :Repository engine Author Referee Editor Publication Pipeline: Review 1:submit 2:review 3:accept or deny 4:transfer
:Repository engine :Conversion engine :Editorial manager :Publication Engine Author Reader Editor Publication Pipeline: Editorship 5:assign URN 6:convert 7:retrieve 8:edit 9:give imprimatur 10:publish 11:read
conversion engine XSLT DiPP-Services 1 Conversion-Service customizable stylesheets preparation for long term preservation statistics
DiPP-Services 2 URN-Service persistent identifier for journals, articles, supplementary material Distribution-Service registration for OAI-Harvesting RSS-feeds Email-”Alert” etc.
obj: journal obj: container ... obj: article ... obj: content obj: content obj: content ... ds: xml ... ds: html ... ds: image ... DiPP-Services 3 Hierarchy-Service defined in “administrative metadata” datastream child-list, parent-list cModel metadata-field defines element
Fedora-is it good enough? pros highly modularized architecture versioning of datastreams addition of own metadata formats cons added metadata in own formats are not searchable inconsistent versioning of API-A and API-M methods from Fedora 1 to Fedora 2
Summary and Outlook workflow based publication system extended services on top of Fedora DINI-Certification standardisation of document and publication server full-text indexation via FAST-search-engine improvement of usability
Contact dipp@hbz-nrw.de Dr. Wolfram Horstmann horstmann@hbz-nrw.de ++49-221 / 40075-173 Dr. Peter Reimer reimer@hbz-nrw.de ++49-221 / 40075-197 Jochen Schirrwagen schirrwagen@hbz-nrw.de ++49-221 / 40075-460