enable tracing on public datasets of other organizations

[fm3]

Easy fix. However, this creates a new ambiguity: in NML files, the organization is not specified with the dataset name. So far, when uploading NMLs, we picked the dataset of the user. Now, we use the disambiguation route. A better solution would be to persist the organization to NML. Any comments on that thought?

Steps to test:

• enable organization creation, disable autologin
• set one dataset to public
• create new organization via /onboarding
• as the user of that organization, you should see the public dataset + be able to trace
• download and re-upload NML of that tracing

Issues:

• fixes Create annotations for public datasets of other orgs doesn't work #3529

---

• Updated changelog
• [ ] Updated migration guide if applicable
• [ ] Updated documentation if applicable
• [ ] Needs datastore update after deployment
• Ready for review

[youri-k]

Looks good except for the edge case where there are two datasets with the same name and the public dataset is newer and someone from the other org tries to upload a tracing to this dataset, but I don't see a way to work around this.

[fm3]

created follow-up issue #3536 to track that

[normanrz]

@fm3 could we cherry-pick this to demo instance?

[fm3]

@normanrz sure. should we just install the resulting branch on demo or create a 18.11.1 release? Or just roll demo to the corresponding master build from yesterday?

[normanrz]

Let's roll to master on monday.