Thanks, all, for your very useful replies. I don't know anything about the SIP2 interface, but I'm going to find out now. Thanks for the pointer. Galen, Just to verify, I can call the itemnumber variable with: <!-- TMPL_VAR NAME="itemnumber" --> right? It seems like these variables usually use the MySQL field name, which is very logical. Is that a good rule of thumb to follow when determining if a variable is available to a template? Any idea where these variables are defined? I have fundamental programming knowledge, but don't know much about perl. Thanks for answering the novice questions. Cheers, Christopher Curry Assistant Technical Librarian / Assistant IT Officer American Philosophical Society 105 South Fifth Street Philadelphia, PA 19106-3386 Tel. (215) 599-4299 ccurry@amphilsoc.org <mailto:ccurry@amphilsoc.org> *For technical support, please use helpdesk@amphilsoc.org <mailto:helpdesk@amphilsoc.org>* Main Library number: (215)440-3400 APS website: http://www.amphilsoc.org Zeno Tajoli wrote:
Dear Christopher,
At 22.06 17/02/2010, Christopher Curry wrote:
Since we're not using Koha's circulation system, we'll need to link Aeon and Koha so that an item checkout from Aeon sends a database UPDATE call to Koha and updates items.onloan with the desired due date (or at least, that's what I've been able to sort out by poking around).
First, am I correct that updating the availability status of an item in the Koha Opac requires only that we update this field (items.onloan)?
if you need to operate at SQL level, you can read the SQL documentation here: http://wiki.koha.org/doku.php?id=en:development:dbschema
Bye Zeno Tajoli
Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)