[Archivesspace_Users_Group] FileMakePro to ArchivesSpace migration
Chris.Fitzpatrick at lyrasis.org
Fri Jan 9 04:08:27 EST 2015
Hm, well the problem is you can't have line breaks in a CSV file, because that would make a new row in the CSV.
The fix would probably be to convert the FMPro line breaks into something like a vertical line bar then customize the CSV importer to convert vertical bars into line breaks.
Does that make sense?
Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat | Phone: 918.236.6048
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Peter MacDonald <pmacdona at hamilton.edu>
Sent: Thursday, January 8, 2015 5:46 PM
To: Archivesspace_Users_Group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] FileMakePro to ArchivesSpace migration
I have managed to design a procedure to import FMPro date into AS through CSV import.
But I'm not sure how to handle carriage returns within fields in the FMPro data.
Do I need to remove them all before importing? If I don't remove them, they end up in AS represented as a weird-looking HEX character. Is that okay to leave these in or should I remove all these carriage returns before importing the CSV file?
Library Information Systems Specialist
Hamilton College Library
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group