Resource Allocation

This page defines broad areas of resposibility, specifically regarding technical development, to keep track of which work is happening where (and which pieces of work are still unassigned).

Ryan Scherle

 * day-to-day coordination/administration
 * (technical) interaction with journal representatives
 * feature development and bug fixes as needed
 * assist w/ helpdesk duties
 * usability testing: getting the system and prototypes in front of scientists and getting feedback
 * user interface design: improving the layout of pages and workflow based on feedback from usability testing

@mire

 * Any development that goes deeply into DSpace, or is of interest to the wider DSpace community.
 * see Work Packages @mire

Craig Willis

 * HIVE vocabulary server
 * general HIVE documentation/support
 * integration of vocabularies to Dryad submission/curation system
 * taxonomic search
 * automatic metadata extraction

Peter Midford

 * maintenance of journal metadata import process and submission system
 * misc fixes to other code as needed
 * assist w/ helpdesk duties

Peggy Schaeffer

 * (non-technical) communication with current partner journals & Board members
 * (non-technical) communication with prospective partner journals
 * communication with authors to solicit high-impact data
 * general public relations and training
 * communication via blog, Twitter, Facebook & posts to Partners and Users lists
 * wiki maintenance and updating

Elena Feinstein

 * curation of new deposits
 * development of curation manuals
 * supervise student curators (when needed)
 * "first line of defense" for helpdesk duties
 * training/outreach: developing documentation or videos aimed at various communities. Presenting tutorials or otherwise representing Dryad at scientific conferences.
 * development of metadata standards
 * metadata maintenance and authority control
 * selection of content for educational resources, development of educational resources
 * research in metadata generation?
 * reports to journals on submissions
 * PR for "important" data submissions
 * training/outreach: developing documentation or videos aimed at various communities. Presenting tutorials or otherwise representing Dryad at scientific conferences.
 * design of DryadLab

Heather Piwowar

 * data citation
 * best practices
 * opportunistic research: What do we need to know to optimize the effectiveness of Dryad?

Responsibilities that currently float between people

 * integration: designing and developing interfaces for handshaking with TreeBASE/GenBank/DataONE
 * replication
 * preservation
 * author tools: identifying needs for specialized tools that work within the repository, and implementing tools to fulfill those needs. (e.g., JPIP interface for working with large images, streaming interface for videos, subsetting interface for large data files, etc.)
 * research in metadata generation: the work that was formerly scheduled for Mike Graves