<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:x="urn:schemas-microsoft-com:office:excel" 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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;}
/* List Definitions */
@list l0
{mso-list-id:196547569;
mso-list-type:hybrid;
mso-list-template-ids:1622043642 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1534221071;
mso-list-type:hybrid;
mso-list-template-ids:96927650 -34722198 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:919;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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"><span style="color:#1F497D">We put it in the 506: <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">=506 1\$aAccess limited to UNC Chapel Hill-authenticated users.$fUnlimited simultaneous users<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">=506 1\$aAccess limited to UNC Chapel Hill-authenticated users.$fLimited to three (3) concurrent users<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">=506 1\$aAccess limited to UNC Chapel Hill-authenticated users.$fLimited to one (1) concurrent user<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">This applies not just to ebooks, but also streaming media titles and anything else that happens to get cataloged through my section. In general these are NOT added to MARC records for e-journal titles.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Currently this does not display *<b>prominently</b>* in our online catalog view. A user needs to click on the “Full record” tab and look in the Notes section for the one labeled “Access restrictions:”
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">However, library staff---particularly front line public service staff and reserves staff---know to look there. That solves our primary problems:
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">users reporting that an ebook isn’t working and public service staff not knowing where to look to find out if it’s likely just a limited-concurrent user problem<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">limited-concurrent user books being placed on reserve – now reserve staff can warn professors and/or request an unlimited user model at the time reserves are being set up<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Technically, I suppose we should be putting $2local on the end, but we aren’t. Not sure why we didn’t. The values in $f are a locally controlled vocabulary, however.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We decided upon this field/usage when it looked like we’d be adding features to our public catalog to:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">more prominently display any MARC (or other data) mapped into that “Access restrictions” property<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">add an “Access level” facet so people could exclude single user ebooks, or include only unlimited user ebooks.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Shortly after we started this work, development on that catalog was frozen. We’re now building a new public catalog product, and expect it to include these features.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It was never our end users clamoring for this particular info, so we are living with the situation as-is for now.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Adding the fields to everything has been a gargantuan task, involving:
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Coordinating with acquisitions staff on a shared language for and place for this information where cataloging staff can easily find it for our collections.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Mapping YBP’s “purchase model” terms to our little local vocab for 506$f, locally and in YBP Technical Specifications for DDA Discovery & Purchase MARC records, and the “E-Shelf Ready” MARC we receive
from YBP for a subject-specific e-preferred approval plan<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Ongoing cataloging workflows (documentation, MarcEdit tasks, etc) for preparing batch vendor record sets all had to be updated<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Countless hours of running global updates in the ILS to add the field to collections retrospectively<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Manual project(s) to retrospectively update individually-copy cataloged firm ordered ebooks. (Going forward, ACQ staff updates a spreadsheet with new title purchases, including what platform the title’s
on and the “purchase model”. The spreadsheet auto-generates the 506 (and other platform/collection-specific fields) that need to be copied into each record by staff who do that copy cataloging, based on mappings and lookups.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Dealing with the terrible collections where the number of concurrent users varies per title: working with vendors/service providers to get per-title, specifics on concurrent users, in a form we could
use to match/merge into our existing MARC records. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We also use SerialsSolutions for MARC for some ebook collections (though they’re our MARC source of last resort due to quality issues and responsiveness to problem reports). We have 3 accounting units sharing
1 SerialsSolutions account. Each accounting unit has different coding practices for ebooks (relating to stats, local record management needs, etc), so each accounting unit needed to tweak/load their own SerialsSolutions ebook records. Since of course SerialsSolutions
can’t split our ebook MARC out into separate files per accounting unit, my answer was to write a script/app that would split up the records in separate files for the 3 units. It’s based on a spreadsheet that maps each tracked SerialsSolutions package to an
accounting unit. This was already being used when we started adding the 506s, so I added a column to the spreadsheet to assign the correct 506$f to each package. The script adds the 506 field to the records while it’s splitting them up for delivery to the
accounting units.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I guess overall, we’re a little weird in that, for a long time we had some statistical reporting requirements that affected the way we define and manage “collections.” This extends to our desire to have a proactive
system in place for reconciling/auditing access and discoverability (and verifying a title list of record to keep on file) for purchases of ebook frontlists, modules, collections, etc.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In general, whenever possible, for me a new “collection” needs to be set up/handled for anything where any of the following varies:
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">fiscal year content was purchased<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">accounting unit (I only handle cataloging for one, but my unit handles the cataloging or related work for some things that span units)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">platform/provider<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">purchased vs. subscribed vs. free/open vs. gratis access<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">MARC/metadata source/stream (copy cataloged vs. SerialsSolutions vs. OCLC WorldShare Collection Manager vs. vendor-provided batches vs. YBP “e-shelf ready” vs. … )
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">format of content (affects some workflow steps (fixed field batch editing!) and how we’re supposed to record stats)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">This is often a bear, and not always possible, but, in addition to generally making sense for our environment and allowing me to keep track (mostly) of and report on everything, it means we have relatively few
“collections” where the # of users varies within the collection. For example, it seems like a lot of libraries would consider all their books on Ebrary platform to be the “Ebrary ebook collection.” Meanwhile we distinguish between:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">ebrary academic complete (subscription, vendor MARC, unlimited users, 506 batch added)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">ebrary public library complete (subscription, vendor MARC, unlimited users, 506 batch added)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">ebrary title-by-title perpetual access, HSL (purchased (fo), copy cataloged, users vary, 506 added manually)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">ebrary title-by-title perpetual access, UNL (purchased (fo), vendor MARC, users vary, 506 mapped in from spreadsheet before load)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">ebrary title-by-title perpetual access, YBP e-preferred (purchased (ap), YBP MARC, users vary, 506 mapped in based on vendor specs)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">best, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-=-<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Kristina M. Spurgin – Library Data Strategist<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> E-Resources & Serials Management, Davis Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> University of North Carolina at Chapel Hill<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> CB#3938, Davis Library – Chapel Hill, NC 27514-8890<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> 919-962-3825 – kspurgin@email.unc.edu<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Eril-l [mailto:eril-l-bounces@lists.eril-l.org]
<b>On Behalf Of </b>Amy Lynn Fry<br>
<b>Sent:</b> Wednesday, March 22, 2017 10:02 AM<br>
<b>To:</b> Eril-l@lists.eril-l.org; Web Technologies in Libraries <WEB4LIB@LISTSERV.UC.EDU><br>
<b>Subject:</b> [Eril-l] notes in ebook records<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have gotten to the point where we really need to include notes in each of our ebook bib records about numbers of simultaneous users.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Have others of you found a need to do this retrospectively? How have you approached this?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m specifically interested in:<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Where in the record did you put the note? In the link? In a 5xx?<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>What does the note say?<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Does a note also appear within your openURL resolver, and what does that look like?<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>How did you handle books from the same vendor that have different user restrictions? For example, we have ebrary books that have 1, 3 or unlimited users. Do you put the same note in every book from that vendor (that says something like,
“Connect to ebook for use restrictions,” or something generic like that), or do you divide up the books into different groups so you can give more precise notes? If you divide them up, how do you manage them in your knowledgebase? Do you keep custom lists?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have Serials Solutions for our knowledgebase and get some MARC records from them for ebooks. We have Summon and 360 Link for discovery and openURL linking, and Innovative Sierra for our ILS.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your help! If you can link me to examples that would be very helpful, too.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Amy<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Amy Fry<o:p></o:p></p>
<p class="MsoNormal">Associate Professor, E-resources Librarian<o:p></o:p></p>
<p class="MsoNormal">Jerome Library<o:p></o:p></p>
<p class="MsoNormal">Bowling Green, OH 43403<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:afry@bgsu.edu">afry@bgsu.edu</a><o:p></o:p></p>
<p class="MsoNormal"><i>email is the best way to reach me</i><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>