[Koha-devel] items.ccode or items.itype ?

[Ryan Higgins]

Yes, sorry for the flip-flop.  I had seen that `itype` was removed from
items table in
updatedatabase, so reinterpreted 'ccode' as 'circ code'.  As it turns out,
we really need
to have two means of classification at the item level, and itype was still
defined in the framework.
So items.itype is intended to be mapped to itemtypes.
biblioitems.itemtype still exists, because completely moving itemtype
to the item level seemed to likely to introduce bugs.   With the system
preference
'item-level_itypes' ON, biblioitems.itemtype has a couple of display
functions, and should
be set.  A plugin should populate items.itype from biblioitems.itemtype,
giving a 'default'
value.

items.ccode is intended as 'Collection Code', linked to an
authorised_value.

Ryan Higgins
LibLime

On 11/12/07, Paul POULAIN < paul.poulain at free.fr> wrote:
>
> Hello world (and mainly liblimers)
>
> kados told me on the chat last week that the item-level circulation
> stuff relied on items.ccode field.
>
> I see this morning commits from Ryan, that speak of "further mods to
> change from ccode to itype at item-level itypes"
>
> Does it mean ccode won't be used anymore and the field name is in fact
> items.itype ?
>
> Is there something i've missed here ?
>
> --
> Paul POULAIN
> BibLibre SARL
> Expert en Logiciels Libres pour l'info-doc
> Tel : 04 91 31 45 19
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/koha-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20071114/ff1181ef/attachment-0002.htm>