[Archivesspace_Users_Group] Publish status set incorrectly in Accession csv import

[Wetherill, Julie M.]

Hi all,

We have a problem importing accession records by csv that seems to be limited to a single user's computer.

Accession imports by this staff user are loaded successfully, but the records always land in the system as published despite the accession_publish column being set to '0' (unpublished) across the board. Our public interface doesn't display accessions but PUI solr happily indexes them, so PUI users find these accession records but can't open them. So we don't want published accessions.

We are running v3.0.2 and the user (who I'm calling User 0) is working off a fresh accession csv template pulled from github.

Using the same csv, I am able to import accession records that load as unpublished. And other users in the same repository as User 0 can load that csv and get unpublished records. But not User 0.

All csv editing is done in a text editor and not Excel. I don't think this is an issue with user preferences or permissions (which are the same for everyone who has tested).

Using a hex viewer, I don't see anything funky going on with the value for accession_publish in the csv (it is the number zero).

Any ideas what is causing this weirdness? Many moons ago we had a similar issue importing EADs from spreadsheet and discovered that the internal Excel datatype assigned to the publish column was not what the loader expected, causing it to assign a default publish value regardless of the supplied value. But in the accessions case, Excel is not involved.

Thanks in advance for any advice you can offer. Regards. -julie

Julie Wetherill
HUIT Library Technology Services
Harvard University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221207/7ad38304/attachment.html>