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.

Sign up for GitHub

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

Jump to bottom

Some tissue blocks have no sex assigned to them from donor, default to female despite being registered into male organ #15

Open

andreasbueckle opened this issue Sep 28, 2022 · 0 comments

Collaborator

andreasbueckle commented Sep 28, 2022

@bherr2 Capturing this based on our f2f convo:

For example, tissue block http://entity.api.hubmapconsortium.org/entities/HBM964.XZCR.478 derives from donor: https://portal.hubmapconsortium.org/browse/sample/0a558711c6b9d5b9029717d722a2c31c#provenance

Donor https://portal.hubmapconsortium.org/browse/donor/1e0b527a436936050455fe755dfbaba2 is male.

target in rui_location for http://entity.api.hubmapconsortium.org/entities/HBM964.XZCR.478 is correctly"target": ["http://purl.org/ccf/latest/ccf.owl#VHMLeftKidney"](http://purl.org/ccf/latest/ccf.owl#VHMLeftKidney)

However, https://entity.api.hubmapconsortium.org/entities/HBM735.QDFT.264 has a field "living_donor_data" that we do not account for in our code, so the sex of the tissue block defaults to female.

The text was updated successfully, but these errors were encountered:

bherr2 transferred this issue from hubmapconsortium/ccf-ui

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment