Bug #13306
Feature #13279: Add relationship type to authority record relations CSV import and export
Problem: the relations.csv file produced by csv:authority-export contains the wrong column headers
Status: | Verified | Start date: | 05/20/2020 | |
---|---|---|---|---|
Priority: | Medium | Due date: | ||
Assignee: | Peter Van Garderen | % Done: | 100% | |
Category: | CSV export | |||
Target version: | Release 2.6.0 | |||
Google Code Legacy ID: | Tested version: | |||
Sponsored: | Yes | Requires documentation: |
Description
It uses "sourceAuthorizedFormOfName" and "targetAuthorizedFormOfName" whereas ""objectAuthorizedFormOfName" and "subjectAuthorizedFormOfName" are expected
Subtasks
History
#1 Updated by Peter Van Garderen about 2 years ago
- Sponsored changed from No to Yes
#2 Updated by Peter Van Garderen about 2 years ago
- Parent task changed from #13286 to #13279
#3 Updated by Mike Cantelon about 2 years ago
- Status changed from New to Code Review
- Assignee deleted (
Mike Cantelon)
Currently under CR (as part of PR for #13305).
#4 Updated by Mike Cantelon about 2 years ago
- Status changed from Code Review to QA/Review
- Assignee set to Peter Van Garderen
Fix merged into qa/2.6.x.
#5 Updated by Peter Van Garderen almost 2 years ago
- Status changed from QA/Review to Verified
The right column headers for "objectAuthorizedFormOfName" and "subjectAuthorizedFormOfName" are now used so this is fixed. However, the column "legacyid" was removed which creates a roundtripping error when this relations.csv is imported back into an AtoM instance. See https://projects.artefactual.com/issues/13329