Bug #8993

CSV export: --public option does not exclude physical storage information, even if hidden via visible elements

Added by Dan Gillean almost 5 years ago. Updated almost 3 years ago.

Status:VerifiedStart date:09/23/2015
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:CSV export
Target version:Release 2.4.0
Google Code Legacy ID: Tested version:2.3
Sponsored:No Requires documentation:

Description

In our EAD export code (and used as a possible setting for finding aid generation), we have a "public" option - when used, this will exclude draft descriptions from an export, AND, if the physical storage information associated with published records is hidden from public users via the Visible elements module, the storage information will also be excluded. This was added because the disclosure of physical location infomation can be considered a security risk by some archives; users should have the choice as to whether or not this information is publicly available.

The CSV export task seems to have a similar option - from the help text for the task:
  • --public: Do not export draft physical locations or child descriptions

However, physical storage information is not excluded from published records when exporting using the --public option, even if the location is hidden via Visible elements

To reproduce
  • Create a fonds with child descriptions
  • Add physical storage information to those children
  • Make sure all the records with physical storage information (and their parent records) are published
  • Hide phyiscal storage information via Admin > Visible elements
  • From the CLI, run the csv export task, using the --public option

Error encountered
physicalObjectName, physicalObjectLocation, and physicalObjectType are all still expored

Expected result
  • Task excludes physical storage information when using --public option, and physical storage is hidden via Visible elements

EITHER THIS (ideal), or at the very least, we should remove mention of physical storage from the task help, as it is misleading


Related issues

Related to Access to Memory (AtoM) - Bug #8992: CSV export: --single-slug option should export child records Verified 09/23/2015
Related to Access to Memory (AtoM) - Bug #11453: Exports by unathenticated users should always use --publi... Feedback 08/24/2017

History

#1 Updated by Dan Gillean almost 5 years ago

  • Related to Bug #8992: CSV export: --single-slug option should export child records added

#2 Updated by Mike Gale almost 3 years ago

  • Status changed from New to Code Review
  • Assignee changed from Mike Gale to Mike Cantelon

#3 Updated by Mike Cantelon almost 3 years ago

  • Status changed from Code Review to Feedback
  • Assignee changed from Mike Cantelon to Mike Gale

Seems good!

#4 Updated by Mike Gale almost 3 years ago

  • Status changed from Feedback to QA/Review
  • Assignee changed from Mike Gale to Dan Gillean

merged qa/2.4.x 4ad2b97

#5 Updated by Dan Gillean almost 3 years ago

  • Target version set to Release 2.4.0

#6 Updated by Dan Gillean almost 3 years ago

  • Related to Bug #11453: Exports by unathenticated users should always use --public option added

#7 Updated by Dan Gillean almost 3 years ago

  • Status changed from QA/Review to Verified

Looks good! Note that this only fixes CSV export from the CLI. see related issue #11453 for other issues when public users export via the UI.

Also available in: Atom PDF