some informations on item status
Hello, Following some IRC chat & joshua commits, here are some explanations about item status : "item status" covers 2 things : - what is automatically set - what is manually set what is automatically set => the position of the book regarding issuing. It means wether the book is on issue, waiting, or "available". There is no field the DB to store this : the issues table is searched everytime it's needed => the "on order" flag, that can be set only when there is no item for a given book, but an order placed on it (remember a book is immediatly created when you place an order, in MARC as well as in non-MARC DB) what is manually set => it's 3 different fields in items table : - notforloan - itemlost - wthdrawn Since Koha 1.x, all those fields have the following meaning : 0 means "no", and 1 means "yes". So notforloan=1 basically means item is not for loan and notforloan=0 means its not not for loan (= can be issued) In Koha 2.0, i've added a feature that works at least for notforloan and MARC=ON : you can define a list of authorized values that are integers and used in the MARC subfield that is mapped to items.notforloan. the rule being : 0 means "no"
1 means "yes".
Thus, you can define why an item is "notforloan". Can be, for example "being repaired", or whatever you want. The consequence is that you can have notforloan meaning : 0 : available 1 : not for loan 2 : lost 3 : withdrawn 4 : being repaired 5 : ... and thus lost & wthdrawn fields are useless for me. HTH -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
Thanks for that explaination Paul. However, unless I'm mistaken, there's still no way to determin 'on the fly' whether an item is reservable or not using this scheme. Do you libraries have some items that are not reservable? If so, how do you determine this in the OPAC? -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS On Tue, Aug 30, 2005 at 04:16:46PM +0200, Paul POULAIN wrote:
Hello,
Following some IRC chat & joshua commits, here are some explanations about item status : "item status" covers 2 things : - what is automatically set - what is manually set
what is automatically set => the position of the book regarding issuing. It means wether the book is on issue, waiting, or "available". There is no field the DB to store this : the issues table is searched everytime it's needed
=> the "on order" flag, that can be set only when there is no item for a given book, but an order placed on it (remember a book is immediatly created when you place an order, in MARC as well as in non-MARC DB)
what is manually set => it's 3 different fields in items table : - notforloan - itemlost - wthdrawn
Since Koha 1.x, all those fields have the following meaning : 0 means "no", and 1 means "yes". So notforloan=1 basically means item is not for loan and notforloan=0 means its not not for loan (= can be issued)
In Koha 2.0, i've added a feature that works at least for notforloan and MARC=ON : you can define a list of authorized values that are integers and used in the MARC subfield that is mapped to items.notforloan. the rule being : 0 means "no"
1 means "yes".
Thus, you can define why an item is "notforloan". Can be, for example "being repaired", or whatever you want.
The consequence is that you can have notforloan meaning : 0 : available 1 : not for loan 2 : lost 3 : withdrawn 4 : being repaired 5 : ...
and thus lost & wthdrawn fields are useless for me.
HTH -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
Joshua Ferraro a écrit :
Thanks for that explaination Paul. However, unless I'm mistaken, there's still no way to determin 'on the fly' whether an item is reservable or not using this scheme. Do you libraries have some items that are not reservable? If so, how do you determine this in the OPAC?
I don't understand well your question. What do you mean by "on the fly" ? (I understand the english word, but not what you mean here) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (2)
-
Joshua Ferraro -
Paul POULAIN