Task #6526

Task #6524: Improve CSV import

Change "creatorDates" column header label to creationDates

Added by Dan Gillean over 6 years ago. Updated over 5 years ago.

Status:VerifiedStart date:03/26/2014
Priority:MediumDue date:
Assignee:Mike Cantelon% Done:

0%

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

Description

Often people confuse this with the dates of existence of a creator. There is also another subtask proposal to add dates of existence for a creator (so we don't end up with so many empty authority records), so clarifying this field would help.


Related issues

Related to AtoM Wishlist - Task #6527: Add creator entity type and creator dates of existence co... New 03/26/2014

History

#1 Updated by Dan Gillean over 6 years ago

  • Assignee deleted (Mike Cantelon)

#2 Updated by Mike Cantelon over 5 years ago

  • Status changed from New to QA/Review
  • Assignee set to Dan Gillean

I've done this in branch dev/issue-7764-accession-date-fields (and have renaamed the columns in the example CSV files with the new names).

#3 Updated by Dan Gillean over 5 years ago

Another important factor to note: we are hoping, on #7905, to add some legacy logic so that users who continue to use the old column names will still have imports that succeed. In essence we will add some fallback logic to the import script that will copy values, if present, from the legacy columns to the new columns, for at least the next couple AtoM releases. If "creatorDates" is used, the import will still proceed as expected. If we ever have the opportunity to add a way to import actor dates of existence in the description CSV templates, we will use a non-reserved column name, such as "actorDates," or "actorExistenceDates," or something like this.

This is to ensure that users who have developed custom transformation or migration scripts (including Artefactual, to handle data migrations) will not have to update all existing scripts. We will still correct the problem, without creating issues for users with legacy CSV templates or custom transformation scripts.

#4 Updated by Mike Cantelon over 5 years ago

OK, I've added copying of legacy column values to new columns (if no data found in new columns).

#5 Updated by Dan Gillean over 5 years ago

  • Assignee changed from Dan Gillean to Mike Cantelon
  • Requires documentation set to Yes

Mike, has this been merged yet? if you can point me to a commit so I can confirm exactly what got changed (e.g. did creationDateType get added to the ISAD and RAD CSV templates too? or just to the accession one?), that would be helpful!


Documentation updates that will be required:

#6 Updated by Dan Gillean over 5 years ago

  • Status changed from QA/Review to Verified

#7 Updated by Dan Gillean over 5 years ago

  • Requires documentation deleted (Yes)

updated in 2.2 CSV import docs, and in CSV examples included in 2.2 and on new wiki

Also available in: Atom PDF