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

Configure whether personal data stored in Provenance #2889

Closed
heathergreerklein opened this issue Jul 17, 2020 · 5 comments · Fixed by #9442
Closed

Configure whether personal data stored in Provenance #2889

heathergreerklein opened this issue Jul 17, 2020 · 5 comments · Fixed by #9442
Assignees
Labels
interface: REST API v7+ REST API for v7 and later (dspace-server-webapp module) privacy Issues relating to improving user privacy options

Comments

@heathergreerklein
Copy link

From release plan spreadsheet
Estimate from release plan: TBD
Expressing interest: none

DSpace should include a configuration that disables storing personal information (email, netid, name) in the dc.description.provenance field. Currently, this info is automatically stored when items are submitted or reviewed.

@heathergreerklein heathergreerklein added interface: REST API v7+ REST API for v7 and later (dspace-server-webapp module) low priority Estimate TBD Needs to have an estimate added labels Jul 17, 2020
@heathergreerklein heathergreerklein added this to the 7.2 milestone Jul 17, 2020
@tdonohue tdonohue added the privacy Issues relating to improving user privacy options label Aug 3, 2021
@tdonohue tdonohue removed this from the 7.2 milestone Oct 29, 2021
@damian-joz
Copy link
Contributor

@tdonohue
As PCG Academia we would like to contribute to this task. @AndrewAlesik can start an implementation right away.

@tdonohue
Copy link
Member

@damian-joz : Thanks! Please be aware that this may be unlikely to make it into 8.0 at this point, since we are only accepting bug fixes / small improvements. Nonetheless, you are welcome to begin working on this, and when it is ready submit a PR (which likely would be scheduled for 9.0).

Assigning you to this ticket, but delegate the actual work to whomever you want.

@tdonohue tdonohue removed the Estimate TBD Needs to have an estimate added label Mar 29, 2024
@damian-joz damian-joz removed their assignment Mar 29, 2024
@damian-joz
Copy link
Contributor

Thanks @tdonohue . I can't reassign to anyone else so please assign @AndrewAlesik to the issue.

@tdonohue
Copy link
Member

@damian-joz : To be clear, the person who develops on this task does not need to be assigned to the ticket. The ticket just needs to be assigned to someone on your team so that I know who to contact if there are questions.

I cannot assign @AndrewAlesik either as GitHub is blocking my ability to assign him until he either adds a comment to this ticket or is added as a full developer to the DSpace project in GitHub.

With other service providers, I just make sure that someone at the service provider is assigned. It doesn't matter who actually does the work or creates the PR. Just make sure the PR links back to this ticket.

@damian-joz
Copy link
Contributor

Hi @tdonohue

We've prepared the PR: #9442
I think it could still be a part of DSpace 8.0 if we could find a reviewer quickly as it is a small PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interface: REST API v7+ REST API for v7 and later (dspace-server-webapp module) privacy Issues relating to improving user privacy options
Projects
Status: ✅ Done
3 participants