<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>My understanding of what I was doing at this meeting with OCLC was determining whether they were even a possible option by engaging senior leadership who would be capable of making this decision. We still don’t know for sure, but based on Terry’s reports
of his discussions with Taylor at OCLC, Terry identified that as the missing piece — OCLC senior leadership attitude and ability to make a commitment. I think it is premature to commit to them for many reasons. However, they seem rather eager to commit to
us, which was the point of the meeting.</div>
<div><br>
</div>
<div>I’m going to disagree with Tom, here. We’ve spent an enormous amount of time discussing putative and in many cases apparently speculative technology options at the steering committee meetings in advance of the actual technology committee’s deliberations
— all members of the committee should be discussing these options in depth and making recommendations before the steering committee discusses these. In the interests of everyone’s time and sanity, I would like to propose the following plan of action:</div>
<ol>
<li>The steering committee does not discuss technology until the full technology committee meets, discusses, and delivers its draft report.</li><li>SLO/the steering committee hold off on any decisions or recommendations on technology staffing until that report is delivered, since the actual person or entity hired will depend so much on the actual technology.</li></ol>
<div>I know we have a smaller group phone call this Friday to discuss what should be in the technology report, but I feel like we are chasing our own tails too far in advance of the discussions at the actual technology committee, which does not meet until the
17th of February, and which has not yet had these discussions.</div>
<div><br>
</div>
<div>Best, Gwen</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div style="font-family: Calibri; font-size: medium;">
<div style="widows: 1;">
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size: 10pt; font-family: Optima, serif;">Gwen Evans</span></span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"></span></p>
</div>
<div style="widows: 1;">
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size: 10pt; font-family: Optima, serif;">Executive Director, OhioLINK</span></span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"></span></p>
</div>
<div style="widows: 1; font-family: Calibri, sans-serif; font-size: 14px;">
<p class="MsoNormal"><a tabindex="0" href="https://email.osu.edu/owa/redir.aspx?C=yABf3LFOkkWRenaUhIeuu8fgj9Eh09EIzjzYk8LZChVNExG8a_rLuGXWeDNyfAo-Yn1uw1Chvck.&URL=http%3a%2f%2fwww.ohiolink.edu%2f" target="_blank" style="font-family: Optima, serif; font-size: 10pt; color: blue;">http://www.ohiolink.edu/</a></p>
</div>
<div style="widows: 1;">
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"></span></p>
</div>
<div style="widows: 1;">
<div>
<p class="MsoNormal"><br>
</p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size: 10pt; font-family: Optima, serif;">ph: 614-485-6608</span></span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; font-family: Optima, serif;">gwen@ohiolink.edu</span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"></span></p>
</div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size: 10pt; font-family: Optima, serif;">1224 Kinnear Rd</span></span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size: 10pt; font-family: Optima, serif;">Columbus, Ohio 43212</span></span></p>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-family: Optima; font-size: 13px;">ORCID ID:0000-0002-4560-0435</span></span></p>
<p class="MsoNormal"><span class="apple-style-span"></span></p>
<p class="p1"><b>Per Ohio Revised Code, this communication and any attachments may constitute a public record.</b><span class="s1"><b> (</b><a href="http://codes.ohio.gov/orc/149.43"><span class="s2"><b>http://codes.ohio.gov/orc/149.43</b></span></a><b>)</b></span></p>
</div>
</div>
</div>
</div>
<div><br>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Reese, Terry P." <<a href="mailto:reese.2179@osu.edu">reese.2179@osu.edu</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, February 10, 2016 at 2:48 AM<br>
<span style="font-weight:bold">To: </span>Gwen Evans <<a href="mailto:gwen@ohiolink.edu">gwen@ohiolink.edu</a>>, DPLAsteering <<a href="mailto:dplasteering@lists.oplin.org">dplasteering@lists.oplin.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: Meeting with OCLC<br>
</div>
<div><br>
</div>
<div 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">
<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;}
@font-face
{font-family:Optima;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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.apple-style-span
{mso-style-name:apple-style-span;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
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.s1
{mso-style-name:s1;}
span.s2
{mso-style-name:s2;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thanks for the update Gwen. I’ve gotten the same impression that this is something OCLC seems pretty interested in thinking about. I will say, even
if OCLC were willing to go forward, I’m still not sure this would be the best option for Ohio. I could see working in parallel , maybe a pilot to test aggregation, and a separate track working with a well-known technology stack. I think OCLC could potentially
offer institutions an avenue for providing metadata to the project, I just wouldn’t be enthusiastic of turning the technology stack over to them. While doing so frees the state hub from managing a system, it also comes with a significant technology cost,
and I think, only kicks the technology question down the road for another 3 years. I also have significant reservations that 1) this is a project that will hold their interest to get the kind of updates it needs, and 2) that they can modify the gateway to
meet our needs. I work with OCLC a lot on these types of projects (that fall outside of WorldCat) and their track record of bringing these types of things to fruition and supporting them long-term has not been good in my opinion. Things tend to get half
done, and I would prefer not to work with a 1ˇ2 solution.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">My personal option (and I may be the only one) – but if we don’t have an organization in this state willing, and able to handle the aggregation component
– it’s not time for Ohio to submit a proposal. OCLC may have a role to play and place in that space, but I don’t have a lot of enthusiasm for them being our technology infrastructure. But as I say, that could be just me. I know that is what Nathan and I
will be working with the subcommittee to make more clear. Because I see a number of scenerios based on the different hub homes, and OCLC managing the technology certainly is one. I just don’t think it would be my first or second choice.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">--tr<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><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><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> DPLAsteering [<a href="mailto:dplasteering-bounces@lists.oplin.org">mailto:dplasteering-bounces@lists.oplin.org</a>]
<b>On Behalf Of </b>Evans, Gwen<br>
<b>Sent:</b> Tuesday, February 9, 2016 5:25 PM<br>
<b>To:</b> DPLAsteering <<a href="mailto:dplasteering@lists.oplin.org">dplasteering@lists.oplin.org</a>><br>
<b>Subject:</b> [DPLAsteering] Meeting with OCLC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Hello All — I met with Bruce Crocco and Mary Sauer-Games today about DPLA. I asked two things of them: Can they get past the CC-0 requirement for metadata,
and if they could, could they make a decision quickly about partnering with the DPLA in Ohio group to work on the aggregator. They said they think they could have a yes/no answer about metadata by next Friday’s Steering Committee meeting, and shortly after
that they would confirm whether they would be willing to be the technology hub aggregator (I mentioned that we were planning to apply early summer, but we had meetings scheduled each month and would expect an answer on that question in March. Mary has been
talking to Taylor so he has the level of detail needed. I emphasized that this was a three year commitment, not for all time, and the benefits of OCLC engagement would be that they would be able to assess what the business opportunities were, if any. We did
discuss the necessity of being more or less ready to go (or ready to start) implementing if DPLA accepts our application.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">They (Mary, really) expressed serious interest; I think if they deliver on the metadata yes/no on time, then we can press them on the next commitment. I would
recommend that we have a “plan A” for hub hosting and management just in case they say no, or waffle too long.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Best, Gwen<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size:10.0pt;font-family:Optima;color:black">Gwen Evans</span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size:10.0pt;font-family:Optima;color:black">Executive Director, OhioLINK</span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><a href="https://email.osu.edu/owa/redir.aspx?C=yABf3LFOkkWRenaUhIeuu8fgj9Eh09EIzjzYk8LZChVNExG8a_rLuGXWeDNyfAo-Yn1uw1Chvck.&URL=http%3a%2f%2fwww.ohiolink.edu%2f" target="_blank"><span style="font-size:10.0pt;font-family:Optima">http://www.ohiolink.edu/</span></a><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size:10.0pt;font-family:Optima;color:black">ph: 614-485-6608</span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Optima;color:black"><a href="mailto:gwen@ohiolink.edu">gwen@ohiolink.edu</a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size:10.0pt;font-family:Optima;color:black">1224 Kinnear Rd</span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size:10.0pt;font-family:Optima;color:black">Columbus, Ohio 43212</span></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span class="apple-style-span"><span style="font-size:10.0pt;font-family:Optima;color:black">ORCID ID:0000-0002-4560-0435</span></span><span style="color:black"><o:p></o:p></span></p>
<p class="p1"><b><span style="font-size: 13.5pt; font-family: Calibri, sans-serif; color: black;">Per Ohio Revised Code, this communication and any attachments may constitute a public record.<span class="s1"> (</span></span></b><span class="s1"><span style="font-size: 13.5pt; font-family: Calibri, sans-serif; color: black;"><a href="http://codes.ohio.gov/orc/149.43"><span class="s2"><b>http://codes.ohio.gov/orc/149.43</b></span></a><b>)</b></span></span><span style="font-size: 13.5pt; font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>