-
Notifications
You must be signed in to change notification settings - Fork 38
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
Duplicate POI management #1037
Comments
Two inputs from my perspective:
@hauf-toni maybe we can just add some are to an existing are in the POI detail field to show sth. like "Diese Ort befinden sich ebenfalls an der Adresse:" So that people see what other locations they already created with this address. This might lead to more awareness. |
i think your proposed solution is reasonable and purposeful. if possible, it would be ideal if users would be suggested a location with the same/similar name directly when entering it, and only in exceptional cases the flow is "create a new location", as this variant is more likely in the medium and long run. |
Motivation
WordPress currently has many duplicate POIs, because it is very easy to enter it again when creating a new event. The GUI does not prevent the user from creating a POI that has the same name. This will result in a unusable list of POIs for the app. We need a different solution in the Django CMS.
Proposed solution
We should prohibit users from creating a POI that is similar (in name and/or location) to an existing one. We need to consider that there could be 2 different locations very close to each other. If a POI exists, the user should be guided to use the existing POI. The user should also be able to explicitly ignore this notification and create a new POI.
We should make use of our new UX & design expert to define a clean process for users.
The text was updated successfully, but these errors were encountered: