In the interest of release early, release often, I fixed the branches.pl problem so that new branches get the 'IS' and 'CU' branchrelations automatically so that they show up in the circulation module. I think this is getting pretty close to production ready now. Of course, if I go look at bugs.koha.org I might get a rude surprise. :) Steve.
Go, Steve, go! -pate On Wed, 23 Oct 2002, Tonnesen Steve wrote:
In the interest of release early, release often, I fixed the branches.pl problem so that new branches get the 'IS' and 'CU' branchrelations automatically so that they show up in the circulation module.
I think this is getting pretty close to production ready now.
Of course, if I go look at bugs.koha.org I might get a rude surprise. :)
Steve.
------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
_______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
On Wed, Oct 23, 2002 at 10:41:34AM -0700, Tonnesen Steve wrote:
I fixed the branches.pl problem so that new branches get the 'IS' and 'CU' branchrelations automatically so that they show up in the circulation module.
What are "IS" and "CU", anyway? For that matter, could you please explain what branchrelations are? -- Andrew Arensburger This message *does* represent the arensb@ooblick.com views of ooblick.com I am heavily armed, easily bored, and off my medication.
On Thu, 24 Oct 2002, Andrew Arensburger wrote:
On Wed, Oct 23, 2002 at 10:41:34AM -0700, Tonnesen Steve wrote:
I fixed the branches.pl problem so that new branches get the 'IS' and 'CU' branchrelations automatically so that they show up in the circulation module.
What are "IS" and "CU", anyway? For that matter, could you please explain what branchrelations are?
To be honest, I don't know. I just found them in the code. Functionally here's what the restrict: Branches that don't have the 'IS' branchrelation can't issue books (ie they don't show up in the "Select a Branch" area of circulation. Branches that don't have the 'CU' branchrelation set don't show up in the "To Branch" part of the branchtransfers page. All of this was made necessary because HLT is using the branch field for things that aren't really branches, namely collections of books either within or branch or that are spread across branches, so that different circulation rules have to be applied to different branches. My proposal was that this be handled through the use of virtual bookshelves to handle collection management (among other things). Steve.
Tonnesen Steve wrote:
On Thu, 24 Oct 2002, Andrew Arensburger wrote:
On Wed, Oct 23, 2002 at 10:41:34AM -0700, Tonnesen Steve wrote:
I fixed the branches.pl problem so that new branches get the 'IS' and 'CU' branchrelations automatically so that they show up in the circulation module.
What are "IS" and "CU", anyway? For that matter, could you please explain what branchrelations are?
Branches that don't have the 'IS' branchrelation can't issue books (ie they don't show up in the "Select a Branch" area of circulation.
Branches that don't have the 'CU' branchrelation set don't show up in the "To Branch" part of the branchtransfers page.
All of this was made necessary because HLT is using the branch field for things that aren't really branches, namely collections of books either within or branch or that are spread across branches, so that different circulation rules have to be applied to different branches. My proposal was that this be handled through the use of virtual bookshelves to handle collection management (among other things).
Steve.
Hi Steve and Andrew, This is all my fault! I added the "branchcategories" and "branchrelations" tables when I was working on the circulations code. I think this should all be reoganised. However Steve does seem to have fixed up the Installer so that it works out of the box. Perhaps the new Shelf.pm code is the answer.... Finlay
Tonnesen Steve wrote:
On Thu, 24 Oct 2002, Andrew Arensburger wrote:
On Wed, Oct 23, 2002 at 10:41:34AM -0700, Tonnesen Steve wrote:
I fixed the branches.pl problem so that new branches get the 'IS' and 'CU' branchrelations automatically so that they show up in the circulation module.
What are "IS" and "CU", anyway? For that matter, could you please explain what branchrelations are?
Branches that don't have the 'IS' branchrelation can't issue books (ie they don't show up in the "Select a Branch" area of circulation.
Branches that don't have the 'CU' branchrelation set don't show up in the "To Branch" part of the branchtransfers page.
All of this was made necessary because HLT is using the branch field for things that aren't really branches, namely collections of books either within or branch or that are spread across branches, so that different circulation rules have to be applied to different branches. My proposal was that this be handled through the use of virtual bookshelves to handle collection management (among other things).
Steve.
Hi Steve and Andrew, This is all my fault! I added the "branchcategories" and "branchrelations" tables when I was working on the circulations code. I think this should all be reoganised. However Steve does seem to have fixed up the Installer so that it works out of the box. Perhaps the new Shelf.pm code is the answer.... Finlay
Tonnesen Steve wrote:
On Thu, 24 Oct 2002, Andrew Arensburger wrote:
On Wed, Oct 23, 2002 at 10:41:34AM -0700, Tonnesen Steve wrote:
I fixed the branches.pl problem so that new branches get the 'IS' and 'CU' branchrelations automatically so that they show up in the circulation module.
What are "IS" and "CU", anyway? For that matter, could you please explain what branchrelations are?
Branches that don't have the 'IS' branchrelation can't issue books (ie they don't show up in the "Select a Branch" area of circulation.
Branches that don't have the 'CU' branchrelation set don't show up in the "To Branch" part of the branchtransfers page.
All of this was made necessary because HLT is using the branch field for things that aren't really branches, namely collections of books either within or branch or that are spread across branches, so that different circulation rules have to be applied to different branches. My proposal was that this be handled through the use of virtual bookshelves to handle collection management (among other things).
Steve.
Hi Steve and Andrew, This is all my fault! I added the "branchcategories" and "branchrelations" tables when I was working on the circulations code. I think this should all be reoganised. However Steve does seem to have fixed up the Installer so that it works out of the box. Perhaps the new Shelf.pm code is the answer.... Finlay
participants (4)
-
Andrew Arensburger -
Finlay Thompson -
Pat Eyler -
Tonnesen Steve