Make organization name its id, drop the mongo id

[fm3]

The old organizationId (which was a mongoId/ObjectId) is dropped. The old organizationName is renamed to organizationId. The old organizationDisplayName is renamed to organizationName.

URL of deployed dev instance (used for testing):

• https://organizationidvsname.webknossos.xyz

Steps to test:

• Test annotating, annotation download+reupload, signup, login
• Test task system
• Test libs access
• Test migrations

TODOs:

• update in sql schema
• update in scala code
• the mongoid is used as key in loki?
• update in routes
• update in proto
• update in frontend
• checks on name in sql and create organization code (allow [A-Za-z0-9\-_. ]+ in sql)
• test around
• sql migration, careful with foreign keys
  • to make rollback easier, keep old ids, rename to nullable unused column?
  • migrate analytics events json in postgres
    • for foreign-webknossos analytics events it may be that the id cannot be looked up. talk to norman on how to handle these.
• make sure that analytics events those from old webknossoses can still be ingested
• make sure that analytics events those from new webknossoses can still be ingested
• bump api version, provide adapters → only for routes used by python client. e.g. dataset_list
• todos in code
• change worker job arguments from organization_name to organization_id: Follow-up Rename organization_name to organization_id in worker args #8038
• adapt vx runs moving script in notion, make it more robust -> can be done later
• What do to with OrganizationCreationParameters which has the organizationDisplayName prop? -> renaming to organizationName? -> its fine, just do it
• check whether frontend events eventProperties need to be migrated
• Mention in reversion that the newly created orgas first need a manual valid _id_old entry for the reversion to work.
• The update route for organizations was changed. (The param displayName was renamed to name). Should a versioned API route be created for this? No need, that route is only used by our frontend.
• Test wk thoroughly

Issues:

• fixes Make the organization name its id, drop the mongo id #7689

• follow-up: Clean up old organization id residuals #8039

• follow-up: Rename organization_name to organization_id in worker args #8038

• follow-up (libs): Use webknossos API v8 (organization_id) webknossos-libs#1178

---

• Updated changelog
• Updated migration guide if applicable
• Adapted wk-libs python client if relevant API parts change → Follow-up: Use webknossos API v8 (organization_id) webknossos-libs#1178
• Removed dev-only changes like prints and application.conf edits
• Considered common edge cases
• Needs datastore update after deployment

[fm3]

@MichaelBuessemeyer is this TODO still open?

[MichaelBuessemeyer]

nope, should be resolved

[fm3]

LGTM :)

Two questions:

• There is an open TODO comment in schema.sql, I think it is actually resolved. Can you double-check that?
• I think I remember you talking with Norman about the idea of a full backup of the analyticsEvents table. That seems to not be included in the evolution. Does that plan still stand? If so, do we want to do this manually or do we want to add it to the evolution?

I fixed a couple of small things in my last commits.

I can’t hit approve since I was the original author. Do you want to do so?

[MichaelBuessemeyer]

LGTM checked newest changes together with @fm3