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

Change bulk upload (via wizard or API) to allow for traits not in the trait_covariate_associations table #459

Closed
gsrohde opened this issue Nov 10, 2016 · 5 comments
Assignees

Comments

@gsrohde
Copy link
Contributor

gsrohde commented Nov 10, 2016

See terraref/computing-pipeline#193 (comment) for discussion of how this should work.

@gsrohde gsrohde self-assigned this Nov 10, 2016
@gsrohde gsrohde added this to the February 2017 milestone Feb 3, 2017
@gsrohde
Copy link
Contributor Author

gsrohde commented Mar 3, 2017

Changes for the API have been implemented (but not deployed). This changes the API behavior as follows.

[From issue #193:]

  1. Any column heading that matches an existing variable name will be recognized as a trait variable except (a) if it is listed in the trait_covariate_associations table as a covariate; (b) in the unlikely event that it also happens to match one of the canonical column headings—citation_author, citation_year, citation_title, citation_doi, cultivar, species, site, treatment, utc_datetime, local_datetime, date, yield, n, SE, notes, access_level, or entity. (This rule is mainly to prevent everything from breaking if someone somewhat perversely adds one of these unlikely names as the name of a variable.)
  2. The use cases for adding a row to the trait_covariate_associations table are (a) we wish to recognize a column heading as the name of a covariate variable associated with some (or some set of) trait variable(s); (b) we wish to enforce a requirement for certain trait variables that certain associated covariates always be specified. (For example, on https://betydb.org, leafT must always be specified when trait data for Vcmax, quantum_yield, Amax or certain other variables is uploaded.)

In addition, it is an error if there is a variable name listed in the heading that corresponds to a covariate in the trait_covariate_associations table without there also being a corresponding trait name.

gsrohde added a commit that referenced this issue Mar 9, 2017
…rd (issue #459) and removed "pending" from related tests.
@gsrohde
Copy link
Contributor Author

gsrohde commented Mar 15, 2017

Fixed by release 4.15.

@gsrohde gsrohde closed this as completed Mar 15, 2017
@gsrohde gsrohde reopened this Mar 16, 2017
@gsrohde
Copy link
Contributor Author

gsrohde commented Mar 16, 2017

Re-opening. This feature is not yet working properly.

@gsrohde
Copy link
Contributor Author

gsrohde commented May 18, 2017

@dlebauer I made a note that this was not yet working properly, but I don't remember who reported this or any other details.

@gsrohde gsrohde assigned dlebauer and unassigned gsrohde Jun 2, 2017
@dlebauer
Copy link
Member

dlebauer commented Jun 2, 2017 via email

gsrohde added a commit that referenced this issue Jun 22, 2017
…izard or API) to allow for traits not in the trait_covariate_associations table")

Improved efficiency by taking some one-time computations outside of a loop.
gsrohde added a commit that referenced this issue Jun 22, 2017
…the feature in issue #459 is working.

Also tweaked the test to get it working properly.
@gsrohde gsrohde assigned gsrohde and unassigned dlebauer Jun 22, 2017
@gsrohde gsrohde closed this as completed Jun 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants