<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi everyone, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In August 2021, a <a href="http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2021-August/008619.html">
list message</a> 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.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards. –julie<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Julie Wetherill<o:p></o:p></p>
<p class="MsoNormal">HUIT Library Technology Services<o:p></o:p></p>
<p class="MsoNormal">Harvard University<o:p></o:p></p>
</div>
</body>
</html>