Why not change IndependantBranches?
So there's this text in the kohadocs.git en/manual.xml about IndependantBranches that says "It is important that this value be set before going live and that it NOT be changed." The kohadocs.git log message of when that IndependentBranches warning line was added is commit c2885b75d1dd8085df072fcd0af17d1bbe046f90 "integrate wayne state manual contents" Anyone know why it's important that this value not be changed after going live? Anecdotes after asking on IRC a few times and by direct mail suggests that some have tried changing it and not noticed anything break - just the behaviour changes and some patrons might not be visible by any staff except a superlibrarian. Thanks in advance for any answers, -- MJ Ray, Software Engineering Specialist, www.software.coop member. Emails 3 x daily: please use info@software.coop for faster answer. Turo Technology LLP, reg'd in England+Wales, number OC303457 Registered Office: 12 Canada Road, Erith, LONDON, DA8 2HE
I cannot imagine why altering that syspref would break anything. It does indeed only modify runtime behavior. In fact, CCFLS has switched it on and off at various time with no negative side effects. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com ) On Fri, Nov 16, 2012 at 7:24 AM, MJ Ray <mjr@phonecoop.coop> wrote:
So there's this text in the kohadocs.git en/manual.xml about IndependantBranches that says
"It is important that this value be set before going live and that it NOT be changed."
The kohadocs.git log message of when that IndependentBranches warning line was added is commit c2885b75d1dd8085df072fcd0af17d1bbe046f90 "integrate wayne state manual contents"
Anyone know why it's important that this value not be changed after going live?
Anecdotes after asking on IRC a few times and by direct mail suggests that some have tried changing it and not noticed anything break - just the behaviour changes and some patrons might not be visible by any staff except a superlibrarian.
Thanks in advance for any answers, -- MJ Ray, Software Engineering Specialist, www.software.coop member. Emails 3 x daily: please use info@software.coop for faster answer. Turo Technology LLP, reg'd in England+Wales, number OC303457 Registered Office: 12 Canada Road, Erith, LONDON, DA8 2HE
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
What happens if a borrower has some items due in the future from other branch and you switch to independent branches? Regards To+ On Fri, Nov 16, 2012 at 10:16 AM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
I cannot imagine why altering that syspref would break anything. It does indeed only modify runtime behavior. In fact, CCFLS has switched it on and off at various time with no negative side effects.
Kyle
http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com )
On Fri, Nov 16, 2012 at 7:24 AM, MJ Ray <mjr@phonecoop.coop> wrote:
So there's this text in the kohadocs.git en/manual.xml about IndependantBranches that says
"It is important that this value be set before going live and that it NOT be changed."
The kohadocs.git log message of when that IndependentBranches warning line was added is commit c2885b75d1dd8085df072fcd0af17d1bbe046f90 "integrate wayne state manual contents"
Anyone know why it's important that this value not be changed after going live?
Anecdotes after asking on IRC a few times and by direct mail suggests that some have tried changing it and not noticed anything break - just the behaviour changes and some patrons might not be visible by any staff except a superlibrarian.
Thanks in advance for any answers, -- MJ Ray, Software Engineering Specialist, www.software.coop member. Emails 3 x daily: please use info@software.coop for faster answer. Turo Technology LLP, reg'd in England+Wales, number OC303457 Registered Office: 12 Canada Road, Erith, LONDON, DA8 2HE
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Le 16/11/2012 14:16, Kyle Hall a écrit :
I cannot imagine why altering that syspref would break anything. Try to change the "marcflavour" one ;-) It does indeed only modify runtime behavior. In fact, CCFLS has switched it on and off at various time with no negative side effects. But I agree with you, it's probably harmless, *if* you know what you're doing and are ready to update all your circulation/transfer rules, because there are many consequences.
Side comment = BibLibre problem solved on mailing lists ! side comment of the side comment = We lost time investigating why I did not recieved the answers to my "Bugzilla change proposal" (while it was OK for other messages and others at BibLibre, since yesterday 6PM local-time). It was because "dedup" parameter was ON => if you send a mail to the list AND cc: or to: someone who subscribed the list, he will recieve the mail only once (mailman will realize it's useless to send it to cc: and to: ppl !) -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
Paul Poulain wrote:
It was because "dedup" parameter was ON => if you send a mail to the list AND cc: or to: someone who subscribed the list, he will recieve the mail only once (mailman will realize it's useless to send it to cc: and to: ppl !)
Thanks to all who've answered on the IndependantBranches change. I'll look into Tomas's question unless anyone knows what happens? aside: The dedup parameter should be OFF - the copy sent via the list is always useful because Mailman adds the various List-* headers which switches on mailing list support in list-compatible software (which is why I can set my reply preference to list-only, for example, or I could unsubscribe with two clicks). Sadly, much email software still isn't compatible with mailing lists. I describe ones I know at http://mjr.towers.org.uk/comp/list-mua - please send me any updates directly, and/or open bug reports with your email software producers - the internet will thank you! Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
Le 16/11/2012 14:56, MJ Ray a écrit :
aside: The dedup parameter should be OFF - the copy sent via the list is always useful because Mailman adds the various List-* headers which switches on mailing list support in list-compatible software (which is why I can set my reply preference to list-only, for example, or I could unsubscribe with two clicks).
2 things: * I've nothing against that (nothing for as well, it doesn't matter), do others agree ? * the dedup ON does something only if you're in the cc: or to:, which doesn't happen frequently afaik. It's here for years and I didn't spotted it until those days. But, once again = what do others think ? If majority, I have nothing against changing. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
I am very tired right now ... so I'm sorry if I missed something .. but do I need to update the manual?? Nicole
Nicole Engard <nengard@gmail.com>
I am very tired right now ... so I'm sorry if I missed something .. but do I need to update the manual??
About the IndependantBranches warning? It's not clear. We're going to give it a test and see if anything breaks. I intend to send you a patch for manual.xml in light of our experiences (either weaken the warning, or explain why it's there) in about a month. Nudge me if I forget... Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
participants (5)
-
Kyle Hall -
MJ Ray -
Nicole Engard -
Paul Poulain -
Tomas Cohen Arazi