<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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;}
--></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=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I have added several wish list items we discussed during the cataloging interest group meeting held at this year’s Evergreen International Conference. They are:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Link to Edit MARC in record summary<o:p></o:p></b></p><p class=MsoNormal><a href="https://bugs.launchpad.net/evergreen/+bug/1297833">https://bugs.launchpad.net/evergreen/+bug/1297833</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'>In the record summary, in addition to links for Add Volumes and View MARC, add a link to Edit MARC. Access to the link would be controlled by permissions so that if user did not have permission to edit a MARC record the link would be “grayed” out and not functional for them. This would allow catalogers to access Edit MARC functionality more quickly and improve workflow.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>MARC tag/field edit permissions<o:p></o:p></b></p><p class=MsoNormal><a href="https://bugs.launchpad.net/evergreen/+bug/1297836">https://bugs.launchpad.net/evergreen/+bug/1297836</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'>Within MARC Edit, the ability to set permissions by MARC tag/field so that a library could assign editing tasks for a specific field to an individual user. For example, allowing a user to edit only the 300 field in the MARC record and not be able to edit any other field.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'>In addition to being controlled by permissions, the ability to allow specific tag/field edits should also be a library or server setting so that a library or consortium can allow or disallow the functionality as a whole.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Ability to display notes in public facing OPAC by specific library<o:p></o:p></b></p><p class=MsoNormal><a href="https://bugs.launchpad.net/evergreen/+bug/1297838">https://bugs.launchpad.net/evergreen/+bug/1297838</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'>In library consortia, local notes (e.g. 590s) specific to an individual library’s copy/item is not generally allowed. We would like the ability to make local notes in the MARC bibliographic record display in OPAC searches scoped to the specific library. We envision this to be similar to the |9 in 856 fields whereby coding within the field creates local notes that would then display only to the system or branch indicated in the field. This would also be valuable to other note fields as well. For example, where different libraries have different use and reproduction rights that could be indicated in a 540 note scoped for an individual library. These notes would be repeatable with in the MARC bibliographic record.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For those of you that requested or supported the wish list items, please take a moment to add to the Launchpad report, whether to clarify your request or to add that it effects you. If you did not request the report, please login and do the same, or let us know where there may be problems with the request we did not foresee in our discussion.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please also let me know if I missed a discussion item you would like to add as a wish list or bug fix.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><i><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>Elaine</span></i><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br>J. Elaine Hardy<br>PINES & Collaborative Projects Manager<br>Georgia Public Library Service<br>1800 Century Place, Ste 150<br>Atlanta, Ga. 30345-4304<br><br>404.235-7128<br>404.235-7201, fax<br>ehardy@georgialibraries.org<br>www.georgialibraries.org<br>www.georgialibraries.org/pines</span><o:p></o:p></p></div></body></html>