- Koha - lists.katipo.co.nz

Re: [Koha] Web-based circulation interface
by kaye.guidetti＠wesley.com.au 23 Jan '01

23 Jan '01

I don't see any problem with just having a link to another page which displays the overdues - many library software programs handle it this way. Would also like to see a flag if there is a reserved book waiting for the borrower to collect. I can't tell you how many times a borrower has borrowed his books and walked out only to have another staff member come over and say - did Mr so and so collect the book that was waiting for him? Borrower has holds / Borrower has books to collect / or something similar?? Sirsi Unicorn software just flags accounts (money owing). If there is money owing for an overdue fine you get caught, if there is money owing for a lost book you get caught, if there is money owing because you have to pay a reservation fee on a book that is now available to collect you get caught, but you get the book too. Chris Cormack <chris(a)katipo.co.nz>@lists.katipo.co.nz on 23/01/2001 23:31:17 Sent by: koha-admin(a)lists.katipo.co.nz To: Tonnesen Steve <tonnesen(a)cmsd.bc.ca> cc: koha(a)lists.katipo.co.nz Fax to: Subject: Re: [Koha] Web-based circulation interface * Tonnesen Steve <tonnesen(a)cmsd.bc.ca> [010123 13:14]: > > On Tue, 23 Jan 2001, Chris Cormack wrote: > > > > Is the code up in cvs on sourceforge? > > It is now. I've also fixed a bug with issuing reserved books that was > pointed out by Kaye Guidetti. Another feature that is missing is the > flags information. Although my patron information shows NOTES and ODUES > flags, there is currently now way to see the information. I'm thinking of > just including the flag information at the bottom of the issues page, to > save having to reload another page for each flag that comes up. > That sounds like a good idea. We have more screen real estate with a web browser than we do with a curses screen, so no real reason to have to click through to another page. What do the librarians think? Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris(a)katipo.co.nz www.katipo.co.nz _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha =========================================== This email message has been swept by MIMESweeper for The Wesley Group of Hospitals- Australia Although this email has been scanned for any known virus, please ensure that due care is taken and correct virus management procedures are maintained. If you have any questions contact the Help Desk on x7029 or via email at help(a)wesley.com.au =========================================== ===================================================================== This e-mail is intended solely for the addressee named above, and may contain confidential or legally privileged information. The copying, distribution or use of this document or any of the information contained in this document, by persons other than the addressee, is expressly prohibited. If you have received this document in error, please notify the sender or info(a)wesley.com.au, and then delete this document. Unless stated otherwise, this e-mail represents only the views of the sender and not the views of the Wesley Group of Hospitals. Tel: (61) 7 3232 7000 Fax: (61) 7 3371 6834 E-mail: info(a)wesley.com.au Web: http://www.wesley.com.au ============================================================

1 0

Web-based circulation interface
by Tonnesen Steve 23 Jan '01

23 Jan '01

I've started playing around with a web-based circulation interface. I have a basic issues module completed (no returns yet). If anybody wants to take a look at it, browse to: http://koha.cmsd.bc.ca/cgi-bin/koha/circ/circulation.pl Use me as the borrower (just type ton, and then select Steve Tonnesen). There are exactly 17 items in my sample database there, barcodes 1000-1016. Let me know what you think. Steve.

2 3

Web interface for circulation
by megan 19 Jan '01

19 Jan '01

One other thing as well. I am just wondering if anyone out there is working on a web interface for circulation. Because I am setting this up for a small community library (run out of a couple of community spaces) - It is not neccessary to have the speed associated with a telnet or ssh interface.... and in fact is much easier for folks to deal with a web interface then telnet.... I was gonna ask around locally to see if anyone would help me work on that - but I was just wondering if anyone on this list was already working on it? megan ************************************************************************* cel - (604) 782-1742 http://megan.tao.ca haven't heard of the flying folk army? http://flyingfolk.ca

2 1

adding library branches
by megan 18 Jan '01

18 Jan '01

hello: I'm not sure if this is where I should ask - but.... I cannot figure out how to alter the perl scripts (or all the perl scripts that need to be altered) to add branches to my library set up. Is there someone on this list who would be willing to walk me through this process? I am not really a wizard at perl - and I'm having trouble figuring out how to and which code needs to be modified. Thanks for any and all help Megan ************************************************************************* cel - (604) 782-1742 http://megan.tao.ca haven't heard of the flying folk army? http://flyingfolk.ca

1 0

API for circulation modules
by Tonnesen Steve 17 Jan '01

17 Jan '01

I've added my API for circulation modules to the cvs repository (C4/Circulation/Circ2.pm), as well as my latest tk circulation interface (/tkperl/tkcirc) which depends on Circ2.pm. Some things I know I'm still missing: Branch and printer selection I don't create a database handle in the circulation code itself. This means that the subroutines in Circ2.pm must open and close a database handle with each call. I don't know if this delay hurts overly much, but it's there. I've been thinking that I should create the the database handle in the circulation code and pass it to the subroutines. If the database handle isn't defined, the subroutines can always create their own as a fallback. My understanding of the accounting system underlying Koha is scratchy at best. I just copied the accounting code from the existing interface... Still missing payment option in the interface (and the API, for that matter). Steve

2 1

Fixes for NewBiblio and Acquire
by glen_stewart＠associate.com 15 Jan '01

15 Jan '01

