The DSpace community has approached TranslateWiki.net (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:

• JIRA Ticket describing the current status of the dialogue between DSpace and TWN

Related DSpace Components:

• dspace-api-lang : JSPUI and API level language packs (in Java Properties file format)
• dspace-xmlui-lang : XMLUI language packs (in Apache Cocoon XML format)
• dspace-xmlui : XML-based interface based on Apache Cocoon
• dspace-jspui : Custom JSP-based interface

Recommended Skills:

• Multilingual and/or translation experience
• Familiarity with Java web application Internationalization

Difficulty Level: Medium

Currently, the hierarchical structure used in DSpace allows 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 Objects and criteria, composed of:

• arbitrarily selected communities, collections and/or items,
• dynamic results from criteria/queries (logical expressions; e.g. 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-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:

• Sets, sets or sets? 

Related DSpace Components:

• dspace-api : DSpace Java API
• dspace-xmlui : XML-based interface based on Apache Cocoon
• dspace-jspui : Custom JSP-based interface

Recommended Skills:

• Java programming experience

Difficulty Level: High

Develop a Puppet-DSpace 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.

Related DSpace Components:

• vagrant-dspace : A Vagrant setup for DSpace development. It includes the "starting point" for a puppet-dspace module under "/modules/dspace/"

Recommended Skills:

• Experience with Puppet or similar tools (e.g. Chef). At a minimum some base familiarity and even some Ruby experience (which Puppet is based on).
• Familiarity with Vagrant, or willingness to learn.

Difficulty Level: Medium

MDS is an experimental offshoot of DSpace in which new ideas may be prototyped and examined. Recently a REST API (with CRUD operations, etc) has been added to DSpace 4. A valuable 'proof of adequacy' is building an entire functional web UI backed only by the API. The goal of this project is to construct such an admin UI for MDS, using a modern, agile web application framework. A proof of concept using AngularJS already begun could serve as a basis for further work.

Related DSpace Components:

• dspace-rest : The REST API  which now ships with DSpace 4.

Recommended Skills:

• Experience or familiarity with one or more agile web frameworks
• Experience or familiarity with buiding agile interfaces against a REST API

Difficulty Level: Medium to High