<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:"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: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>Hi all,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, I was testing authorities in Sprint 2 of the web client, mostly out of curiosity since we don’t currently use authorities. I came across something I thought was odd and reported it, and it turns out to be outside the scope of the testing since the behavior I observed is the same as it is in the current client. Before I go to Launchpad with a development request/bug fix, I wanted to check with anyone who is currently using authorities in Evergreen.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What I discovered was that, in Manage Authorities, I was able to delete an auth record that was linked to bib records. I didn’t expect that; I assumed it would behave like other records that are linked together, like not deleting bib records with copies attached. Instead, the bib records in the web client were left pointing to an auth record that no longer existed. So since it apparently behaves that way in the current client (according the responses my ticket in Lighthouse got), my question is: should it? I don’t see any bugs entered in Launchpad for it yet. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Since we aren’t using authorities yet, I don’t have a living example to put in a Launchpad ticket. Has anyone else seen this happen in their system, and do they consider it to be a problem?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Mary<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Mary Llewellyn<o:p></o:p></p><p class=MsoNormal>Database Manager<o:p></o:p></p><p class=MsoNormal>Bibliomation, Inc.<o:p></o:p></p><p class=MsoNormal>24 Wooster Ave.<o:p></o:p></p><p class=MsoNormal>Waterbury, CT 06708<o:p></o:p></p><p class=MsoNormal>mllewell@biblio.org<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>