Feature #13183

Add CSV import for physical locations

Added by David Juhasz about 1 year ago. Updated 7 months ago.

Status:VerifiedStart date:09/25/2019
Priority:MediumDue date:09/25/2019
Assignee:-% Done:

100%

Category:CSV import
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

This feature will add a new command-line import task for physical storage data. At this time, work to add support via the user interface has not been included in this development.

The new CSV template will contain the following columns:

  • legacyId
  • name
  • type
  • location
  • culture
  • descriptionSlugs

descriptonSlugs will be used to link the new physical storage containers to existing descriptions, using the slug of the target description(s). It will be a multi-value field, meaning users will be able to add multiple pipe-separated values.

Error handling:

If a user imports a CSV and no matching description slug is found, AtoM will:

  • Create the container but not link it to any description
  • Report in the console that the slug could not be found

Users encountering this issue could correct the CSV and then re-import it as an update to add the link the target description, using the update functionality described in issue #13185.

Development tasks

  • Create CLI import task
  • Add basic physical storage columns
  • Add ability to link containers to existing descriptions on import
  • Add template to lib/task/import/example
  • QA testing

Related issues

Related to Access to Memory (AtoM) - Bug #13201: Browse Physical storage page does not show values that ha... Verified 10/10/2019
Precedes Access to Memory (AtoM) - Feature #13185: Update physical storage data via CSV import Verified 09/26/2019 09/26/2019

History

#2 Updated by David Juhasz about 1 year ago

  • Follows Feature #13185: Update physical storage data via CSV import added

#3 Updated by David Juhasz about 1 year ago

  • Follows deleted (Feature #13185: Update physical storage data via CSV import)

#4 Updated by David Juhasz about 1 year ago

  • Precedes Feature #13185: Update physical storage data via CSV import added

#5 Updated by David Juhasz about 1 year ago

  • Precedes deleted (Feature #13185: Update physical storage data via CSV import)

#6 Updated by David Juhasz about 1 year ago

  • Precedes Feature #13185: Update physical storage data via CSV import added

#7 Updated by Dan Gillean about 1 year ago

  • Description updated (diff)

#9 Updated by David Juhasz 12 months ago

  • Related to Bug #13201: Browse Physical storage page does not show values that have not been translated added

#10 Updated by David Juhasz 12 months ago

  • Status changed from New to Code Review
  • Assignee deleted (David Juhasz)

Ready for code review: https://github.com/artefactual/atom/pull/983

Dev branch: dev/issue-13183-physical-object-csv-import

#11 Updated by David Juhasz 12 months ago

  • Description updated (diff)

Updated CSV column names

#12 Updated by David Juhasz 12 months ago

  • Status changed from Code Review to QA/Review
  • Assignee set to Corinne Rogers

Merged to qa/2.6.x and ready for testing

Note: requires installing PHP composer: and running composer install to get dependencies.

#13 Updated by David Juhasz 12 months ago

  • Status changed from QA/Review to Feedback
  • Assignee changed from Corinne Rogers to David Juhasz

This is causing an application-wide critical error in AtoM when the vendor/composer/autoload.php file doesn't exist. :(

#14 Updated by David Juhasz 12 months ago

  • Status changed from Feedback to QA/Review
  • Assignee changed from David Juhasz to Corinne Rogers

I created PR992 to fix the autoloader error, and merged it to qa/2.6.x after review.

#15 Updated by David Juhasz 12 months ago

  • Status changed from QA/Review to Document
  • Assignee deleted (Corinne Rogers)

Ready for documenting

#16 Updated by David Juhasz 12 months ago

  • % Done changed from 0 to 100

#17 Updated by David Juhasz 12 months ago

  • % Done changed from 100 to 90

#18 Updated by Dan Gillean 7 months ago

  • Status changed from Document to Verified
  • % Done changed from 90 to 100
  • Requires documentation deleted (Yes)

Also available in: Atom PDF