[Bug 24501] New: Authorities 'merge' is confusing
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Bug ID: 24501 Summary: Authorities 'merge' is confusing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs@lists.koha-community.org Reporter: nick@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org While authority updates sometimes happen because of the merging of authorities, authority record edits also cause a need to 'merge' Perhaps the cronjob and sysprefs should refer to 'updating' authorities? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 --- Comment #1 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- There's a function within Koha two take two authority records and combine them into one authority record. Koha refers to this as merging. That's a good name for that and doesn't confuse people. But then there's also a cron job that takes changes made to authority records and pushes them out to bibs. Koha also refers to this as merging. This *does* confuse people. They see a cron called "merge_authorities.pl" and assume it's going to clean up duplicate authorities or something. So I'd propose renaming the cron and the various system preferences that refer to the cron, though I understand that's a change to a very well-established Koha feature. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I understand that it is confusing, but changing a cronjob name means that in every installations people might have to change their cronjob setup... I am not sure if we should do this. And if we do it, maybe it should be a gradual process turning the current script into a wrapper that sends a deprecation warning to the logs for one release and asks you to switch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy@rijksmuseum.nl --- Comment #3 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> ---
From ExLibris: Authorities - Preferred Term Correction – This job performs preferred term correction on all bibliographic records that are linked to authority records using the Authorities - Link BIB Headings job. For example, if a bibliographic record contains the non-preferred term “Narcotics, Control of,” and the associated authority record contains the preferred term “Drug control,” the Authorities – Preferred Term Correction job replaces “Narcotics, Control of” with the preferred term “Drug control.” Bibliographic records are also updated with any subsequent updates to authority records.
=> The general term updating is used here in connection with preferred term correction. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 --- Comment #4 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- OCLC: Once you control a heading (and add or replace the record in WorldCat), the heading in the bibliographic record is automatically updated whenever the linked authority record changes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 --- Comment #5 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #2)
I understand that it is confusing, but changing a cronjob name means that in every installations people might have to change their cronjob setup... I am not sure if we should do this. And if we do it, maybe it should be a gradual process turning the current script into a wrapper that sends a deprecation warning to the logs for one release and asks you to switch.
We have renamed cron jobs in the past. But I agree that we should not do that too often ;) In this case I think it is more important to update interface, documentation etc. and even the routine name (C4::AuthoritiesMarc::merge) than renaming the script and cronjobs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Henry Bolshaw <bolshawh@parliament.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bolshawh@parliament.uk -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #6 from David Cook <dcook@prosentient.com.au> --- (In reply to Marcel de Rooy from comment #5)
We have renamed cron jobs in the past. But I agree that we should not do that too often ;) In this case I think it is more important to update interface, documentation etc. and even the routine name (C4::AuthoritiesMarc::merge) than renaming the script and cronjobs.
Agreed. Having a legacy script name isn't too big of a problem, if you can open that file and see that it's about processing heading updates in bib records from authority records. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=28011 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Catrina Berka <catrina@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |catrina@bywatersolutions.co | |m --- Comment #7 from Catrina Berka <catrina@bywatersolutions.com> --- While the documentation has great warning notes about the actual function of this cron, I agree with the previous comments that renaming it will reduce confusion. Any plan, however slow, that moves us towards this end would be welcome. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Esther Melander <esther.melander@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |esther.melander@bywatersolu | |tions.com --- Comment #8 from Esther Melander <esther.melander@bywatersolutions.com> --- Even if the cron is not renamed, it would be helpful to rename the system preference AuthorityMergeLimit to AuthorityLinkLimit or something similar and provide clarifying language in the system preference description. These system preferences should be considered for clarification/renaming: AuthorityMergeLimit AuthorityMergeMode -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Maude Boudreau <maude.boudreau@collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maude.boudreau@collecto.ca -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24501 Miranda Nero <mnero@oslri.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mnero@oslri.net -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org