<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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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">
<div class="WordSection1">
<p class="MsoNormal">Hello, all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We’re looking to improve our digitization on demand, and I’m hoping other people may be willing to tell us their workflows. We’re particularly interested in cases where reference staff are creating only one or two images per collection,
so we end up with a batch of data relating to multiple collections that we need to get into ASpace and our digital repository. While our workflows for our repository are pretty solid, ASpace is another story. We’ve looked at the Digitization on Demand plug-in
developed by Hudson Molonglo, and possible ASpace API solutions. Does anybody have a really efficient way of moving this data around? We’d love to hear about it!<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Adrienne Pruitt </b><span style="font-size:9.0pt">| Collections Management Archivist<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt">Digital Collections and Archives<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt">Tufts University<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt"><a href="mailto:adrienne.pruitt@tufts.edu"><span style="color:windowtext">adrienne.pruitt@tufts.edu</span></a> |<span style="background:white">617-627-0957<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>