[EP-tech] Re: Eprints VS Dspace
Ian.Stuart at ed.ac.uk
Thu Jul 16 07:57:41 BST 2015
The two products are, essentially, the same.
My choice came down to "I'm a Perl programmer" - therefore getting to
grips with DSpace was going to be harder for me.
There are other things:
* DSpace has a large formal support network [duraspace] behind it,
whilst EPrints doesn't
- It's easier to get features into "core" eprints [when you know the
right people to ask]
- DSpace is more formal in what goes in & what to expect in future
* DSpace envies the way EPrints is really agile in how its developed;
EPrints envies DSpace in the large support structure it has in place
* DSpace has the concept of "collections", which are like mini
repositories (which can have their own Look & Feel) within the one
service; EPrints has the idea of multiple repositories (which can have
radically different data-requirements) under one web server.
..... but, fundamentally, it comes down to what your tech staff are
happiest using: Perl or Java
On 15/07/15 21:54, Edwin Gamez wrote:
> Hello everyone.
> I am currently implementing Eprints as a repository for digital
> collections. I have some time using eprints and have adjusted its
> structure and environment in general. But recently I asked me the
> question why use Eprints, instead of DSpace, has given me the task. I
> have not found anywhere that tells me a comparison which is better than
> the other, from my point of view both are equal.
> The question is: What is the difference between Eprints and DSpace? Why
> some decide to use DSpace and other eprints. I want to know your answers
> on what type of repository is more convenient to use and what are the
> advantages of each.
Developer: ORI, RJ-Broker, and OpenDepot.org
Bibliographics and Multimedia Service Delivery team,
The University of Edinburgh.
This email was sent via the University of Edinburgh.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
More information about the Eprints-tech