Princeton University has had an Open Access mandate in place since fall of
2011. Slowly but surely we are getting to the point of following through by
collecting articles in the form of citation metadata and article documents. At
the moment we hope to work with Symplectic for citation discovery. Staff will
upload documents on behalf of authors. Citation metadata and documents will be
pushed through to a DSPACE repository, where the articles will become
accessible to everybody. We have to plan our process, such that we ask as
little as possible from facility authors.
So first off - is there anybody out there using Symplectic ? If so, please
tell me about your experience.
Second: Do you know of a DSPACE instance dedicated to scholarly publications ?
In addition, there are several questions, we need to answer, and I would like
to learn from other people / institutions, who went through this already.
Content organizations
At one extreme we could simply have a giant community with one giant
collection, where everything goes. Personally. I lean towards organizing
articles by department, which we expect to have available as one of the
metadata fields. Articles with authors from different departments would be
listed in two collections.
Workflow
Once article metadata and a document is ingested, it enters a workflow.
* Where necessary, a staff member adds wording requested by publishers to
accompany the publication on the web.
* If the document is deemed unacceptable (see Document formats), a new
better document needs to be found and uploaded
* Once all is ready, we plan to send an email to inform author/s of the
pending publication in our repository, Preferably that email should contain a
link to the item, as it will look once published. At a minimum it should
include a link to the article bitstream, so authors can properly review.
* The item becomes public, unless the author replies within a specified
time indicating that publication should be ‘aborted’.
I have not really worked with the DSPACE workflow system; my guess is, that
I’ll have to do some custom coding. Right ?
Document formats:
Which document formats should we allow ? PDF, PDF/A, others ?
How can we validate formats ?
How to virusscan documents ?
Is this done in a cronjob, integrated in the workflow ?
The word on the street seems to be: 'do not do automatic format migration’. Is
that the consensus ?
Once we have content in the repository, it will make sense to offer a couple
XML, json access points, so it is easy to list articles by department, by
author, .. or access individual articles … I expect that referrers, for example
department websites, will often want to take the query result and format them
as HTML themselves as opposed to linking to DSPACE item pages. Will the REST
interface do the trick ?
Many questions, … - so thank you in advance for any and all answers
Monika
________________
Monika Mevenkamp
phone: 609-258-4161
Princeton University, Princeton, NJ 08544
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
