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

Added by Peter Van Garderen 6 months ago. Updated 4 months ago.

Status:VerifiedStart date:05/20/2020
Priority:MediumDue 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

Bug #13329: Problem: remove the unused legacyId column from relations...VerifiedPeter Van Garderen

History

#1 Updated by Peter Van Garderen 6 months ago

  • Sponsored changed from No to Yes

#2 Updated by Peter Van Garderen 6 months ago

  • Parent task changed from #13286 to #13279

#3 Updated by Mike Cantelon 6 months 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 6 months 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 5 months 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

Also available in: Atom PDF