Re: [Treebase-devel] curation workflow

[Ryan S. <rsc...@ac...>]

(moving this onto the treebase-devel list)

> So... the upshot is that downloading a matrix from the matrix tab is  
> a temporary work-around until PhyloWS gets fixed.

Thanks. I didn't realize that different portions of the interface used  
different methods to retrieve data. Is there a reason to keep it this  
way?

Unfortunately, I can't test it right now, as the search system on  
8ball is currently down.


I forgot to mention that our current curation workflow is now  
available at
https://www.nescent.org/wg_dryad/TreeBASE_Curation

I had wanted to manage the bibliographic curation work within Endnote  
to take advantage of the more structured interface, but after testing  
a bit, I have found that Endnote makes it too easy to accidentally add  
irrelevant or duplicate citations to the database. So now, I think it  
may be best to keep the bibliographic information in the Google  
spreadsheet (and back it up periodically). When we have all of the  
citations, one person could go through the entire sheet to ensure  
consistency in journal names, etc. Does this sound reasonable? Or is  
there a way to disallow Endnote from adding new citations?

--- Ryan