<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="color: rgb(0, 0, 0); font-family: Calibri,Arial,Helvetica,sans-serif; font-size: 12pt;" dir="ltr">
<p>Hi Zeno,</p>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" style="color: rgb(0, 0, 0); font-family: Calibri,Arial,Helvetica,sans-serif; font-size: 12pt;" dir="ltr">
<p>You are right about the need for having default indicators too on the authority side. That would be welcome too.</p>
<p><br>
</p>
<p>But in this specific case (when we change authority type in a merge) we need as a fallback the default indicators of the biblio record. ( As you explained on bug 14769, we cannot trust the indicators from the authority record. Since the indicators on a 100
authority cannot be used on a 600 biblio field etc. -- Who invented those rules, should be rewarded ;)
</p>
<p><br>
</p>
<p>In the code we now copy the old biblio field indicators into the new biblio field, and these may be similarly wrong for another biblio field. So I would like to fallback to the default indicators of that new biblio field; they may still be wrong too, but
better than nothing. Choosing between two bicycles, while you want a car.</p>
<p><br>
</p>
<p>That said, this is advanced authority merging. I would normally not recommend changing type. It should be an exception. So probably we can consider this as minor issue.</p>
<p><br>
</p>
<p>Thanks for your feedback,</p>
<p>Marcel<br>
</p>
<p><br>
</p>
</div>
<hr tabindex="-1" style="width: 98%; display: inline-block;">
<div id="x_divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size: 11pt;"><b>Van:</b> Tajoli Zeno <z.tajoli@cineca.it><br>
<b>Verzonden:</b> dinsdag 17 januari 2017 09:51:40<br>
<b>Aan:</b> Marcel de Rooy; koha-devel<br>
<b>Onderwerp:</b> About defaults of indicators for auth merges</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size: 10pt;">
<div class="PlainText">Hi Marcel,<br>
<br>
I write to you and here same thoughts about defaults of indicators for <br>
auth merges.<br>
You say:<br>
"We actually need framework default indicators first to address merges<br>
crossing the authtype border correctly".<br>
As start we need to remember that indicators for Auth are different from <br>
Biblio indicators (see bug 14769).<br>
<br>
I think this true only for this specific case:<br>
auth 'A' type '1' merge auth 'B' type '2' = auth 'CC' type '3'<br>
<br>
in case<br>
auth 'A' type '1' merge auth 'B' type '2' = auth 'CC' type '1'<br>
we need to use indicators of auth 'A'<br>
<br>
The code of bug 9701 is about Biblio indicators.<br>
We need new code, in different .pl, and new columns, in different <br>
tables, for authority.<br>
<br>
Bye<br>
Zeno Tajoli<br>
<br>
<br>
-- <br>
Zeno Tajoli<br>
/SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche<br>
Email: z.tajoli@cineca.it Fax: 051/6132198<br>
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)<br>
</div>
</span></font></div>
</body>
</html>