Getting Started¶
Source Code¶
Currently the source code for both implementations of DataSpace and the Open Access Repository are managed and maintained on the GitLab repository. Please note that the DataSpace code base is maintained on the branch dataspace-prod, and that the Open Access Repository code base is maintained on the branch oar-prod.
DataSpace¶
Server Environments¶
DataSpace installations are available throughout three server environments. These are currently deployed using the Ubuntu 18.04 LTS operating system:
Open Access Repository (OAR)¶
Server Environments¶
OAR installations are also deployed on three server environments:
Repositories¶
Actively maintained repositories¶
Because DSpace is particularly difficult to work with, a collection of repositories have been created externally to aid with bulk ingest, reporting, and other administrative tasks.
pulibrary/dspace-cli: A collection of dataspace-specific administrative jruby scripts inherited from OIT that answer common stakeholder questions.
pulibrary/dspace-jruby: A jruby wrapper for any DSpace instance. This is used heavily in pulibrary/dspace-cli
pulibrary/dspace-osti: An administrative task that scrapes Dataspace and publishes to OSTI. This is a process that needs to be run annually for PPPL to comply with grant requirements.
pulibrary/orangetheses: Harvests Senior Theses from dataspace and indexes them into the catalog.
PrincetonUniversityLibrary/dspace-smoke-tests: Automated smoke tests for PUL DSpace instances. Written in Cypress.
PrincetonUniversityLibrary/dataspace: A copy of dataspace in GitHub so that our stakeholders can make PRs to edit XML when necessary.
pulibrary/etd_transformer: A ruby-based solution to the complicated bulk ingest process of senior theses.
Other Useful Links¶
ZenHub boards
Princeton Research Data and Open Scholarship: Tracks tickets specific to PRDS & PPPL.
dspace: Tracks maintenance and other miscellaneous work not necessarily tied to a stakeholder.
