search

culturecreates / artsdata-shortcode

Wordpress plugin for Artsdata
0 stars 1 forks source link

Remove members that "do not agree" to terms_conditions #23

Open saumier opened 1 year ago

saumier commented 1 year ago

Currently the terms_conditions is not being loaded since version 1.1 came out. members that "do not agree" to terms_conditions should not be loaded into Artsdata and not appear in the member directory.

Email from Frédéric 14-Jun-2023

Hi Gregory,

Could you please confirm that the field "terms_conditions_v1_0" is also used to determine which records are loaded to Artsdata? This is our consent question. Any member who does not agree should not be loaded to Artsdata.

I scanned the pilot project doc about this and I couldn't find anything indicating clearly that this field was taken into account prior to loading the data.

Frédéric
saumier commented 1 year ago

Data currently available from Wordpress API

empty agree (v1.1) agree (v1.0) agree and disclose (v1.1) do not agree (v1.1) agree and disclose (v1.0) do not agree (v1.0)

saumier commented 1 year ago

Of the above members, there are 3 with "do not agree (v1.0)" and 1 with "do not agree (v1.1)"

fjjulien commented 1 year ago

After discussing this issue with the team, we all agreed that consent should be required for member data to be loaded to Artsdata and displayed in the directory. No consent = no listing in the directory.

On the CAPACOA side of things, we have a lot of work to make this requirement clear across all our membership forms and resources. In addition, we have several members who have simply been paying their membership invoice without even bothering to log into their account. The good news is: the consent requirement will be a good incentive.

@saumier Could you give me the names of the members who haven't given consent?

saumier commented 1 year ago

@fjjulien Here is the SPARQL to get the consent status of all members.

There are many with "empty", and there are 4 with "do not agree".

You can search the results for "do not agree".

https://s.zazuko.com/NMkm7K

fjjulien commented 1 year ago

@dugost We revised the Membership Open Data Strategy to include this clarification. Could you please update the "No thanks" value to reflect the wording in the revised strategy?

Note: I don't think we need to create another version of the strategy. This change does not affect members who had given their consent. A new version number should only be created when a change invalidates consent provided under a previous version (which is absolutely not the case here).

fjjulien commented 1 year ago

We also need a system to remove terminated members from the directory. I'll open another issue about this.

dugost commented 1 year ago

@fjjulien Staging checkout has updated EN/FR wording for "No thanks". Will reflect this on production site.

fjjulien commented 1 year ago

Currently the terms_conditions is not being loaded since version 1.1 came out.

I believe this was fixed in version 2.0 of capacoa-artsdata-usermeta. I see the field in the list of extracted fields.

fjjulien commented 1 year ago

members that "do not agree" to terms_conditions should not be loaded into Artsdata and not appear in the member directory.

@saumier Logically and Ethically, that is how we should proceed. However, if this presents any technical challenges, I am not adamant that we should proceed in this fashion. Here's why:

All in all, it's probably not worth it setting up an exclusion mechanism at the ETL level if it presents any complexity. If it's easy to code, proceed. If it is going to take more than 15-20 mins, leave it.

This being said, if we do not create an exclusion mechanism at the ETL level, we should still create one at the display level.

I will let you assess with of the two exclusion mechanisms is easiest to code.

fjjulien commented 1 year ago

For priority setting purposes, this issue is not in direct scope for the current iteration. #18 and #25 are higher priority.