EprintsOpen Source Document Repository

Henok MikreORNL and University of Tennessee

Summer Intern1

Overview

• Developed and maintained by the School of Electronics and Computer Science at the University of Southampton, UK

• Written in perl• MySQL as a database engine• Allows authentication through LDAP • Highly customizable• > 267 installations around the world

2

Purpose

• One-stop location for publications and presentations associated with CCA– Especially for sponsors, potential users

• Easily organize different versions of an eprint (draft, submitted, pre-publication, published)

• Control who gets to see what • Categorize by projects, funders• Browse by almost any attribute, including author,

projects, dates, status, event, and refereed

3

Purpose (cont.)

• Maintain draft or pre-publication versions of eprints.

• Maintain links to published versions at external sites

• Export a bibliographic list of a desired collection (i.e. all works by a given author)

• Saved searches

4

User Types/User Roles• Visitor (anonymous)– Browse, search repository

• User (authenticated)– Deposit item, submit a new version of previously

deposited item, request an item to be deleted• Editor– Deposit item, review items deposited by users, move

items to live archive• Admin– Index new items for search, manage metadata fields, etc

• Additional roles can be defined easily

5

Workflow

• Visitor can browse and export citations• Authenticated users taken to work area at

login; can make a new entry or import a BibTeX or XML citation

• Editors also taken to work area at login; reviews and moves items to live archive (i.e. quality control)

• Admins re-index repository, manage metadata fields

6

Workflow: User login

7

Item under review

8

Next login: item is live!

9

Self-Archiving and Post-Prints• In most cases, copyright on final published form

owned by publisher• Posting link is useful, but may require fee-for-access• Many journals/publishers allow “self-archiving” of final

versions– http://www.eprints.org/openaccess/self-faq/#self-archivin

g– http://romeo.eprints.org/publishers.html

• Post-prints (the final version you sent to the publisher) are yours and can be posted as you wish. Just be clear what they are, especially if you made changes at the proof stage!

10

What’s Next?• More customization:– Export citation for any given item on-the-fly– Integrate appearance w/ new CCA Forum Plone site– Additional repositories?

• CompFrame (beyond just CCA)– Multiple repository synchronization

• i.e. CCA w/ CompFrame repositories– Better application of user roles

• Not clear that we need more sophistication (yet)– Controlled subject vocabulary? (not using now)– Can modify/add/remove document types if desired

11

Live Demo

• Browsing as visitor• Authenticated user: login -> work space • Workflow of depositing new item

12