How can we get rid of the UUID in the URLS

[wellemut]

Problem

• Our URLs are not human understandable and not nice to share https://kartevonmorgen.org/#/?entry=6f39c3bdac864981a6715538268af235 The number does not help to know, what i find when clicking on it

Solution

• Can we create a slug of up to 50 signs (the whole title) for the entries. Replace all spaces by minus? Like: https://kartevonmorgen.org/#/?entry=SIRPLUS-Rettermarkt
  • If the name is not unique, just add the City to it, like https://kartevonmorgen.org/#/?entry=SIRPLUS-Rettermarkt-Berlin
  • If its still not unique, add the street: https://kartevonmorgen.org/#/?entry=SIRPLUS-Rettermarkt-Berlin-Karl-Marx-Straße
  • If its still not unique within the first 50 letters, add the streetnumber or any other, if it has no street number like https://kartevonmorgen.org/#/?entry=SIRPLUS-Rettermarkt-Berlin-Karl-Marx-Str-30

Would be Much nicer.

Can we solve this in the backend? Can we replace the UUID completly? Do we need an extra ofDB-Colum, that links Slug to ID? Should this be solved in the frontend only?

[uklotzde]

Introduce another pseudo-unique identifier that could change at any time whenever someone modifies an entry??? No, I don't think that this would make sense.

[wellemut]

Ok, so in the ófDB we allways handle things by the ID. Than its just the question, is this slug added additionally?

Wechange also has an ID for each group, but shows a slug in the URL, that you can change whenever you want https://wechange.de/project/klimafit-initiative-emmendingen/

[uklotzde]

We don't have a concept of unique, custom, alternative identifiers. This only works if editing of entries (entirely or only certain properties) would be restricted to their "owners", which is another missing concept.