Ideas for Potential DSpace Summer of Code projects
Add your ideas here!
Please add your suggestions for GSoC 2012 projects related to DSpace! If you are interested in mentoring, please let us know! Also, be sure to visit the listing of Past GSoC Project Ideas below, to see if anything there is still relevant.
Please add your own ideas to the table below, and feel free to volunteer as a mentor for any existing idea
Summary |
Relevant DSpace component(s) |
Detailed Description |
Mentor volunteer(s) |
---|---|---|---|
Stop Using Email as User Identifier |
EPerson |
Use of email address as a persistent identifier for the DSpace conflicts with the fact that email addresses are not persistent. Email addresses go away and/or are reassigned to other individuals. There are also policy concerns with Authenticators like Shibboleth and CAS that may or may not deliver an email address as a organizational policy. |
|
GFDAO (Generic Fedora Data Access Objects) |
storage-triplestore |
Bring together the storage-fedora and storage-triplestore projects to produce a Fedora store based persistence tier that includes use of SPARQL to retrieve "Related and/or Contained" Fedora Objects. Objective is: That once DSpace Communties, Collections, and Items are represented as Fedora Objects with relationships captured in RELS-EXT, then a data persistence and mapping layer will need to be engineered for DSpace / Fedora interaction. Such a Data Access tier will provide a suite of Domain Model Centric Data Access Objects that will provide a DOFM (DSpace Object Fedora Mapping). Semantic Queries will be utilized to acquire sub collections, sub-communities, Items and parent objects. Further thought can be placed into creating a generic Fedora Data Access Object that is capable of resolving any RELS-EXT (or other rdf based relation for that matter). |
|
Disseminator Framework |
ItemView |
A Disseminator Framework will associate Disseminators with Items and/or Bitstreams, Disseminators will combine METS file description and behavior sections to supply the user interface with a standard representation of the dissemination services that can be applied to a content bitstream in DSpace. See for further background:
|
|
Extend Metadata Framework to Support Stronger Typing and Validation |
MetadataValue |
Extend the DSpace Metadata Domain Model to support the following features:
|
|
Rewrite Packager Framework |
dspace-api |
Refactor Packagers to support Chain of Command |
|
DSpace Core Domain Model |
dspace-api |
Domain Model |
|
Accessibility |
dspace-api |
DSpace is selected as an institutional repository platform for one special library for the blind (details come later). Its implementation/adaptation for institutional use is currently in progress (near end-stage). The institution would be willing to share some ideas, requirements and code already done in order to make solution widely available for institutions of similar type.
|
|
Enhance REST-API Implementation |
REST API |
Update the REST API to use a more common framework (like Spring WebMVC or Jersey), rather than the current Sakai bus implementation. |
Needs mentor(s) |
Metadata Reconciliation with Authoritative Sources |
EditItemStatus |
Build a tool that allows curators to compare DSpace metadata with metadata from authoritative sources. The tool will allow curators to see DSpace metadata alongside metadata from a system such as CrossRef or PubMed. Individual metadata fields will be color-coded according to the degree of consistency. Curators will be able to click a button for each metadata field they wish to import from the authoritative source. |
|
Enhancements to DSpace Statistical Reports, including one or more of the following: Develop Visualizations, tabbed/paginated inteface, and/or "Export to CSV" |
Solr Statistics Engine |
The current DSpace Solr Statistics Engine interface is rather simplistic in nature. Maybe it's time to spice it up a bit and add some better visualizations (via something like Google Charts API). It also could be worthwhile to paginate or tab the interface, both to help improve performance (less queries on one page = better performance) and so that administrators are first shown a "general summary" page, but can choose to visit other pages/tabs to get more detailed statistics in the area of interest.
|
Needs mentor(s) |
Past Ideas for Potential DSpace GSoC projects
We have archives of all our Past GSoC Ideas Pages still available for reference/ideas. However, you should check with the available mentors before suggesting any of these older project descriptions. In some cases these projects may require rethinking to bring them up to date.
- DSpace Summer of Code Ideas 2012
- DSpace Summer of Code Ideas 2011
- DSpace Summer of Code Ideas 2010
- DSpace Summer of Code Ideas 2009
- DSpace Summer of Code Ideas 2008
Past DSpace GSoC Projects
- 2011 Projects listed on GSoC 2011 Projects page.
- For years prior to 2011, please visit Past DSpace Summer of Code Projects.