Untitled entries on import

[Felicity Crowe]

Hi

I’d be grateful for any advice. After importing a CSV file into AtoM, all entries containing accented characters (e.g. à, é, è) were replaced with catalogue entries titled “untitled” (for example Gunn MSS XIX.3 here). I’d like to delete these “untitled” entries from the catalogue, but I can’t access their pages and visiting their slugs results in a 500 Error. Does anyone know how I can delete these records?

Appropriately for today, these entries seem like the undead - not really alive, but impossible to kill.

Help would be greatly appreciated!

Best wishes

Felicity

[Dan Gillean]

Hi Felicity, 

First thing I would recommend checking is that your CSV is actually UTF-8 encoded. The errors you describe sound similar to cases when AtoM encounters special characters it does not recognize. 

Note that while it IS possible to get a valid UTF-8 CSV out of newer versions of Microsoft Excel, they still make it really hard, and by default MS continues to ignore established de fact standards and use its own custom line endings and character encodings, which can cause all sorts of weird behaviors on import - see this section of the import documentation. Generally we recommend using LibreOffice Calc or similar as an alternative.

Don't forget, you can also validate your CSVs before running an import, which can tell you a lot about the likely outcome and help you spot potential issues in advance. See: 

• https://www.accesstomemory.org/docs/latest/user-manual/import-export/csv-validation/

Dan Gillean, MAS, MLIS
Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

he / him

--
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-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/30d279e0-3c2d-4500-9f6b-f8094469c0cbn%40googlegroups.com.

[Felicity Crowe]

Thanks Dan, this is really helpful! I think I may not have saved the spreadsheet as a UTF-8 CSV, so I'll have another go. We don't seem to have an option in AtoM to validate CSVs, which I expect is because we're still using the 2.5.3 version (hoping to upgrade soon).

Thanks again,

Felicity