Prevent duplicate repository linkage in lower level descriptions on import
|Assignee:||Sarah Romkey||% Done:|
|Target version:||Release 2.2.0|
|Google Code Legacy ID:||Tested version:||2.0.1, 2.1, 2.1.1|
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.
#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"