You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
how would we decide upon what particular columns to keep on these lists.
I do not know what particular columns do researchers query the most, so that if we include them it would help them a lot
I think there might be a possibility when a researcher doesn't know about this thing (when he/she is new to pyobis and won't lookup documentation in much detail but at a glance. Because when I do something I see the docs at a glance, do some experimentation to understand it by self and then get back to docs.)
they will need to find which columns are present in the which curated list and that might add up to efforts
but this idea is really great which might ease efforts and make it more easier and friendly to the less code-friendly person.
Working with occurrence data I feel overwhelmed by the number of columns.
Would it be a good idea to allow for easy subsetting of columns?
Here is some code in which I have done that:
We could include arrays of curated column lists so that a user could do something like:
To drop everything but the curated list of "taxonomic" and "temporal" columns. Thoughts?
The text was updated successfully, but these errors were encountered: