Difference between revisions of "Hackathon 2013/DataIntegration"
From TaxonWorks Wiki
Julieallen34 (Talk | contribs) (Created page with "The Data Integration pitch is a combination of many pitches for how to use TaxonWorks with other databases: *GenBankIntegration -- be able to pull genetic sequences from OTUs...") |
Julieallen34 (Talk | contribs) |
||
Line 2: | Line 2: | ||
*GenBankIntegration -- be able to pull genetic sequences from OTUs from TaxonWorks: | *GenBankIntegration -- be able to pull genetic sequences from OTUs from TaxonWorks: | ||
− | **Work to write Ruby script to pull sequence data from GenBank | + | **Work has started to write Ruby script to pull sequence data from GenBank |
− | * | + | *PhylotasticIntegration -- Patch into the Phylotastic architecture (once it is up and running) to add a list of species from TaxoNWorks and get a tree |
+ | |||
+ | *NexMLParser -- add a NexML file with any information of choice | ||
+ | |||
+ | *VizualizationOnMaps -- Specimen on google maps, shapefiles, tile srves from GBIF, map of life API |
Revision as of 09:33, 4 October 2013
The Data Integration pitch is a combination of many pitches for how to use TaxonWorks with other databases:
- GenBankIntegration -- be able to pull genetic sequences from OTUs from TaxonWorks:
- Work has started to write Ruby script to pull sequence data from GenBank
- PhylotasticIntegration -- Patch into the Phylotastic architecture (once it is up and running) to add a list of species from TaxoNWorks and get a tree
- NexMLParser -- add a NexML file with any information of choice
- VizualizationOnMaps -- Specimen on google maps, shapefiles, tile srves from GBIF, map of life API