<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</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>
<div>Lisa Hinchliffe and at least one other person pointed out the nice ability to prioritize databases in LibGuides displays. I like this, too. Again, though, what I would like to see is a way to use a
<i>single source</i> for databases metadata that can be reused in multiple places. The primary place where we keep that data is in our ERM, CORAL. At this point, LibGuides 2.0 does not support an easy way to link the two without duplication of maintenance effort.
Yes, there is a way to do a one-time import into LibGuides of databases information, but SpringShare does not yet support a more robust way for these two systems to “talk” to one another. I think this might be a step back from what was available in LibGuides
1.0, but I’m less familiar with 1.0 than 2.0.</div>
</div>
</div>
<div><br>
</div>
<div>With very limited time to devote to management of e-resources along with the very big scope of the work, it’s very important for me that ongoing maintenance be handled as efficiently as possible. That seems to be a good, basic principle.</div>
<div><br>
</div>
<div>Steve</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE">
<div><br>
</div>
<div><a href="http://www.wheaton.edu/Academics/Faculty/O/Steve-Oberg" style="color: purple;">Steve Oberg</a></div>
<div>Assistant Professor of Library Science</div>
<div>Electronic Resources and Serials</div>
<div>Wheaton College (IL)</div>
<div>+1 (630) 752-5852</div>
<div><br>
</div>
<div>NASIG Vice-President/President-Elect</div>
<div></div>
<div><img src="cid:53ABEA4C-9117-4FE8-A026-C878AD305E81" type="image/png" width="175.000000" height="48.000000" alt="NASIG - http://www.nasig.org"></div>
</div>
</div>
<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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Corbel;
panose-1:2 11 5 3 2 2 4 2 2 4;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Tahoma","sans-serif";
color:#002164;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Tahoma","sans-serif";
color:#002164;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
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>
</body>
</html>