[Archivesspace_Users_Group] Digital objects import with incorrect Published value

[Wendy Scheir]

I think a related or adjacent issue to this is that there are 2 separate
*Publish?* fields for each Digital Object record, but the import
spreadsheet has the option to select TRUE/FALSE for only 1 of them.

The way we're using DOs, sometimes (often, actually) we want one=TRUE and
the other=FALSE within a single record.

Wendy

The New Archives and Special Collections

On Mon, Jan 10, 2022, 5:11 PM Wetherill, Julie M. <
julie_wetherill at harvard.edu> wrote:

> Hi everyone,
>
>
>
> In August 2021, a list message
> <http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2021-August/008619.html>
> from Benn Joseph at Northwestern UL described their trouble getting
> incorrect Publish values when importing digital objects via spreadsheet.
> Harvard migrated to v3.0.2 in Fall 2021 and we also have this problem. It
> seems like the ASpace code that interprets the incoming spreadsheet data is
> being extra picky about the Type value of the “publish” (Publish Digital
> Object Record) attribute that is supplied in the spreadsheet.
>
>
>
> If the archivist uses the TRUE/FALSE controlled values provided in the
> official template on github (bulk_import_DO_template.xlsx), digital objects
> load with the correct “publish” values and their PUI display looks good.
> When I run the TYPE function on these values, I get type 4 (logical value).
>
>
>
> But sometimes, an archivist will paste in TRUE/FALSE values copied from
> another file (especially true in high volume automated workflows). At a
> glance these TRUE/FALSE values look identical but they aren’t. I noticed
> that these values are left aligned in the cell, rather than centered as
> Excel does to indicate a logical TRUE or FALSE. And when I run the TYPE
> function on a cell with these values I get type 2 (text). Seems like ASpace
> wants only the logical TRUE/FALSE. An imported digital object that has the
> text value TRUE for “publish” will be set to the default FALSE
> (unpublished). When this happens in high volume it’s a mess to clean up.
> And despite being marked Published=FALSE in staff mode, in the PUI, these
> digital objects are partially displaying. By that I mean, there is no
> digital link but the DO’s are labeled DIGITAL and display in the PUI list
> of digital objects.
>
>
>
> I guess the work-around is user education (warn users to only supply
> logical TRUE/FALSE). But I’d prefer we tweaked ASpace code to accept either
> the logical or text value of TRUE/FALSE as I suspect used to be the case
> when spreadsheet import was plugin-based.
>
>
>
> Regards. –julie
>
>
>
> Julie Wetherill
>
> HUIT Library Technology Services
>
> Harvard University
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220110/c9193635/attachment.html>