[2024-11-07] Remove E-mail, phone number and website from POI

[MizukiTemma]

Motivation

Currently POI has three fields for contact information: E-mail, phone number and website. We came to an idea, however, while discussing and implementing contact management system, that those fields/information must be managed in contacts in futur.

Proposed Solution

• Remove those three fields from POI
• Adjust ajax POI form poi_box.html (remove Contact details, etc)
• Create a migration to create contacts from those poi fields and remove the fields from poi
• Adjust the api so that it returns the same results (Contacts without title and name could be treated as primary contact, and returned instead of the now removed data)

Alternatives

User Story

Additional Context

Design Requirements

[MizukiTemma]

As "primary contact" meant is contact objects without "point_of_contact_for". There is a constraint that for each POI max. one primary contact exists (already implemented).

For this issue I have imagined following work steps:

1. For each POI which has at least one of E-mail, phone number and website, create a contact object with them ("point_of_contact_for" and "name" stay empty).
2. Remove E-mail, phone number and website fields from POI model.
3. Remove the box of those three fields from the POI form.
4. Adjust API so it finds the primary contact of the requested POI and reads those fields from the primary contact.

[osmers]

Just one question before this gets closed - didn't we say that this cannot be removed before we have not migrated the information stored there to a general contact?

[david-venhoff]

Yes, this will be part of this issue:

• Create a migration to create contacts from those poi fields and remove the fields from poi

Though it looks like it is currently missing from the pr