-
Notifications
You must be signed in to change notification settings - Fork 18
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
Adding app_context from SenNet #1299
Conversation
…ove it outside of live code
…es are returned, will be separate PR
@gesinaphillips - so the hard-coding is setting the ingest-api value when the validate_tsv function is used outside of the context of an upload? I think this will cause issues in SenNet (not sure) because I believe that they do exactly that. They call that function without constructing an upload, when someone uploads a metadata.tsv file. So I think we would have to hard-code that value in the SenNet IVT. Everything else looks fine! |
@jpuerto-psc But either way, if we have the HuBMAP URLs hard-coded in |
@jpuerto-psc, Updated: Not a major issue with the update on SenNet since the fork will allow the hardcoded url to be updated, we just need to inform about this. |
Fantastic, then we're good here I think! |
This deviates from the SenNet in a few necessary and one maybe-tryhard way.
validation_utils
.Note the TODO in upload.py regarding the hardcoded defaults.
What do you think?