Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Project Title / Summary

Relevant DSpace component(s)

Detailed Description / Links

Mentor volunteer(s)

TranslateWiki Integration




The DSpace community has approached (TWN), the mediawikibased platform for interface translation of open source projects. The initial discussions are promising and the TWN community is currently building support for the Apache Cocoon message format that is used by XMLUI. We need an ambitious GSOC student to connect the dots, working with both communities in extending the integration and ensuring that in the end, the threshold is lowered for external translators to provide interface translations for DSpace.

Related Links:

Bram Luyten

Virtual Sets: Separate the internal repository structure from the navigation structure




Currently, Dspace’s the hierarchical structure used in DSpace allows to share sharing items between collections by explicitly declaring these relations on each item. However, DSpace does not allow to relate a collection or a sub-community between two or more communities.

Virtual Sets are arbitrary aggregations of Dspace DSpace Objects and criteriascriteria, composed of:

  • arbitrarily selected communities, collections and/or items,
  • dynamic results from criteriascriteria/queries (logical expressions. ; e.g. SOLR Solr queries)
  • other declared Virtual Sets (initially, cycles are not allowed)

Virtual Sets in DSpace would allow the creation of complex navigation structures regardless of the hierarchical (perhaps administrative) structure of communities and collections.

Structures, as described above, are supported in at least another repository software such as Fedora-based Hydra due to its generic object model.

 The initial implementation would affect the dspace-xmlui component. However, further extensions of this implementation would at least involve the modification of the dspace-api component too, possibly implementing the Virtual Sets as api component and either of the web UIs, since both now use Discovery (Solr) by default. Virtual Sets should be implemented at the dspace-api level for DSpace Objects to offer more orthogonal features like Virtual Sets backup, export and exposure through OAI-PMH. Stretch goals would include making use of Virtual Sets in other interfaces like REST and/or OAI.

Related links: 

Ivan Masár
create a DSpace-Puppet modulevagrant-dspaceDevelop a DSpace-Puppet module for deploying DSpace, and provisioning DSpace-related services. The goal would be to deploy on at least one popular Linux OS, and likely the target will be Debian/Ubuntu since testing will be done with Vagrant-DSpace, which currently uses only Ubuntu. The final product should be useful for deploying DSpace to a cloud infrastructure, or really any server configured to run Puppet (in other words, the module should make no assumptions that rely upon paths used by Vagrant). A stretch goal for this project will be to make the puppet module OS-agnostic, and have it run on both Debian/Ubuntu as well as CentOS/RHEL. But just meeting the Ubuntu target would be sufficient for this project. The puppet module already built for use in Vagrant-DSpace would be a great starting point. The module, when complete, should enable an operator to go from a standard OS base image to a running instance of DSpace, complete with a container to host the application, and (optionally) a PostgreSQL database for metadata.Hardy Pottinger