Difference between revisions of "Proposed Student Projects"

From Dryad wiki
Jump to: navigation, search
(Generating Curation Reports)
(Flesh out DryadLab)
Line 36: Line 36:
 
Improve the process for generating statistics associated with Dryad. There are two types of statistics, those associated with periodic reports to stakeholders (e.g., board meetings, annual reports to funders), and those associated with the [[Global Statistics Display]].
 
Improve the process for generating statistics associated with Dryad. There are two types of statistics, those associated with periodic reports to stakeholders (e.g., board meetings, annual reports to funders), and those associated with the [[Global Statistics Display]].
  
== Flesh out DryadLab ==
+
== Lingering Issues ==
 +
 
 +
The Dryad issue-tracking system contains many issues that have not been resolved. Many of these issues could be addressed by a student. A student could approach these issues in two ways:
 +
# Identify individual issues that are tractable and solve them. These issues include problems like minor usability tweaks and documentation needs.
 +
# Identify classes of issues that occur frequently, and develop tools/processes to solve these issues.
  
 
[[Category:Work Packages]]
 
[[Category:Work Packages]]

Revision as of 11:28, 17 August 2012

Dryad occasionally has the opportunity to work with student interns through projects like the Google Summer of Code and the DataONE internship program. This page collects ideas for projects that are suitable for student work. All of these projects provide valuable progress for Dryad. They are relatively self-contained projects, requiring a minimal amount of background knowledge before the student is able to make a meaningful contribution.

Processing data packages with SWORD and ORE

Extend the DSpace SWORD interface to support BagIt data packages OAI-ORE descriptions. Upon receiving a package with an OAI-ORE description, it should be able to generate the equivalent data package and data files in the submission system. Extend the existing BagIt exporter to create equivalent packages for export purposes.

Proposed as a project for the 2012 Phyloinformatics Summer of Code.

Notes:

  • DSpace's Replication Task Suite has code for working with BagIt objects (beyond the BagIt transformer that is specific to Dryad).
  • People who may be interested in collaborating:
    • Stuart Lewis (SWORD)
    • Hardy Pottinger (U Missouri-Rolla) was planning to build similar technology
    • Marco Fabiani (Queen Mary University of London) is looking for similar technology

Metadata editing with HAMR

Build out the user interface for HAMR. Integrate HAMR with Dryad.

History:

  1. Proposed as a project to the 2012 DSpace Summer of Code, but the organization was not accepted.
  2. Proposed (in slightly more general form) as a project for the Rose-Hulman Senior Project program.

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.

An initial design for such a tool was created during a hackathon at the 2011 Code4Lib conference. This design, called HAMR, provides a good starting point for the project, but there is considerable room for a student to work with the DSpace community to determine the final design of the tool.

Improving the Dryad API

Implement the proposal for a new Dryad API.

Generating Reports

Develop more reports that are needed from the list of Curator Reports.

Improve the process for generating statistics associated with Dryad. There are two types of statistics, those associated with periodic reports to stakeholders (e.g., board meetings, annual reports to funders), and those associated with the Global Statistics Display.

Lingering Issues

The Dryad issue-tracking system contains many issues that have not been resolved. Many of these issues could be addressed by a student. A student could approach these issues in two ways:

  1. Identify individual issues that are tractable and solve them. These issues include problems like minor usability tweaks and documentation needs.
  2. Identify classes of issues that occur frequently, and develop tools/processes to solve these issues.