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

Tracing proto organizationName field – dataset vs user orga #6522

Closed
fm3 opened this issue Sep 30, 2022 · 1 comment · Fixed by #6548
Closed

Tracing proto organizationName field – dataset vs user orga #6522

fm3 opened this issue Sep 30, 2022 · 1 comment · Fixed by #6548
Assignees

Comments

@fm3
Copy link
Member

fm3 commented Sep 30, 2022

Looks like createExplorational sets the organizationName field using the user orga, not the dataset orga, as it is described in the comment in the proto files. This creates problems like #6521 – we should consider how to deal with this disparity

@fm3
Copy link
Member Author

fm3 commented Oct 2, 2022

annotations for datasets of foreign orgas can be found via

select a._id, uo.displayname as userOrg, dao.displayname as datasetOrg
from webknossos.annotations_ a
join webknossos.datasets_ d on a._dataset = d._id
join webknossos.users_ u on a._user = u._id
join webknossos.organizations_ uo on u._organization = uo._id
join webknossos.organizations_ dao on d._organization = dao._id
where u._organization != d._organization

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