Direct comparison
Dspace Vs Eprints: Key Differences & Comparison | CASRAI
DSpace and EPrints are the two dominant open-source platforms for institutional repositories. DSpace (Lyrasis) has stronger global adoption; EPrints (Southampton) has historically led in UK higher education.
Side-by-side comparison
| Dimension | DSpace | EPrints |
|---|---|---|
| First release | 2002 (MIT and Hewlett Packard partnership) | 2000 (University of Southampton) |
| Governance and maintenance | Maintained by Lyrasis (US non-profit library consortium); DSpace community governed via DSpace Steering Group | Maintained by the University of Southampton and EPrints Services (commercial support arm) |
| Technology stack | Java backend (DSpace 7.x: Spring Boot REST API); Angular 12+ frontend. Previous versions used JSP/XMLUI (DSpace 6.x) which are now end-of-life. | Perl-based; Apache/mod_perl architecture; EPrints 3.4 supports REST API but the core is Perl. No modern SPA frontend out of the box. |
| Current version and UI | DSpace 7.x (released 2021 onwards): separate frontend (Angular) and backend (REST API). Migration from DSpace 6.x is a significant undertaking requiring data migration scripts. | EPrints 3.4.x: traditional server-rendered interface. A more modern interface has been developed by the community but adoption is uneven. |
| Global adoption | Largest global install base by OpenDOAR count; dominant in North America, Latin America, Asia, and Africa | Historically dominant in UK higher education; widely used in Europe and Australia; smaller global footprint than DSpace |
| RIOXX metadata profile support | RIOXX 3.0 plugin available for DSpace 7.x; maintained by community contributors. Requires plugin installation. | RIOXX 3.0 plugin available for EPrints 3.4; EPrints has historically had stronger RIOXX community engagement in the UK. |
| OAI-PMH and SWORD support | OAI-PMH 2.0 built in; SWORDv2 and SWORDv3 supported via plugins; REST API is the primary integration point in DSpace 7 | OAI-PMH 2.0 built in; SWORDv2 supported; REST API added in EPrints 3.4 |
| Customisability | DSpace 7 highly customisable via Angular theming and configurable submission forms; REST API enables headless use. Requires JavaScript/Angular skills. | Highly customisable via Perl plugins and XML configuration; large library of community plugins. Requires Perl skills for deep customisation. |
| Community and support | Large international community; annual DSpace North America and global events; Lyrasis provides commercial support contracts; active mailing lists and GitHub | Strong UK community via Jisc and the UK EPrints community (Tech Watch); EPrints Services offers commercial support; community forum at SourceForge/GitHub |
Common questions
FAQ
Should UK institutions migrate from EPrints to DSpace?+
Migration is not necessary and is a significant undertaking. EPrints remains actively maintained and well-supported within the UK community. Institutions should consider migrating if they need a modern REST API-first architecture (DSpace 7), if their IT team has stronger Java/Angular skills than Perl skills, or if they want to align with a platform that has a larger global community. Many UK institutions remain on EPrints without issue. Evaluating both platforms against specific local requirements — workflows, CRIS integration, RIOXX compliance, and staff capacity — is essential before committing.
Which platform is easier to install and maintain?+
Both platforms require dedicated technical expertise and are not trivial to administer. EPrints is often considered easier for initial installation by those familiar with LAMP-stack environments. DSpace 7's separation into a Java backend and Angular frontend introduces more moving parts but delivers a more maintainable long-term architecture. Both have active documentation and community support. Institutions without dedicated repository technical staff typically engage EPrints Services or Lyrasis for managed hosting.
Do both DSpace and EPrints support the RIOXX metadata profile?+
Yes. RIOXX 3.0 plugins are available for both DSpace 7.x and EPrints 3.4. RIOXX is a metadata application profile for UK open access repositories developed under Jisc funding, designed to expose consistent, machine-readable metadata for use by aggregators and funders. Institutions complying with UKRI's open access policy are expected to expose RIOXX-compatible metadata. Plugin installation and configuration is required on both platforms; the EPrints RIOXX community has historically been more active in the UK.
What is Samvera (Hyku) and when should it be considered?+
Samvera is an open-source repository framework built on Ruby on Rails with a Solr search index and Fedora digital object storage backend. Hyku is its multi-tenant, cloud-ready variant. Samvera is more commonly adopted in North America, particularly by universities with strong digital library programmes seeking a highly flexible platform. It is significantly more complex to install and operate than DSpace or EPrints, but offers greater architectural flexibility. It is rarely the first choice for UK institutions building a straightforward research outputs repository.
Going deeper
