Replied: Sun, 01 Mar 2009 22:46:01 -0500 Replied: Sun, 01 Mar 2009 22:36:23 -0500 Return-Path: william.piel@yale.edu Delivery-Date: Sun Feb 08 22:47:59 2009 Return-Path: Delivered-To: mjd-final-delivery-1@plover.com Received: (qmail 5721 invoked by uid 119); 8 Feb 2009 22:47:59 -0000 Delivered-To: mjd-filter-sa@plover.com Received: (qmail 5713 invoked by uid 119); 8 Feb 2009 22:47:56 -0000 Delivered-To: mjd-filter-deliver2@plover.com Return-Path: X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on plover.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE autolearn=ham version=3.2.3 Received: (qmail 5702 invoked by uid 119); 8 Feb 2009 22:47:56 -0000 Delivered-To: mjd@plover.com Received: (qmail 5686 invoked from network); 8 Feb 2009 22:47:56 -0000 Received: from pantheon-po08.its.yale.edu (130.132.50.50) by 192.168.1.102 with SMTP; 8 Feb 2009 22:47:56 -0000 Received: from [10.0.1.195] ([99.145.99.61]) (authenticated bits=0) by pantheon-po08.its.yale.edu (8.12.11.20060308/8.12.11) with ESMTP id n18MkbD6019909 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 8 Feb 2009 17:46:38 -0500 Cc: Mark Dominus , Rutger Vos Message-Id: <4BB519AD-8458-4F99-A2A8-0B2A3907D8C7@yale.edu> From: William Piel To: Val Tannen In-Reply-To: <46874146-F1B3-4E93-8883-FABB054625AD@cis.upenn.edu> Content-Type: multipart/alternative; boundary=Apple-Mail-2-275443425 Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: Master task list right now Date: Sun, 8 Feb 2009 17:46:37 -0500 References: <1233607488.31015.41.camel@localhost> <46874146-F1B3-4E93-8883-FABB054625AD@cis.upenn.edu> X-Mailer: Apple Mail (2.930.3) X-YaleITSMailFilter: Version 1.2c (attachment(s) not renamed) --Apple-Mail-2-275443425 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Regarding which tasks are needed to be completed before beta-testing can start... These surely need to be done prior to beta-testing: 1. Title: Populate JRUAN schema with data from treebase 1 2. Title: Missing original nexus files for matrices 3. Title: What about the other 39 matrices? 4. Title: Can a user change their password? 5. Title: Set test flag in uploaded submissions These would be nice to have done by then, but not critical for beta- testing: 6. Title: Reviewer read-only access to studies 7. Title: Taxon search 8. Title: TB1 importation checking 9. Title: Resolve TB1_STUDYID / ACCESSIONNUMBER confusion These are needed, at a minimum, prior to TB2 going public: 10. Title: Taxon search using ncbi classification 11. Title: Simple tree-delivering URL-API so that we can use a non- crippled version of PhyloWidget on our search page (currently we're stuck with an old crippled version that includes the "save to database" feature) Item number 1 has a lot of stuff in it, including importing the latest taxon-intel dump. It is important that the taxon-intel dump gets fully imported prior to testing because beta-testers will be creating new taxon_variant and taxon records, even if their test submissions are not set to be published and even if their test submissions are later deleted. We don't want beta testers creating taxon-intel records that are already present in TB1 -- that would create duplicates once the taxon-intel dump gets finally loaded. This does create a new "to do" item: I will need a taxon-intel dump from TB2 after the beta-testing is over but before the final TB1 data migration happens. This is so that I can bring the TB1 taxon-intel up- to-date with the TB2 taxon-intel before I create new TB1 taxon-intel records and before I do a last migration to TB2. bp --Apple-Mail-2-275443425 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable

Regarding which tasks are needed to be completed before = beta-testing can start...

These surely need to = be done prior to beta-testing:

1. Title: = Populate JRUAN schema with data from treebase 1

2. Title: = Missing original nexus files for matrices

3. Title: What = about the other 39 matrices?

4. Title: Can a user change = their password?

5. Title: Set test flag in uploaded = submissions

These would be nice to have done by = then, but not critical for = beta-testing:

6. Title: Reviewer read-only = access to studies

7. Title: Taxon search

8. = Title: TB1 importation checking

9. Title: Resolve TB1_STUDYID = / ACCESSIONNUMBER confusion

These are needed, = at a minimum, prior to TB2 going = public:

10. Title: Taxon search using ncbi = classification

11. Title: Simple tree-delivering URL-API so = that we can use a non-crippled version of PhyloWidget on our search page = (currently we're stuck with an old crippled version that includes the = "save to database" feature)

Item number 1 has a = lot of stuff in it, including importing the latest taxon-intel dump. It = is important that the taxon-intel dump gets fully imported prior to = testing because beta-testers will be creating new taxon_variant = and taxon records, even if their test submissions are not set to = be published and even if their test submissions are later deleted. We = don't want beta testers creating taxon-intel records that are already = present in TB1 -- that would create duplicates once the taxon-intel dump = gets finally loaded.

This does create a = new "to do" item: I will need a taxon-intel dump from TB2 after the = beta-testing is over but before the final TB1 data migration = happens. This is so that I can bring the TB1 taxon-intel up-to-date with = the TB2 taxon-intel before I create new TB1 taxon-intel records and = before I do a last migration to = TB2.

= = --Apple-Mail-2-275443425--