DSpace open source software is a turnkey repository application used by more than 2,000 organizations and institutions worldwide to provide durable access to digital resources. For more information, visit http://www.dspace.org/
main branch. This means that there is NO user interface on this
main branch. DSpace 7 will feature a new, unified Angular user interface, along with an enhanced, rebuilt REST API. The latest status of this work can be found on the DSpace 7 Working Group page. Additionally, the codebases can be found in the following places:
- DSpace 7 REST API work is occurring on the
mainbranch of this repository.
- The REST Contract is at https://github.com/DSpace/Rest7Contract
- DSpace 7 Angular UI work is occurring at https://github.com/DSpace/dspace-angular
If you would like to get involved in our DSpace 7 development effort, we welcome new contributors. Just join one of our meetings or get in touch via Slack. See the DSpace 7 Working Group wiki page for more info.
If you are looking for the ongoing maintenance work for DSpace 6 (or prior releases), you can find that work on the corresponding maintenance branch (e.g.
dspace-6_x) in this repository.
Past releases are all available via GitHub at https://github.com/DSpace/DSpace/releases
Documentation / Installation
Documentation for each release may be viewed online or downloaded via our Documentation Wiki.
The latest DSpace Installation instructions are available at: https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace
Please be aware that, as a Java web application, DSpace requires a database (PostgreSQL or Oracle) and a servlet container (usually Tomcat) in order to function. More information about these and all other prerequisites can be found in the Installation instructions above.
Running DSpace 7 in Docker
DSpace is a community built and supported project. We do not have a centralized development or support team, but have a dedicated group of volunteers who help us improve the software, documentation, resources, etc.
We welcome contributions of any type. Here's a few basic guides that provide suggestions for contributing to DSpace:
- How to Contribute to DSpace: How to contribute in general (via code, documentation, bug reports, expertise, etc)
- Code Contribution Guidelines: How to give back code or contribute features, bug fixes, etc.
- DSpace Community Advisory Team (DCAT): If you are not a developer, we also have an interest group specifically for repository managers. The DCAT group meets virtually, once a month, and sends open invitations to join their meetings via the DCAT mailing list.
We also encourage GitHub Pull Requests (PRs) at any time. Please see our Development with Git guide for more info.
In addition, a listing of all known contributors to DSpace software can be found online at: https://wiki.lyrasis.org/display/DSPACE/DSpaceContributors
DSpace provides public mailing lists where you can post questions or raise topics for discussion. We welcome everyone to participate in these lists:
- firstname.lastname@example.org : General discussion about DSpace platform, announcements, sharing of best practices
- email@example.com : Technical support mailing list. See also our guide for How to troubleshoot an error.
- firstname.lastname@example.org : Developers / Development mailing list
Great Q&A is also available under the DSpace tag on Stackoverflow
Additional support options are at https://wiki.lyrasis.org/display/DSPACE/Support
DSpace also has an active service provider network. If you'd rather hire a service provider to install, upgrade, customize or host DSpace, then we recommend getting in touch with one of our Registered Service Providers.
DSpace uses GitHub to track issues:
- Backend (REST API) issues: https://github.com/DSpace/DSpace/issues
- Frontend (User Interface) issues: https://github.com/DSpace/dspace-angular/issues
By default, in DSpace, Unit Tests and Integration Tests are disabled. However, they are run automatically by Travis CI for all Pull Requests and code commits.
- How to run both Unit Tests (via
maven-surefire-plugin) and Integration Tests (via
mvn install -DskipUnitTests=false -DskipIntegrationTests=false
- How to run only Unit Tests:
mvn test -DskipUnitTests=false
- How to run a single Unit Test
# Run all tests in a specific test class # NOTE: failIfNoTests=false is required to skip tests in other modules mvn test -DskipUnitTests=false -Dtest=[full.package.testClassName] -DfailIfNoTests=false # Run one test method in a specific test class mvn test -DskipUnitTests=false -Dtest=[full.package.testClassName]#[testMethodName] -DfailIfNoTests=false
- How to run only Integration Tests
mvn install -DskipIntegrationTests=false
- How to run a single Integration Test
# Run all integration tests in a specific test class # NOTE: failIfNoTests=false is required to skip tests in other modules mvn install -DskipIntegrationTests=false -Dit.test=[full.package.testClassName] -DfailIfNoTests=false # Run one test method in a specific test class mvn install -DskipIntegrationTests=false -Dit.test=[full.package.testClassName]#[testMethodName] -DfailIfNoTests=false
- How to run only tests of a specific DSpace module
# Before you can run only one module's tests, other modules may need installing into your ~/.m2 cd [dspace-src] mvn clean install # Then, move into a module subdirectory, and run the test command cd [dspace-src]/dspace-server-webapp # Choose your test command from the lists above