Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

associatedTaxa #223

Closed
qgroom opened this issue Aug 7, 2016 · 10 comments
Closed

associatedTaxa #223

qgroom opened this issue Aug 7, 2016 · 10 comments

Comments

@qgroom
Copy link

qgroom commented Aug 7, 2016

Not a bug, but a feature request perhaps.
I'd like to be able to extract the associatedTaxa field from occurrences.
For example, if I have a parasite I'm interested in how can I pull out all the host species mentioned in datasets?
Regards
Quentin

@sckott
Copy link
Contributor

sckott commented Aug 7, 2016

Thanks for your question. Can you give some example parasite names you'd be interested in.

@qgroom
Copy link
Author

qgroom commented Aug 7, 2016

I'm interested in a wide variety of organism intereactions, I more interested if people are collecting the information, rather than the data itself.
Some examples of plant parasites I picked out as examples are...
Nuytsia floribunda
Cuscuta europaea
Arceuthobium oxycedri
Anthobolus filifolius
Viscum album
Balanophora fungosa
Orobanche uniflora
Orobanche minor
Monotropa hypopitys
Conopholis americana

Also good examples of animal parasites are...
Remora remora
Conopholis americana
Simenchelys parasitica
Dasypsyllus gallinulae
Pinnotheres pisum
Varroa destructor
Sacculina carcini
Clonorchis sinensis
Andricus quercuscalifornicus
Phytomyza ilicis

@sckott
Copy link
Contributor

sckott commented Aug 7, 2016

thanks for the examples

I more interested if people are collecting the information, rather than the data itself.

so you mainly want presence/absence of of the associatedTaxa field? or any host information, regardless of field? because there appears to be host notes in other fields, e.g., occurrenceRemarks in this occurrence http://api.gbif.org/v1/occurrence/1211989229

@qgroom
Copy link
Author

qgroom commented Aug 8, 2016

I need to see what is in it too, so that I can judge how useful it is.
Yes, it would be useful to see what it in occurrenceRemarks. I suppose there might also be data in associatedOccurrences, associatedOrganisms & organismRemarks.

@sckott
Copy link
Contributor

sckott commented Aug 11, 2016

@qgroom This seems like a use case that'd be more useful applied across data sources, i'll get something up on github and ping you soon

@sckott
Copy link
Contributor

sckott commented Aug 12, 2016

@qgroom started something here https://github.com/ropenscilabs/hoasts to play around with ideas

@qgroom
Copy link
Author

qgroom commented Aug 12, 2016

Great! I'm just leaving for two weeks holiday, but I'll take a look once I get back, sooner if we have internet.

@sckott
Copy link
Contributor

sckott commented Aug 12, 2016

sounds good

@sckott
Copy link
Contributor

sckott commented Oct 1, 2016

@qgroom closing this given hoasts, hope that's okay

@qgroom
Copy link
Author

qgroom commented Oct 1, 2016

Sure! It is an interesting and important subject and I'll have to see if I
can work on it more.
Quentin

Dr. Quentin Groom
(Botany and Information Technology)

Botanic Garden Meise
Domein van Bouchout
B-1860 Meise
Belgium

ORCID: 0000-0002-0596-5376 http://orcid.org/0000-0002-0596-5376

Landline; +32 (0) 226 009 20 ext. 364
FAX: +32 (0) 226 009 45

E-mail: quentin.groom@plantentuinmeise.be
Skype name: qgroom
Website: www.botanicgarden.be

On 1 October 2016 at 03:38, Scott Chamberlain notifications@github.com
wrote:

@qgroom https://github.com/qgroom closing this given hoasts, hope
that's okay


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#223 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFRj0DhTubXrNwdt2bFWWBzWFDWHDTVvks5qvbmzgaJpZM4JehE9
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants