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

Enhancement: Exclude hidden fields from CSVs exported by public users #1728

Closed
eferch opened this issue Dec 18, 2023 · 0 comments · Fixed by #1731
Closed

Enhancement: Exclude hidden fields from CSVs exported by public users #1728

eferch opened this issue Dec 18, 2023 · 0 comments · Fixed by #1731
Assignees
Milestone

Comments

@eferch
Copy link

eferch commented Dec 18, 2023

Current behaviour

  • As an administrator: In the visible elements module, uncheck one or more archival description fields to make them hidden from the public.
  • As a public user:
    • Add one or more archival descriptions to the clipboard.
    • Go to the clipboard and export a CSV.
    • The exported CSV includes the field(s) that have been unchecked in the Visible elements module.

Expected behaviour

Exported CSVs should only contain fields that are visible to the user who exported the CSV.

Possible solution

Ideally, exclude hidden fields from the CSV export if the user is not logged in. Another option that would work for us would be to hide the export button entirely for public users.

Context

Hidden fields may contain sensitive information that should not be shared freely with the public (e.g. immediate source of acquisition where the donor prefers to be anonymous). Having this information included in publicly available CSV exports then becomes an information privacy/security risk.

Note that we would still want the full export functionality to be available to staff (authenticated users), just not to the public.

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

Successfully merging a pull request may close this issue.

3 participants