tomay / rebioma

Automatically exported from code.google.com/p/rebioma
0 stars 0 forks source link

taxonomic authority manager #387

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
This is a placeholder for the issue of taxonomic authority manager. In short, 
we need a better way to update the taxonomic authority (TA). The current method 
is to upload the TA as a csv to the server. Another (duplicate) public copy is 
kept on google docs. Is there a better method for this? This requires a wider 
discussion, and this may end up as several related issues. We have recently 
requested funding to develop this. 

Relates also to issue #374, taxonomic revalidation

Original issue reported on code.google.com by tom.alln...@gmail.com on 10 Feb 2011 at 12:02

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Duplicate of issue #130, Taxonomy Authority Administration Page

One (of many) consideration here is that by bringing this into the portal, many 
of the utilities that are available in a spreadsheet are lost (such as sorting, 
formulas, searching, ease of adding new columns, auto-numbering, etc. etc.). 

Original comment by tom.alln...@gmail.com on 15 Feb 2011 at 12:35

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Issue 130 has been merged into this issue.

Original comment by tom.alln...@gmail.com on 18 Feb 2011 at 12:44

GoogleCodeExporter commented 9 years ago
Some suggested ways of implementing this
1. On the portal directly, as a page available to administrators that links to 
a database table
2. Continue to use the Google Doc spreadsheet, but access this via the docs 
api, rather than through a separate csv table maintained on the server
3. Use EOL LifeDesks and related tools to maintain classification hierachies, 
access these via the EOL api (http://www.eol.org/api)
4. Use Google Fusion Tables to maintain authority, share with TRB, edit and 
access through the gft api. Fusion tables have advantages over Google docs: it 
is a true database, allows vertical integration, designed for this case i.e. 
domain specific knowledge 

Original comment by tom.alln...@gmail.com on 18 Feb 2011 at 12:49

GoogleCodeExporter commented 9 years ago

Original comment by tom.alln...@gmail.com on 18 Feb 2011 at 12:50

GoogleCodeExporter commented 9 years ago
Closing; the team has their own method for managing the TA, this is just more 
complication

Original comment by tom.alln...@gmail.com on 29 Oct 2012 at 12:36