Task #7929

Prevent duplicate repository linkage in lower level descriptions on import

Added by Mike Gale over 7 years ago. Updated about 7 years ago.

Status:VerifiedStart date:02/04/2015
Priority:LowDue date:
Assignee:Sarah Romkey% Done:

0%

Category:CSV import
Target version:Release 2.2.0
Google Code Legacy ID: Tested version:2.0.1, 2.1, 2.1.1
Sponsored:No Requires documentation:

Description

Currently, if a user has the same repository filled in in a CSV for all records (and levels of description), AtoM will happily link the repository to all records individually. Ideally, we'd just set the repository at the highest levels of description, and lower levels should inherit the repository that way (this improves performance).

Task: when importing a row/record, check if the highest level of description ancestor has the same repository set. If so, do not set the repository for the current row being imported. If the repository is different between the highest level ancestor and the current row, do the usual behavior.

History

#2 Updated by Mike Gale about 7 years ago

  • Status changed from New to Code Review
  • Assignee changed from Mike Gale to José Raddaoui Marín

#3 Updated by José Raddaoui Marín about 7 years ago

  • Status changed from Code Review to Feedback
  • Assignee changed from José Raddaoui Marín to Mike Gale

#4 Updated by Mike Gale about 7 years ago

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

#5 Updated by Dan Gillean about 7 years ago

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

Failed when the repository did not already exist in AtoM. Error message when CSV import fails: "Must pass a non-null repository id to canInheritRepository"

#6 Updated by José Raddaoui Marín about 7 years ago

The same happens trying to create an information object without repository. Maybe we should return false here instead of throwing an exception.

#7 Updated by Mike Gale about 7 years ago

José Raddaoui Marín wrote:

The same happens trying to create an information object without repository. Maybe we should return false here instead of throwing an exception.

Good idea Radda, I feel the same way.

#8 Updated by Mike Gale about 7 years ago

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

Hopefully that fixed it :)

#9 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Verified

#10 Updated by Mike Gale about 7 years ago

  • Status changed from Verified to QA/Review
  • Assignee changed from Dan Gillean to Sarah Romkey

Fixed & deployed to SFU's site (http://atom.archives.sfu.ca/)

#11 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF