<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Arial",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">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">FYI, the latest code4Lib has a couple articles on Alma/Primo. Both of these articles cover topics that came up in sessions at ELUNA, though I’m not sure if it’s the same authors as the presenters
</span><span style="font-family:Wingdings">J</span><span style="font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:9.0pt;color:#0070C0">Greg Bem, MLIS</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;color:#0070C0">Professor and Library Coordinator</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;color:#0070C0">Pronouns: <i>
he/him/his</i></span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;color:black">Contact Info</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:greg.bem@lwtech.edu%0d"><span style="font-size:9.0pt;color:blue">greg.bem@lwtech.edu</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:black">425-739-8100 xt.8898</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://www.lwtech.edu/campus-life/library"><span style="font-size:9.0pt;color:blue">http://www.lwtech.edu/campus-life/library</span></a></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> lita-l-request@lists.ala.org [mailto:lita-l-request@lists.ala.org]
<b>On Behalf Of </b>Junior Tidal<br>
<b>Sent:</b> Tuesday, May 7, 2019 8:59 AM<br>
<b>Subject:</b> [lita-l] code4Lib Journal Issue 44<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Apologies for cross posting. The newest issue of code4Lib Journal is now available -
<a href="https://journal.code4lib.org/issues/issues/issue44">https://journal.code4lib.org/issues/issues/issue44</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here is a breakdown of the articles in this issue:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14551">Editorial: New Editors, Diversity, and Representation</a><o:p></o:p></b></p>
<p class="MsoNormal">Junior Tidal<o:p></o:p></p>
<p class="MsoNormal">Welcoming new editors, new surveys, and thinking about diversity at code4Lib Journal.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14445">BC Digitized Collections: Towards a Microservices-based Solution to an Intractable Repository Problem</a><o:p></o:p></b></p>
<p class="MsoNormal">Chris Mayo, Adam Jazairi, Paige Walker, Luke Gaudreau<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Our Digital Repository Services department faced a crisis point in late 2017. Our vendor discontinued support for our digital repository software, and an intensive, multi-department, six-month field survey had
not turned up any potential replacements that fully met our needs. We began to experiment with a model that, rather than migrating to a new monolithic system, would more closely integrate multiple systems that we had already implemented—ArchivesSpace, Alma,
Primo, and MetaArchive—and introduce only one new component, namely Mirador. We determined that this was the quickest way to meet our needs, and began a full migration in spring of 2018. The primary benefit of a microservices-based solution for our collections
was the potential for customization; we therefore present our experiences in building and migrating to this system not as a blueprint but as a case study with lessons learned. Our hope is that in sharing our experience, we can help institutions in similar
situations determine 1) whether a microservices-based solution is a feasible approach to their problem, 2) which services could and should be integrated and how, and 3) whether the trade-offs inherent in this architectural approach are worth the flexibility
it offers.<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14371">Building a better book widget: Using Alma Analytics to automate new book discovery</a><o:p></o:p></b></p>
<p class="MsoNormal">Travis Clamon<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Are we doing enough to market newly acquired book titles? Libraries purchase and subscribe to many new book titles each year, both print and electronic. However, we rely on the expectation that users will periodically
search our systems to discover newly acquired titles. Static lists and displays have been traditional marketing methods for libraries, but require tedious time and effort to maintain. Without a practical solution for an academic library, East Tennessee State
University developed an automated process to generate book widgets utilizing data from Alma Analytics. These widgets are now deployed in our subject guides, website, and on our digital displays. This article outlines the development and implementation of these
widgets. We also discuss the challenges we encountered, such as finding image covers and custom subject tagging.
<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14481">Managing Discovery Problems with User Experience in Mind</a><o:p></o:p></b></p>
<p class="MsoNormal">Emery Shriver<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Williams Libraries recently developed a system for users to report problems they included while using the library catalog/discovery layer (Primo). Building on a method created by the Orbis Cascade Alliance,
we built a Google form that allows users to report problems connecting to full text (or any other issue) and automatically includes the permalink in their response. We soon realized that we could improve the user experience by automatically forwarding these
reports into our Ask a Librarian email service (LibAnswers) so we could offer alternative solutions while we worked on fixing the initial issue. The article will include an explanation of the process, reactions from public service staff, methods for managing
the problems once submitted, and code shared on GitHub for those interested in implementing the tool at their own library.<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14419">Responsive vs. Native Mobile Search: A Comparative Study of Transaction Logs</a><o:p></o:p></b></p>
<p class="MsoNormal">Jim Hahn<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">The Consortium of Academic and Research Libraries in Illinois (or CARLI) is comprised of 130 libraries, a majority of which participate in the union catalog I-Share for resource sharing. The consortium implemented
VuFind 4, a responsive web interface, as their shared union catalog in December 2017. This study compared search transaction logs from a native mobile app that serves the consortium with search transactions in the responsive mobile browser. Library professionals
in the consortium sought to understand the nature of mobile search features by evaluating the relative popularity of mobile devices used, search terms, and search facets within the two mobile search options. The significance of this research is that it provides
comparative data on mobile search features to the library UX community. <o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14443">Large-Scale Date Normalization in ArchivesSpace with Python, MySQL, and Timetwister</a><o:p></o:p></b></p>
<p class="MsoNormal">Alicia Detelich<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Normalization of legacy date metadata can be challenging, as standards and local practices for formulating dates have varied widely over time. With the advent of archival management systems such as ArchivesSpace,
structured, machine-actionable date metadata is becoming increasingly important for search and discovery of archival materials. This article describes a recent effort by a group of Yale University archivists to add ISO 8601-compliant dates to nearly 1 million
unstructured date records in ArchivesSpace, using a combination of Python, MySQL, and Timetwister, a Ruby gem developed at the New York Public Library (NYPL).<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14532">Visualizing Fedora-managed TEI and MEI documents within Islandora</a><o:p></o:p></b></p>
<p class="MsoNormal">Raffaele Viglianti, Marcus Emmanuel Barnes, Natkeeran Ledchumykanthan, Kirsta Stapelfeldt<o:p></o:p></p>
<p class="MsoNormal">The Early Modern Songscapes (EMS) project represents a development partnership between the University of Toronto Scarborough’s Digital Scholarship Unit (DSU), the University of Maryland, and the University of South Carolina. Developers,
librarians and faculty from both institutions have collaborated on an intermedia online platform designed to support the scholarly investigation of early modern English song. The first iteration of the platform, launched at the Early modern Songscapes Conference,
held February 8-9, 2019 at the University of Toronto’s Centre for Reformation and Renaissance Studies, serves Fedora-held Text Encoding Initiative (TEI) and Music Encoding Initiative (MEI) documents through a JavaScript viewer capable of being embedded within
the Islandora digital asset management framework. The viewer presents versions of a song’s musical notation and textual underlay followed by the entire song text.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">This article reviews the status of this technology, and the process of developing an XML framework for TEI and MEI editions that would serve the requirements of all stakeholder technologies. Beyond the applicability
of this technology in other digital scholarship contexts, the approach may serve others seeking methods for integrating technologies into Islandora or working across institutional development environments.<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://journal.code4lib.org/articles/14435">Creating a Low-cost, DIY Multimedia Studio in the Library</a><o:p></o:p></b></p>
<p class="MsoNormal">Bryan Elias Hull and Brandon Patterson<o:p></o:p></p>
<p class="MsoNormal">This case study will explain steps in creating a multimedia studio inside a health sciences library with existing software and a minimal budget. From ideation to creation to assessment, the process will be outlined in development phases
and include examples of documentation, user feedback, lessons learned, and future considerations. We’ll explore multimedia software like One Button Studio, GameCapture, Kaltura, Adobe Creative Cloud, Garage Band, and others and compare their effectiveness
when working on audio and visual projects in the library.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Junior Tidal<o:p></o:p></p>
<p class="MsoNormal">Coordinating Editor for issue 44<o:p></o:p></p>
<p class="MsoNormal">code4Lib Journal Editorial Committee<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
To maximize your use of LITA-L or to unsubscribe, see <a href="http://www.ala.org/lita/involve/email">
http://www.ala.org/lita/involve/email</a><o:p></o:p></span></p>
</div>
</div>
</body>
</html>