Bulk export: add support for excluding draft records on archival description exports
|Assignee:||Dan Gillean||% Done:|
|Category:||Import/Export||Estimated time:||4.00 hours|
|Target version:||Release 2.4.0|
|Google Code Legacy ID:||Tested version:|
This feature will build upon the work outlined in issue #9998.
This feature will behave similarly to the --public option on the commmand-line bulk export task. When selected, any draft records will be excluded from the export selections. Similarly, like the existing CLI public option, if physical storage locations are hidden via Visible elements, they will be excluded during the export as well.
#7 Updated by Sara Allain about 3 years ago
- Status changed from QA/Review to Feedback
- Assignee changed from Sara Allain to Steve Breker
Tested on 2.4 VM.
Selecting Include draft records does not include drafts. Drafts are never exported.
Including/excluding drafts does work on http://atomqa24x.accesstomemory.org, which was set up several weeks ago; the VM is the 126.96.36.199 version.
#10 Updated by Steve Breker about 3 years ago
- Assignee changed from Steve Breker to Nick Wilkinson
ACL checks for determining if a user should be able to export drafts was broken by the change to allow background jobs launched by unauthenticated users - user context was no longer set for authenticated users and so ACL checks were failing, preventing the export of drafts.
I have a fix for this ready for CR:
#17 Updated by Dan Gillean almost 3 years ago
- Requires documentation deleted (
Documentation added to 2.4 in the following commit: