<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=Windows-1252">
<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;
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
{mso-style-priority:99;
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.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;}
/* List Definitions */
@list l0
{mso-list-id:2119250960;
mso-list-template-ids:712172250;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">Please join us at the FOLIO Forum Wednesday, July 26<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img width="300" height="140" id="Picture_x0020_1" src="cid:image001.png@01D2F59C.EF632080" alt="https://www.openlibraryenvironment.org/wp-content/uploads/2016/11/folio-logo-transparent-bkgnd-300x140.png"><o:p></o:p></p>
<p><b>Event: How to invent things that meet challenges in libraries<br>
Time: Wednesday, July 26, 2017 at<a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=FOLIO+Forum&iso=20170315T15&p1=1440&ah=1&am=30"> 11:00AM EST / 1600 GMT</a><br>
Register <a href="https://zoom.us/webinar/register/90faca33d00b9a848c34be5db4a05ad8" target="_blank">
Here</a></b><o:p></o:p></p>
<p>Everyone is not an inventor, but with the help of the user experience (UX) driven design method, everyone can learn how they can help improve and innovate the way libraries work in the future. This down-to-earth and practical method is what is being used
to design and develop FOLIO to be a system that addresses real library challenges. We would like to share it with as many people as possible to let library professionals invent solutions for workflow challenges in their local institutions. The solutions could
be apps or plugins for FOLIO, but they do not have to be: The principles of the UX driven design method can be used more generally to create solutions that are more low-tech — the focus is on creating solutions.<o:p></o:p></p>
<p>The starting point for the way the FOLIO system not only looks and feels — but what it does and how it does it — is based on researching library workflows and iterating over solution ideas with library professionals until a practical and good solution is
reached. This process can be divided into 6 steps:<o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Spot a problem<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Find the cause of the problem<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Ask questions<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Ideate<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Test your solution<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Adapt or restart<o:p></o:p></li></ol>
<p>In this forum, Filip will help library professionals utilize this method to invent things that meet challenges in libraries and turn their workflow frustrations into useful solutions.<o:p></o:p></p>
<p><b>SPEAKERS</b>: Filip Jakobsen, <i>UX lead, FOLIO; CEO & founder, Samhæng</i><o:p></o:p></p>
<p>Please use the hashtag #FOLIOforum on social media for these events.<o:p></o:p></p>
<p>The Open Library Community Forum is sponsored by<a href="https://www.openlibraryenvironment.org"> OLE</a> (Open Library Environment) and is governed by the OLE<a href="https://www.openlibraryenvironment.org/?page_id=76"> Code of Conduct</a>.<o:p></o:p></p>
<p>A recording of this Forum will be made available on the<a href="https://www.openlibraryenvironment.org"> OLE</a> website<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Eric Hartnett <br>
Associate Professor <br>
Director of Electronic Resources<br>
Texas A&M University Libraries <u><span style="color:blue"><br>
</span></u><a href="mailto:ehartnett@library.tamu.edu"><span style="color:blue">ehartnett@library.tamu.edu</span></a>
<br>
<br>
331 Library Annex | 5000 TAMU | College Station, TX 77840 <br>
<br>
Tel. 979.845.0797 <u><span style="color:blue"><br>
<br>
</span></u><a href="http://library.tamu.edu/"><span style="color:blue">http://library.tamu.edu</span></a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>