Project

General

Profile

Roadmap

Testing and Upgrading + PGP.ca features

open

over 10 years late (04/16/2014)

63%

103 issues   (73 closed — 30 open)

Testing and Upgrading + PGP.ca features

Installation

Installing the Tapestry application
Set up an OAuth service

Development

Customization
Internationalization
Theming
Development cycle → for hackers and committers

Specifications, requirements, plans

Design sketches → for sample tracking and GET-Evidence-2
Plug-in system notes
Account suspension, deactivation, withdrawal

Related issues
Feature #2419: ci.curoverse.com automatically runs user model tests Actions
Feature #2422: exam automated tests Actions
Feature #2423: enrollment step automated tests Actions
Feature #2428: upgrade to ruby 1.9.3 Actions
Feature #2429: upgrade to rails 3.1 Actions
Feature #2430: upgrade to rails 3.2 Actions
Feature #2431: upgrade to ruby 2.1 Actions
Feature #2501: Much more flexible consent forms Actions
Feature #2518: Allow views and partials to be dynamically overridden Actions
Feature #2979: user email address on contact form should be used for reply-to:, from: should be configurable Actions
Feature #3025: Add an admin interface feature to export all enrolled users + shipping address as a csv file. Actions
Feature #4050: As a participant, I can choose to reveal my real name on my public profile. I can also remove my real name from my public profile. Actions
Feature #4766: Upgrade oauth1 code for google doc/spreadsheet sync to oauth2 Actions
Feature #4978: Distinguish pgp-originated and other files on public profiles Actions
Feature #4979: Improve sample tracking to allow for bulk marking of samples Actions
Feature #6467: upgrade to reCAPTCHA v2 Actions
Feature #6961: Simplify Tapestry/Open Humans account link flow Actions
Feature #7424: README that links to main repo Actions
Feature #7462: Always redirect Open Humans user back to OH Actions
Feature #7815: If a dataset has been released to a user but they have not seen it yet, force-redirect to /specimen_analysis_data after they log in Actions
Feature #8251: fix FAQ link Actions
Feature #9284: Welcome e-mail feature Actions
Idea #2502: Make all the site-specific labels configurable Actions
Idea #2503: Make it possible to disable/enable "sections" Actions
Idea #2526: Make user-acceptance of TOS optional Actions
Idea #2533: Basic clean-up of tests, as a foundation for working on specific ones Actions
Idea #2539: Cells can also be overridden Actions
Idea #2544: The "site override" feature is tested Actions
Idea #2549: Configurable Signup Conditions Actions
Idea #2552: Configurable mini-consent form and validations Actions
Idea #2850: Comprehensive "Sectioning" of Tapestry Actions
Idea #2962: Can deploy in a sub URI Actions
Idea #4662: Possible to disable Shipping Addresses as a section Actions
Idea #4980: Users can connect their Tapestry account to Open Humans via OAuth2 Actions

Tapestry - Next sprint

open

over 10 years late (05/07/2014)

0%

2 issues   (0 closed — 2 open)

Next sprint

Installation

Installing the Tapestry application
Set up an OAuth service

Development

Customization
Internationalization
Theming
Development cycle → for hackers and committers

Specifications, requirements, plans

Design sketches → for sample tracking and GET-Evidence-2
Plug-in system notes
Account suspension, deactivation, withdrawal

Related issues
Feature #5378: Public profiles: add JSON for Samples Actions
Feature #5380: Public profiles: add JSON for Enrollment History Actions

Interpretation automation

open

over 4 years late (06/30/2020)

80%

31 issues   (23 closed — 8 open)

Interpretation automation

About Tapestry

Tapestry handles participant interaction for Personal Genome Projects. It is in production use at the Harvard and UK Personal Genome Projects. It is free software licensed under the GNU Affero General Public Licence v3 or later, and the source code is available on Github.

Installation

Installing the Tapestry application
Set up an OAuth service

Development

Customization
Internationalization
Theming
Development cycle → for hackers and committers

Specifications, requirements, plans

Design sketches → for sample tracking and GET-Evidence-2
Plug-in system notes
Account suspension, deactivation, withdrawal
Submitting data from a third-party study

Related issues
Feature #8688: Accept authenticated API calls from data providers to add datasets to a public profile Actions
Feature #8689: Trigger an arvados job to retrieve the data and import it into Keep Actions
Feature #8697: Check for finished download/processing jobs Actions
Feature #8698: When UserFile data is updated, if it has a suitable data type, submit report-generator jobs Actions
Feature #8699: Add report status/links to "show user_files" page Actions
Feature #8700: Arvados job/pipeline generates GET-Evidence HTML report from VCF Actions
Feature #8701: Arvados job/pipeline generates ClinVar HTML report from VCF Actions
Feature #8707: Arvados job: download data from remote site into Keep Actions
Feature #9027: Incorporate coverage info from get-evidence dataset_reports in publication statistics Actions