Hi all, I'm sending Chris new versions of newbiblio.pl and acquire.pl that may benefit many of you. I suspect he'll put them in the usual place for download. They are pul-n-play with the existing 1.07 release. Here are the reasons/benefits: 1. When creating a new book order (newbiblio.pl), the Format link provides a fixed Javascript list that doesn't draw from the ItemTypes and descriptions in the database. This will be a problem for most adopters of Koha outside it's home site. I've added a routine to extract this info from the database and let the librarian quickly choose it from a pull-down menu. 2. Also in newbiblio.pl, the entry form asks for the Item Barcode. However, this info never gets put in the database! It's not assigned until the item is actually received. In case someone wants to know what the barcode for the new item MIGHT be, I've added code to list the next available barcode number in this field. Hey, if you're gonna waste your typing, you might as well have the computer waste it for ya (-; 3. In the Acquire form (when receiving an ordered item), acquire.pl had the same problem with the fixed Format link. Like #1 above, this is now listed from the database, but the Format selected when the order was placed is SELECTED as the default. 4. Item barcode is filled in automatically in the Acquire (check-in) form, and code supports entry into the database this time! <grin> The barcode number presented is the largest barcode number in the "items" table, +1. This assumes everyone is using all numeric barcodes (we do - do you?). Hope this meets the needs of most folks. Glen

2 1

Re: API for circulation interfaces
by glen_stewart＠associate.com 12 Jan '01

12 Jan '01

Steve, You mentioned "In tk-perl, I like displaying item information in a table format" and this got me worrying that you might plan to not use the web interface for circulation functions. At my company's library, the web is the common denominator among operating systems, so if Koha tools aren't web-based, our librarians can't use them. Just a plea to stick with the web so we can all benefit from each other's work, but if your business needs drive you to another interface, it's understandable. Thanks!

2 1

(no subject)
by Anita Pope 12 Jan '01

12 Jan '01

please remove me from your mailing list for KOHA Regards, Anita Pope Library Manager Australian Institute of Management - Qld & NT cnr Boundary and Rosa Streets Spring Hill 4000 PO Box 200 Spring Hill 4004 Phone (07) 3832 0151 or 16 13 48 Fax (07) 3832 0339 Email library(a)aimqld.com.au Web www.aimqld.com.au

1 0

API for circulation interfaces
by Tonnesen Steve 11 Jan '01

11 Jan '01

Here is a proposed list of functions necessary to generate arbitrary circulation interfaces. Comments requested. Is this an appropriate forum for programming discussion? Program API for circulation interfaces: ==================== getpatroninformation ==================== Subroutine returns a hash reference with all patron information. Can be called with either borrowernumber or cardnumber. ($env, $patroninformation) = getpatroninformation($env,$borrowernumber,$cardnumber) ============= currentissues ============= Returns a hash reference (itemnumber => duedate) ($env, $currentissues) = currentissues($env, $borrowernumber); ================== getiteminformation ================== Subroutine returns a hash reference with all item information. Can be called with either itemnumber or barcode. ($env, $iteminformation) = getiteminformation($env,$itemnumber,$barcode) ============ findborrower ============ Subroutine returns an array reference containing a list of borrowernumbers that match $key. $key could be a cardnumber or a partial last name. ($env, $borrowernumber) = findborrower($env, $key) ========= issuebook ========= This subroutine may or may not generate additional questions that must be answered. ($env, $itemnumber, $rejected, $question, $questionnumber, $defaultanswer, $responses) = issuebook($env,$borrowernumber,$barcode) Subroutine must handle errors, some that block issuing, some that must be approved before issuing. If $rejected is not null, it will contain a message detailing the reason for rejection. Possible responses are listed below, prepended with 'Error:'. Alternatively, $rejected may just be '-1' in which case the issue should be rejected with no message displayed to the user. This might happen if the answer to a question resulted in a rejection. Error: Invalid barcode _____ Error: Invalid borrowernumber ____ Error: Item is restricted [$item->{'notforloan'}==1] Error: Item withdrawn [$item->{'withdrawn'}==1] Error: Restricted Item (and borrower not allowed to check out) [$item->{'restricted'}==1] Error: Reference item not for loan [$item->{'itemtype'} eq 'REF'] [Circulation::Renewals::renewstatus] Error: Issued to this patron, no renewals. If $question is not null, it will contain a YesNo question that should be asked. $defaultanswer will contain 'Y' or 'N'. $questionnumber will contain a unique integer for each question that might be asked. Interface code will generate a hash reference ($responses) with the responsees to each question asked and then recall issuebook() until the issue is accepted or rejected. Question: Already issued to this patron and reserved to ___, renew? default N Question: Already issued to this patron, renew? [$newdate=C4::Circulation::Renewals::renewbook()] Question: Already issued to patron ___, mark as returned? [returnrecord()] calculate any charges [calc_charges()] and [createcharge()] ========== returnbook ========== Subroutine for returning a book. $message may contain an arbitrary message to display to the user (maybe should be an array reference for multiple messages?). ($env, $itemnumber, $borrowernumber, $message, $overduefees) = returnbook($env,$barcode) Message: Reserved for collection at branch _______ Calculate any overdue fees (not in current Circulation code) [UpdateStats]

3 4

Classification field
by Tonnesen Steve 04 Jan '01

04 Jan '01

Happy New Year! Has the classification field in the biblioitems table been replaced by the itemtype field? The entries in the two seem sort of similar in the demo data, except that the classification field isn't very uniform: Where classification is one of (Picturbook, Picture Book, Picture Books, PictureBiook, PictureBook, PictureBooks, Picture_book, Pitcurebook, PitureBook), the itemtype field is always JPC (Junior Picture Book). While on the subject. Are these itemtype classifications part of some library standard, or are they Horowhenua-specific groupings? I found that a lot of things were broken until I created some entries in the itemtype table. Steve Tonnesen (in balmy, melting, Northern British Columbia, Canada).

2 1