Skip to first unread message
tanisfr...@gmail.com
May 18, 2018, 11:37:43 AM5/18/18
to AtoM Users
Hi everyone,
I've read all the topics on this but still have problems. Seeking advice.
I haven't added LegacyID to my csv and my records link by the slug. I made sure the source_name, repository, and title match. I've tried limiting to my repository also, but in any case it always just creates a new record.
What else can I do? I thought about asking someone to show me how to use the command line to see what legacyID AtoM had created so I can use that.
If there's a way I can use the command line to tell the import to look for matches on the slug first, let me know, or other advice on how to make this work.
Other question, if I changed the form field from our institution's set form, does that matter? For example, our set form is ISAD. I changed the default form to RAD in this case and I am using a RAD template csv.
Thank you!
Tanis
Dan Gillean
May 21, 2018, 2:10:07 PM5/21/18
to ICA-AtoM Users
Hi Tanis,
You can double-check what source name was saved in AtoM's database for a particular hierarchy by looking in the Admin section of the edit template:
There's no option to input a source name via the user interface, so by default the import CSV's file name is used. This is noted in the docs in this section:
The best way to check the legacyID that AtoM is looking for on import is to first export the records in CSV format, and see what values AtoM uses to populate the legacyID column. You can modify that export file directly, and then reimport it as an update. You can also use the "Skip unmatched" option so that AtoM won't create new records if no match is found - instead, it will simply report in the console, and skip the records entirely. You could also try improving the match by using the repository dropdown in the import configuration to limit how many records are checked - or if you are importing one archival hierarchy at a time, then limit the matching to a particular top-level description. See:
Note that if that doesn't work, you could perhaps try importing with no legacyID - normally, when a match can't be found on source_name and legacyID, then AtoM will look for an exact match on title, repository, and identifier.
Instructions for CSV imports from the command-line are all outlined in the Administrator's manual, here:
I don't believe that the template used (ISAD or RAD) should matter for most fields - both CSVs use the same internal database names for the fields, and the templates are merely display differences where the underlying fields are the same in the database.
Cheers,
--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/0018f7ee-ddec-4e40-ba15-e6313070535b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages