<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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">Hello Sara,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think you’re encountering this bug which is being worked on for the next release:
<a href="https://archivesspace.atlassian.net/browse/ANW-1526">https://archivesspace.atlassian.net/browse/ANW-1526</a>. The fix is up on our test server at
<a href="https://test.archivesspace.org/staff">https://test.archivesspace.org/staff</a>. Though you won’t be able to try it with your own data there (unless you import it), you could take a look to see if the results for digital objects are more what you’d
expect. It’d be great if you’d comment on the issue if you test it and find something different.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Christine<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Christine Di Bella</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">ArchivesSpace Program Manager</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:christine.dibella@lyrasis.org"><span style="color:blue">christine.dibella@lyrasis.org</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">800.999.8558 x2905</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">678-235-2905</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><img border="0" width="267" height="61" style="width:2.7812in;height:.6354in" id="x_x_Picture_x0020_1" src="cid:image002.jpg@01D9149C.54F8DE70" alt="ASpaceOrgHomeMedium"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Szakaly, Sara J - APHIS<br>
<b>Sent:</b> Tuesday, December 20, 2022 12:56 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] File versions not appearing in reports<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello all, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When running reports, both custom and the built-in file version list report, I cannot get digital object file versions to appear in the report. The field is just blank. Other linked records such as dates appear as expected.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">File versions do appear in digital object <i>component</i> reports though.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve tried in both our instance and in the ArchivesSpace sandbox. We currently have v3.3.1, and I was experiencing the same issue in our previous version (v3.2.0)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Am I misunderstanding something? Any help would be appreciated, thanks!
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="margin-left:-4.8pt">
<tbody>
<tr style="height:.85pt">
<td valign="top" style="padding:0in 0in 0in 0in;height:.85pt">
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><img border="0" width="72" height="51" style="width:.75in;height:.5312in" id="Picture_x0020_1" src="cid:image003.jpg@01D9149C.54F8DE70" alt="https://www.aphis.usda.gov/js/USDA-Logo.jpg"></span><span style="font-family:"Arial",sans-serif"><o:p></o:p></span></p>
</td>
<td style="padding:0in 0in 0in 0in;height:.85pt">
<p class="MsoNormal"><b> </b><b><span style="font-size:12.0pt">Sara Szakaly, MLS</span></b><br>
Archivist & Records Manager<br>
APHIS Wildlife Services (WS)<br>
National Wildlife Research Center<br>
4101 Laporte Ave<br>
Fort Collins, CO 80521<br>
P: 970-266-6021<br>
<u><span style="color:blue"> <a href="mailto:Sara.J.Szakaly@usda.gov">Sara.J.Szakaly@usda.gov</a><o:p></o:p></span></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">In office: M, W, Th | Telework: Tu, F<u><span style="color:blue"><o:p></o:p></span></u></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><br>
<br>
<br>
<br>
This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil
or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.
<o:p></o:p></p>
</div>
</body>
</html>