...
- Google Summer of Code Documentation Site
- Google Summer of Code Application Site
- DSpace Summer of Code – visit here for a list of interested mentors, information about our IRC channel, mailing lists, etc.
...
Accepted DSpace Summer of Code 2011 projects
...
Summary | Relevant DSpace component(s) | Detailed Description | Student | Mentor(s) |
---|---|---|---|---|
SKOS Authority Controls | Authority Control | @Mire has prototyped a Solr driven Authority Control capable of caching and mixing together authority sources so that they can utilized for super fast term completion and lookup. Solr is quite effective for quickly retrieving lists of values that a field should be restricted to. Likewise, when the original DSpace metadata is indexed into the Solr based authority control, the Submitter is also presented with an ad-hoc authority of existing values already contained within the repository. However, it is recognized that Authority Controls Sources are not just lists and have structural components as well. SKOS applies quite well to expressing the structured relationships between taxonomies and hierarchical vocabularies that are often relied on for Authority Control. Recent research in publishing Library of Congress Subject Authorities, Getty TGN Vocabularies etcetera confirms that SKOS is the predominant form to capture these resources for placement on the web.
| ||
WebMVC (Freemarker) UI development | modules/webmvc | WebMVC is currently under development, and is creating a new user interface based on Spring's WebMVC framework. This has the same goals as the JSPUI rewrite project in providing a clean technical implementation with business logic removed from the presentation layer. | ||
New UI built over RESTful services | dspace-api | Currently, DSpace functionality could be accessed using JSP and XML user interfaces. As in the meantime many other technologies arrived which could provide different way of user experience and UI customization, the idea is to create a new interfaces using some of the following technologies:
|
Ideas for Potential Future DSpace Summer of Code projects
Note | ||
---|---|---|
| ||
Please add your suggestions for GSoC 2011 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. |
Info | ||
---|---|---|
| ||
In our DSpace Developers Meeting on March 30, 2011, the developers in attendance voted up/down various project ideas listed here. Based on general lack of interest & support, the following projects were REMOVED:
The full discussion of this meeting is logged in our IRC logs at: http://irclogs.duraspace.org/index.php?date=2011-03-30 |
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) | ||||||
---|---|---|---|---|---|---|---|---|---|
| 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 | |||||||
Enhanced RESTful API | dspace-api | Building on previous years' REST projects, this project is to result in:
|
| ||||||
Usage statistics reports | dspace-xmlui | The new solr statistics engine in DSpace needs to generate more reports, replace the legacy "site-wide" statistics report that is still in use, and make use of
| |||||||
RTMP A/V streaming integration | dspace-api | Integrate DSpace authentication, authorization and bitstream dissemination with an open source RTMP streaming server such as RED5.
|
Note | ||
---|---|---|
| ||
Please add your suggestions for GSoC 2011 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. |
Info | ||
---|---|---|
| ||
In our DSpace Developers Meeting on March 30, 2011, the developers in attendance voted up/down various project ideas listed here. Based on general lack of interest & support, the following projects were REMOVED:
The full discussion of this meeting is logged in our IRC logs at: http://irclogs.duraspace.org/index.php?date=2011-03-30 |
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) | ||||||
---|---|---|---|---|---|---|---|---|---|
Anchor | GFDAO | GFDAO | 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). SKOS Authority Controls | Authority Control | @Mire has prototyped a Solr driven Authority Control capable of caching and mixing together authority sources so that they can utilized for super fast term completion and lookup. Solr is quite effective for quickly retrieving lists of values that a field should be restricted to. Likewise, when the original DSpace metadata is indexed into the Solr based authority control, the Submitter is also presented with an ad-hoc authority of existing values already contained within the repository. However, it is recognized that Authority Controls Sources are not just lists and have structural components as well. SKOS applies quite well to expressing the structured relationships between taxonomies and hierarchical vocabularies that are often relied on for Authority Control. Recent research in publishing Library of Congress Subject Authorities, Getty TGN Vocabularies etcetera confirms that SKOS is the predominant form to capture these resources for placement on the web. Disseminator Framework | ItemView | ||
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 |||||
Enhanced RESTful API | dspace-api | Building on previous years' REST projects, this project is to result in:
|
| ||||||
WebMVC (Freemarker) UI development | modules/webmvc | WebMVC is currently under development, and is creating a new user interface based on Spring's WebMVC framework. This has the same goals as the JSPUI rewrite project in providing a clean technical implementation with business logic removed from the presentation layer. Usage statistics reports | dspace-xmlui | The new solr statistics engine in DSpace needs to generate more reports, replace the legacy "site-wide" statistics report that is still in use, and make use of RTMP A/V streaming integration | dspace-api | Integrate DSpace authentication, authorization and bitstream dissemination with an open source RTMP streaming server such as RED5. New UI built over RESTful services | dspace-api | Currently, DSpace functionality could be accessed using JSP and XML user interfaces. As in the meantime many other technologies arrived which could provide different way of user experience and UI customization, the idea is to create a new interfaces using some of the following technologies: Client run interface (maybe ExtJS other JavaScript based, probably developed by the GSoC student, or JavaFX, or even Flex based) backed by REST API for DSpace.The most important functionality this interface should deliver is user interface which has attractive look and feel and provides users with enhanced usability. Additionally, easier customization of resulting interface would be additionally appreciated. As of project complexity and project deadlines, support for many administrative functions in the interface is not so important in current stage. Attractive, easy to use and customize interface based on currently appealing technologies would further promote DSpace capabilities and play role in its adoption. Client rendered interface based on REST would further decrease load on the server and therefore push DSpace deployment for bigger repositories. Note: RESTful interface over DSpace is developed during previous years under GSoC. It has fully descriptions and specifications available at the web page specified. The interface is to be delivered and developed based on the specifications provided on REST API web page. The REST interface is finished at ~90%; the testing could be done directly with the interface or in coordination with the author. | |
New UI built over DSpace API, based on popular frameworks |
| Currently, DSpace functionality could be accessed using JSP and XML user interfaces. As in the meantime many other technologies arrived which could provide different way of user experience and UI customization, the idea is to create a new interfaces using some of the following technologies:
| |||||||
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.
| |||||||
Scriptable Curation Tasks | dspace-xmlui |
| |||||||
Improve Submitter User Experience | dspace-xmlui | Generally clean up submission process, especially at UI level, and provide a more user friendly submitter experience. (Need to brainstorm out exactly what changes to make obviously)
| Peter Dietz |
...