Bug #8387

Change csv:export behavior to not just append to existing files

Added by Mike Gale about 4 years ago. Updated about 1 month ago.

Status:VerifiedStart date:05/04/2015
Priority:LowDue date:
Assignee:-% Done:

0%

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

Description

Currently, if the user does csv:export multiple times, AtoM will just keep appending the same records to the same CSV file. This is somewhat unexpected behavior, one would expect a new file to be created with each csv:export I think.

We should probably change the fopen() mode from 'a' to 'w'. I think some minor refactoring around deciding when to write CSV headers might need changing too. Hopefully it isn't too bad.

History

#1 Updated by Mike Cantelon 10 months ago

  • Status changed from New to Code Review
  • Assignee changed from Mike Cantelon to Nick Wilkinson

#2 Updated by Nick Wilkinson 10 months ago

  • Assignee changed from Nick Wilkinson to Steve Breker

Hi Steve, passing to you for CR.

#3 Updated by Steve Breker 10 months ago

  • Status changed from Code Review to Feedback
  • Assignee changed from Steve Breker to Mike Cantelon

CR complete. Looks good!

#4 Updated by Mike Cantelon 10 months ago

  • Status changed from Feedback to QA/Review
  • Assignee changed from Mike Cantelon to Dan Gillean
  • Target version set to Release 2.5.0

Merged into qa/2.5.x for QA. Can backport if it passes.

#5 Updated by Michelle Curran 9 months ago

  • Status changed from QA/Review to Verified
  • Assignee changed from Dan Gillean to Mike Cantelon

Verified - works as expected when I export completed jobs in CSV format, export search and browse results, and export clipboard results

#6 Updated by Mike Cantelon about 1 month ago

  • Assignee deleted (Mike Cantelon)

Also available in: Atom PDF