koha-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Koha-devel] some more thoughts on marc linkage of call number...


From: paul POULAIN
Subject: Re: [Koha-devel] some more thoughts on marc linkage of call number...
Date: Mon Dec 9 09:43:01 2002
User-agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.1) Gecko/20020826

Ambrose Li [CCCGT] a écrit:

Hi,

I am thinking of the "093" field we use here. It has the following
structure (as far as I understand):

  a LC classification number
  c Cutter number
  y Year of publication
    - can be null (if a+c already uniquely identifies a book)
    - if not null, can be followed by a letter (a, b, c, etc.)
      if a+c+year cannot uniquely identify a book
  v Volume number (V.1, V.2, etc.) or other things like INDEXES,
    MANUAL, etc.

What if there is a feature where we can map more than one subfield
(e.g., c+y+v here) to one Koha field (e.g., biblioitems.subclass)?
Would this make any sense?

it makes sense if you plan to use marc and non marc db back-end.
if you plan to use only marc, i think you can avoid a link.
if you really want to link, maybe *classification* is what you're looking for, but katipans should know better. Anyway, subclass is only char(3), so, a little bit too short.

--
Paul POULAIN
Consultant indépendant en logiciels libres
responsable francophone de koha (SIBGB libre http://fr.koha.org)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]