https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31925
--- Comment #49 from David Cook <[email protected]> --- (In reply to Phil Ringnalda from comment #48) > I didn't bring it up because I thought it was new behavior. I brought it up > because it's the existing behavior which will impact workflows as a result > of this patch. Sure, there would be an impact, as there is a behaviour difference. I suppose a person could argue that it needs a system preference, although at what point do we draw a line under things... > For as long as AutoCreateAuthorities has existed, it has created them > ignoring the thesaurus in the bib record. If as one of my fellow catalogers > does, you save a bib imported from OCLC and then delete all the headings in > it from thesauri we don't use, then no matter which flavor of a heading came > first our current install of Koha will create an LC authority record from > it, and saving the authority record will at most (if some of the garbage > wasn't deleted) change the thesaurus from one we don't use to the one we do > use. If you've deleted all the headings in the bib record from thesauri you don't use, then why would you have an auto-generated authority for a thesaurus you don't use? > If this change applies to installs that don't use LinkerConsiderThesaurus as > well as those that do, then those installs will have to notice that this bug > landed, realize that it will be creating authorities from a thesaurus they > don't want, and alter their system to always check the thesaurus for any > newly created authority record before touching it. That would leave me > having to remember to *always* switch to a different tab, and open up a > popup window to be sure that I was looking at the correct space in a > multicharacter string for an 'a' to be sure something else hadn't slipped > in. I mark ones that I've checked, so I would only have to do that once, but > for people who don't, they would need to do that every time. Or work out a > way to find every authority record not in the thesaurus they want, and batch > change them all, before any time they do any work that might result in > saving an authority record. If they're not noticing what thesaurus the heading of a copy catalogued record has, I doubt that they'll notice or care what thesaurus is associated with their authority record. I'm not sure that I understand what you're saying here. Why would you need to switch to a different tab and look at the 008 for an authority record? I would assume that you'd know what thesaurus you use for your authority records. In that case, the only issue would be auto-generated authorities for bib headings associated with a different thesaurus. Auto-generated authority records are always a bit tough to control. That's why they're not the best idea. But I'm still not sure what you're getting at here. Could you rephrase your worry for your workflow? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
