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

Duplicate POI management #1037

Open
Tracked by #1039 ...
svenseeberg opened this issue Nov 24, 2021 · 2 comments
Open
Tracked by #1039 ...

Duplicate POI management #1037

svenseeberg opened this issue Nov 24, 2021 · 2 comments
Labels
effort: medium Should be doable in <12h feature New feature or request prio: medium Should be scheduled in the forseeable future.

Comments

@svenseeberg
Copy link
Member

svenseeberg commented Nov 24, 2021

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.

@svenseeberg svenseeberg added the feature New feature or request label Nov 24, 2021
@svenseeberg svenseeberg added this to the Version 1.2 milestone Nov 24, 2021
@svenseeberg svenseeberg added the prio: medium Should be scheduled in the forseeable future. label Nov 24, 2021
@svenseeberg svenseeberg mentioned this issue Nov 24, 2021
7 tasks
@svenseeberg svenseeberg modified the milestones: Version 1.2, Version 1.3 Apr 27, 2022
@ulliholtgrave ulliholtgrave added the effort: medium Should be doable in <12h label May 16, 2022
@timobrembeck timobrembeck modified the milestones: 22Q3, 23Q1 Oct 2, 2022
@ulliholtgrave ulliholtgrave added prio: low Not urgent, can be resolved in the distant future. and removed prio: medium Should be scheduled in the forseeable future. labels Feb 17, 2023
@ulliholtgrave ulliholtgrave modified the milestones: 23Q1, 23Q2 Feb 17, 2023
@timobrembeck timobrembeck modified the milestones: 23Q2, 23Q3 Jul 2, 2023
@ulliholtgrave ulliholtgrave modified the milestones: 23Q3, 23Q4 Jul 17, 2023
@dkehne
Copy link

dkehne commented Sep 11, 2023

Two inputs from my perspective:

  • Show a warning when a poi with the same name already exists. Maybe it is also forbidden to create it or it causes and error. maybe remove the special characters and capital letters before comparing so that "Jobcenter Augsburg" is also "Job-Center Augsburg"

@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.

@dkehne dkehne modified the milestones: 23Q4, 24Q1 Sep 11, 2023
@hauf-toni
Copy link

  • Show a warning when a poi with the same name already exists. Maybe it is also forbidden to create it or it causes and error. maybe remove the special characters and capital letters before comparing so that "Jobcenter Augsburg" is also "Job-Center Augsburg"

@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.

@dkehne dkehne modified the milestones: 24Q1, 24Q4 Dec 13, 2023
@MizukiTemma MizukiTemma mentioned this issue Feb 15, 2024
24 tasks
@JoeyStk JoeyStk mentioned this issue Oct 4, 2024
20 tasks
@JoeyStk JoeyStk modified the milestones: 24Q4, 25Q1 Oct 8, 2024
@JoeyStk JoeyStk added prio: medium Should be scheduled in the forseeable future. and removed prio: low Not urgent, can be resolved in the distant future. labels Oct 8, 2024
@JoeyStk JoeyStk removed this from the Roadmap T37K milestone Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: medium Should be doable in <12h feature New feature or request prio: medium Should be scheduled in the forseeable future.
Projects
None yet
Development

No branches or pull requests

6 participants