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

Associate user's with the "Terms agreements/Privacy Notes" signed and stamp the date #10471

Open
marcbria opened this issue Sep 26, 2024 · 0 comments

Comments

@marcbria
Copy link
Collaborator

marcbria commented Sep 26, 2024

Describe the issue

"Terms of Service” and “Privacy Notes” change on time because they depend on regulations and organization politics.

As an example, let's say that a user accepts a specific "Privacy Note", but GDPR changes and now requires something new (ie: "explicit consent").
How do we know what users signed the old "Privacy Note" and who singed the new one? How do we know the literal text of the old "Privacy Note" or the "ToS" they accepted?

Of course, the editorial service can keep a copy of all this and if remembers the date, can make a query to the DB to extract the affected users, but a more practical/easier solution for Editors would be:

  • Versioning: Keep an archive/log of all the changes made in the Privacy Note / Term agreement.
  • Associate: Refer ToS/PN signed by each user.
  • Stamp: Add an “Stamp” to the tuple to clarify when it was signed.

With this information, OxS will be able to export lists of users "that need to be contacted to explain the ToS" or re-invited or deleted from the user's database, etc. In the future, OxS could be also able to help in managing the user's ToS directly (without an exportation and performing actions outside the system).

What application are you using?
It will be useful in OJS, OMP or OPS.

Additional information
CRAFT project will write a document listing possible scenarios that could require the Editors to interact with the user's list.
This document could help to decide how relevant is this Feature Request and what extra tooling need to be developed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant