Address Data Data model documentation

Back to the feature description

This is where the data is created when the website is used. It is private or professional address data. Consent to publication was given online, so that it should be possible to request a data extract or deletion online - without deleting linked non-personal transaction data (e.g. for event participation). The data will not be published on the website, at most for the purpose of modification after login by the data subject. Otherwise, when entering new data, older data will be overwritten with newer data, provided that the e-mail address remains the same. A new e-mail address leads to a new data record. Data records are stored centrally in the tree under "Website-visitors" and are listed alphanumerically under the e-mail address.

Application scenarios:
Event participation, newsletter subscription, petition, mail campaign, vote, donation, membership application

Data model:
Legend: *mandatory field | [is filled in by the system] | unused fields of the standard data model | (FIELDTYPE Hint)

These are personal address data that typically arise in a professional context. The data is to be published on the website. Consent is required for both processing and publication, which can take place online but is typically done by other means. Changes can be made by editors or after login by the person concerned. If a person concerned wants to become active on the website in other ways, s*he generates an additional website visitor data record. Via a FE-user access s*he can then edit both address data sets online. Data records are stored in a central location in the tree under "Person page data" and are listed alphabetically under surname, first name. They are stored with a URL segment generated from first-name-last name.

Usage scenarios:
NGO employees, (natural) association members, expert database, speaker database, elected officials

Data model:
Legend: *mandatory field | [is filled in by the system] | unused fields of the standard data model | (FIELDTYPE Hint)

This is typically not personal data. If persons are named, then as contact persons, who are often already publicly known. The data is to be published on the website. If contact partners are published, then typically in a protected area. Consent is required for processing as well as publication, which can take place online, but typically takes place by other means. Consent to processing is given if a business relationship exists. Changes can be made by editors or after login by the affected institution. If the institution uses the e-mail address of a person and this person becomes active on the website in another way, s*he generates an additional website visitor a data record. The person is unlikely to be active as a personal page record as well. Records are stored in a central location under "Institutions" and listed alphanumerically under the name, branch and type of the organisation. This name is also used to generate the URL component of the dataset.

Usage scenarios:
(legal) association members, branch offices, local groups, event locations

Data model:
Legend: *mandatory field | [is filled in by the system] | unused fields of the standard data model | (FIELDTYPE Hint)