Feature #10006

Bulk export: add support for excluding draft records on archival description exports

Added by Dan Gillean about 4 years ago. Updated almost 3 years ago.

Status:VerifiedStart date:06/13/2016
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:Import/ExportEstimated time:4.00 hours
Target version:Release 2.4.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

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.

History

#2 Updated by Dan Gillean almost 4 years ago

  • Target version changed from Release 2.4.0 to Release 2.5.0

#3 Updated by Steve Breker over 3 years ago

  • Status changed from New to Code Review
  • Assignee set to Nick Wilkinson

#4 Updated by Dan Gillean over 3 years ago

  • Target version changed from Release 2.5.0 to Release 2.4.0

#5 Updated by Nick Wilkinson over 3 years ago

  • Status changed from Code Review to QA/Review
  • Assignee deleted (Nick Wilkinson)

This was CR'd on the private ticket.

#6 Updated by Sara Allain about 3 years ago

  • Assignee set to Sara Allain

#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 2.4.0.1 version.

#8 Updated by Sara Allain about 3 years ago

  • Assignee changed from Steve Breker to Nick Wilkinson

#9 Updated by Nick Wilkinson about 3 years ago

  • Assignee changed from Nick Wilkinson to Steve Breker

#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:

https://github.com/artefactual/atom/pull/573

#11 Updated by Steve Breker about 3 years ago

  • Status changed from Feedback to Code Review

#12 Updated by Nick Wilkinson about 3 years ago

  • Assignee changed from Nick Wilkinson to Mike Gale

Hi Mike, assigning to you for CR.

#13 Updated by Mike Gale about 3 years ago

  • Assignee changed from Mike Gale to Steve Breker

I just did that CR, what a coincidence. :)

lgtm

#14 Updated by Steve Breker about 3 years ago

  • Status changed from Code Review to QA/Review
  • Assignee changed from Steve Breker to Nick Wilkinson

I have merged PR 573 to qa/2.4.x.

This is ready for testing - 'include draft' should be working now!

#15 Updated by Nick Wilkinson about 3 years ago

  • Assignee changed from Nick Wilkinson to Dan Gillean

#16 Updated by Dan Gillean almost 3 years ago

  • Status changed from QA/Review to Verified

#17 Updated by Dan Gillean almost 3 years ago

  • Requires documentation deleted (Yes)

Also available in: Atom PDF