You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: