[Koha-devel] About defaults of indicators for auth merges
Marcel de Rooy
M.de.Rooy at rijksmuseum.nl
Wed Jan 18 13:47:06 CET 2017
Hi Zeno,
Good observations again !
I posted my response on Bugzilla report 14769. Those interested will pick it up from there.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14769
Thanks,
Marcel
________________________________
Van: Tajoli Zeno <z.tajoli at cineca.it>
Verzonden: dinsdag 17 januari 2017 17:05:36
Aan: Marcel de Rooy; Koha-devel
Onderwerp: Re: About defaults of indicators for auth merges
Hi Marcel,
Il 17/01/2017 15:25, Marcel de Rooy ha scritto:
> 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 ;)
in fact we partialy trust the indicators from the authority record
tag 110 'A' + tag 111 'B' = tag 100 'CC'
an tag 100 'CC' is connect with biblios 100s, 700s, 600s, etc.
I hope that before to definitily save I can fix indicators in auth.
I think is mandatory to have 'change-by-hand' in merge.
After I save; now modifications start on biblios records and tags.
What we want ?
Knowing that auth tag = 100, I know that I can copy 1° auth indicator
into 1° bib tag indicator.
And for the second bib tag indicator ?
Two option:
-1) default of bib tag framewok [your solution]
-2) mantain what is still present [I prefer this option].
I think that the selection between the two option could by done by a
system preference.
Bye
Zeno Tajoli
--
Zeno Tajoli
/SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche
Email: z.tajoli at cineca.it Fax: 051/6132198
*CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20170118/1a5102c9/attachment.html>
More information about the Koha-devel
mailing list