No subject


Thu Nov 17 10:58:26 NZDT 2005


the future if one of the 9xx tags did get taken over eventually (that is =
not supposed to happen but ...).

I think Koha was brilliant for wanting to include more meaningful item =
(format) types. Kudos to whoever thought of that. There may be a more =
permanent and pleasing solution to the problem of moving that info to a =
9xx. Hence the following modest proposal:

     Perhaps for those of you who qualify as real librarians
     (unlike yours truly), one might humbly suggest
     something some my paraprofessional colleagues and I
     have discussed over the years,
     *** a prescribed localised tag for more meaningful
     format types (and/or possibly other information) *** than
     are prescribed by the beloved AACR2R.
     Any suggestion/s would have to be submitted to CPSO
     but perhaps there would be interest enough to have a=20
     tag added.

I realise that one could do this through a note and that, yes, it is =
technically coded in the 007 and 008, but it would be nice to have a =
simpler (if sometimes redundant) and recognisable statement of the =
item's format for patrons (and for us, too). As with 6xx fields, an =
indicator could be used to denote whether the term used was from a =
standardised thesaurus (something that might happen one day), or purely =
of local use.

Just a thought, anyway.

Steven F. Baljkas
library tech at large
Koha neophyte
Winnipeg, MB  CANADA


  ----- Original Message -----=20
  From: COURYHOUSE at aol.com=20
  To: shedges at skemotah.com=20
  Cc: lambert at amigos.org ; koha at lists.katipo.co.nz=20
  Sent: Monday, September 08, 2003 10:29 PM
  Subject: Re: [Koha] 090 Fields


  I guess what we have to analyze ... "is Koha doing something non =
standard that impacts the integrity of the MARC record? "  if so perhaps =
the non standard=20
  information needs to  be at the end of the record past where the MARC =
data is kept? if there is no area present perhaps one needs to  be =
created  as a 'stash'

  Just a thought....

  Ed Sharpe archivist for SMECC



    Subj:Re: [Koha] 090 Fields=20
    Date:9/8/2003 5:24:04 PM US Mountain Standard Time
    From:shedges at skemotah.com
    To:lambert at amigos.org
    CC:koha at lists.katipo.co.nz
    Sent from the Internet=20




    Greg Lambert/Amigos said:
    > As I was reviewing the bulkmarcimport I noticed that the 090 MARC =
field is
    > used by Koha as the ITEMTYPE fields.
    >
    > In the MARC data I am importing, the 090 "a" and "b" subfields are
    > assigned
    > local LC call numbers.
    >
    > Since Koha assigns  "a" as Koha Itemtype (NR)
    >                                          "b" as Koha Dewey =
Subclass (NR)
    >                                          "c" as Koha biblionumber =
(NR)
    >                                          "d" as Koha =
biblioitemnumber (NR)
    >
    > What will happen to my original 090a and 090b fields?  Will they =
still be
    > in the database?  If so, will this cause item "issues"?
    >
    > My limited cataloging knowledge tells me that the 001 field is =
used for
    > the
    > item number information (at least in the colleges I've worked).  =
Is that
    > not the case with MARC21?
    >
    >
    > Thanks!
    > -Greg

    Hmmm.  Do you mean your existing MARC records use an 090 field?  =
Koha has
    to store some important non-MARC information, primarily the =
biblionumber,
    biblioitemnumber and the itemtype, in the MARC record in order to
    interface with the "old" Koha databases.  The 090 tag was chosen =
because
    neither MARC21 nor Unimarc define any use for this tag, so it was
    considered to be "safe."  If you have existing MARC records that =
have data
    in an 090 tag, then you have a problem.  You could move the data to =
a new
    tag using MARC::Record.

    --=20
    Stephen Hedges
    Skemotah Solutions, USA
    www.skemotah.com  --  shedges at skemotah.com
    _______________________________________________
    Koha mailing list
    Koha at lists.katipo.co.nz
    http://lists.katipo.co.nz/mailman/listinfo/koha



  Thanks Ed Sharpe, Archivist for SMECC

  See the Museum's Web Site at

  www.smecc.org

  We are always looking for items to add to the museum's display and =
ref. library
  please advise if you have anything we can use.

  mail:

  Coury House / SMECC
  5802 W. Palmaire Ave.
  Glendale Az 85301  USA

  623-435-1522

  CONFIDENZIALE: Questo messaggio e gli eventuali allegati sono =
confidenziali
  e riservati. Se vi =E8 stato recapitato per errore e non siete fra i
  destinatari elencati, siete pregati di darne immediatamente avviso al
  mittente. Le informazioni contenute non devono essere mostrate ad =
altri, n=E9
  utilizzate, memorizzate o copiate in qualsiasi forma.

  CONFIDENTIAL: This  e-mail  and  any attachments are confidential and =
may
  contain reserved information. If  you are not one of the named =
recipients,
  please notify the sender immediately. Moreover, you should not =
disclose the
  contents to any other persons, nor should the information contained be =
used
  for any purpose or stored or copied in any form.


------=_NextPart_000_002E_01C37671.EBC45340
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1226" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Tuesday, September 9, 2003&nbsp;&nbsp; =
01:15=20
CDT</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Hi, Ed,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I don't think anyone could claim Koha =
is doing=20
something non-standard with its usage of MARC. The decision to use the =
090 in=20
the way that it has, however, was ill-advised given (as I just =
told&nbsp;Greg)=20
the 090 was actually used by LC itself for the call number in the past =
and=20
several systems out there in the market make use of it, causing =
potential=20
migration problems that then get dumped squarely on poor=20
Koha.&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>From what Chris C. and others have said =
since I've=20
been on the list-serv, I gather that the H* (I won't even try to attempt =
the=20
spelling at this late hour) Trust didn't care about MARC and that =
consequently,=20
the developpers might not have appreciated fully how MARC-reliant much =
of the=20
library world is and that there is a whole complicated history behind=20
that.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Anyway, I like your suggestion, =
Ed,&nbsp;about=20
moving the item type to a 9xx field. The developpers could designate one =
of the=20
tags for it and then that would become a Koha feature.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>From the cataloguing side of things, =
this could=20
still get screwed up in the future if one of the 9xx tags did get taken =
over=20
eventually (that is not supposed to happen but ...).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I think Koha was brilliant for wanting =
to include=20
more meaningful item (format) types. Kudos to whoever thought of that.=20
</FONT><FONT face=3DArial size=3D2>There may be a more permanent and =
pleasing=20
solution to the problem of moving that info to a 9xx. Hence the =
following modest=20
proposal:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; </FONT><FONT =
face=3DArial=20
size=3D2>Perhaps for those of you who qualify as real =
librarians</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;(unlike yours =
truly), one=20
might humbly suggest</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;something some =
my=20
paraprofessional&nbsp;</FONT><FONT face=3DArial =
size=3D2>colleagues&nbsp;and=20
I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;have discussed =
over the=20
years,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;*** a=20
prescribed&nbsp;localised tag for more meaningful</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; =
format</FONT><FONT=20
face=3DArial size=3D2>&nbsp;types (and/or possibly other information) =
***=20
than</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; &nbsp;&nbsp; =
are&nbsp;</FONT><FONT=20
face=3DArial size=3D2>prescribed by the beloved AACR2R.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Any =
suggestion/s would=20
have to be submitted to CPSO</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; but perhaps =
there would be=20
interest enough to have a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; tag =
added.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I realise that one could do this =
through a note and=20
that, yes, it is technically coded in the 007 and 008, but it would be =
nice to=20
have a simpler (if sometimes redundant) and recognisable statement of =
the item's=20
format for patrons (and for us, too). As with 6xx fields, an indicator =
could be=20
used to denote whether the term used was from a standardised thesaurus=20
(something that might happen one day), or purely of local =
use.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Just a thought, anyway.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Steven F. Baljkas</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>library tech at large</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Koha neophyte</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Winnipeg, MB&nbsp; CANADA</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">&nbsp;</DIV>
  <DIV style=3D"FONT: 10pt arial">&nbsp;</DIV>
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3DCOURYHOUSE at aol.com=20
  href=3D"mailto:COURYHOUSE at aol.com">COURYHOUSE at aol.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dshedges at skemotah.com=20
  href=3D"mailto:shedges at skemotah.com">shedges at skemotah.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dlambert at amigos.org=20
  href=3D"mailto:lambert at amigos.org">lambert at amigos.org</A> ; <A=20
  title=3Dkoha at lists.katipo.co.nz=20
  href=3D"mailto:koha at lists.katipo.co.nz">koha at lists.katipo.co.nz</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, September 08, =
2003 10:29=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Koha] 090 =
Fields</DIV>
  <DIV><BR></DIV><FONT face=3Darial,helvetica><FONT size=3D2>I guess =
what we have to=20
  analyze ... "is Koha doing something non standard that impacts the =
integrity=20
  of the MARC record? "&nbsp; if so perhaps the non standard =
<BR>information=20
  needs to&nbsp; be at the end of the record past where the MARC data is =
kept?=20
  if there is no area present perhaps one needs to&nbsp; be =
created&nbsp; as a=20
  'stash'<BR><BR>Just a thought....<BR><BR>Ed Sharpe archivist for=20
  SMECC<BR><BR><BR>
  <BLOCKQUOTE=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px"=20
  TYPE=3D"CITE">Subj:<B>Re: [Koha] 090 Fields </B><BR>Date:9/8/2003 =
5:24:04 PM=20
    US Mountain Standard Time<BR>From:<A=20
    =
href=3D"mailto:shedges at skemotah.com">shedges at skemotah.com</A><BR>To:<A=20
    href=3D"mailto:lambert at amigos.org">lambert at amigos.org</A><BR>CC:<A=20
    =
href=3D"mailto:koha at lists.katipo.co.nz">koha at lists.katipo.co.nz</A><BR><I=
>Sent=20
    from the Internet </I><BR><BR><BR><BR><BR>Greg Lambert/Amigos =
said:<BR>&gt;=20
    As I was reviewing the bulkmarcimport I noticed that the 090 MARC =
field=20
    is<BR>&gt; used by Koha as the ITEMTYPE fields.<BR>&gt;<BR>&gt; In =
the MARC=20
    data I am importing, the 090 "a" and "b" subfields are<BR>&gt;=20
    assigned<BR>&gt; local LC call numbers.<BR>&gt;<BR>&gt; Since Koha=20
    assigns&nbsp; "a" as Koha Itemtype=20
    =
(NR)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    "b" as Koha Dewey Subclass=20
    =
(NR)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    "c" as Koha biblionumber=20
    =
(NR)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    "d" as Koha biblioitemnumber (NR)<BR>&gt;<BR>&gt; What will happen =
to my=20
    original 090a and 090b fields?&nbsp; Will they still be<BR>&gt; in =
the=20
    database?&nbsp; If so, will this cause item =
"issues"?<BR>&gt;<BR>&gt; My=20
    limited cataloging knowledge tells me that the 001 field is used =
for<BR>&gt;=20
    the<BR>&gt; item number information (at least in the colleges I've=20
    worked).&nbsp; Is that<BR>&gt; not the case with=20
    MARC21?<BR>&gt;<BR>&gt;<BR>&gt; Thanks!<BR>&gt; =
-Greg<BR><BR>Hmmm.&nbsp; Do=20
    you mean your existing MARC records use an 090 field?&nbsp; Koha =
has<BR>to=20
    store some important non-MARC information, primarily the=20
    biblionumber,<BR>biblioitemnumber and the itemtype, in the MARC =
record in=20
    order to<BR>interface with the "old" Koha databases.&nbsp; The 090 =
tag was=20
    chosen because<BR>neither MARC21 nor Unimarc define any use for this =
tag, so=20
    it was<BR>considered to be "safe."&nbsp; If you have existing MARC =
records=20
    that have data<BR>in an 090 tag, then you have a problem.&nbsp; You =
could=20
    move the data to a new<BR>tag using MARC::Record.<BR><BR>-- =
<BR>Stephen=20
    Hedges<BR>Skemotah Solutions, USA<BR>www.skemotah.com&nbsp; --&nbsp; =

    =
shedges at skemotah.com<BR>_______________________________________________<B=
R>Koha=20
    mailing=20
    =
list<BR>Koha at lists.katipo.co.nz<BR>http://lists.katipo.co.nz/mailman/list=
info/koha</BLOCKQUOTE><BR><BR><BR>Thanks=20
  Ed Sharpe, Archivist for SMECC<BR><BR>See the Museum's Web Site=20
  at<BR><BR>www.smecc.org<BR><BR>We are always looking for items to add =
to the=20
  museum's display and ref. library<BR>please advise if you have =
anything we can=20
  use.<BR><BR>mail:<BR><BR>Coury House / SMECC<BR>5802 W. Palmaire=20
  Ave.<BR>Glendale Az 85301&nbsp; =
USA<BR><BR>623-435-1522<BR><BR>CONFIDENZIALE:=20
  Questo messaggio e gli eventuali allegati sono confidenziali<BR>e =
riservati.=20
  Se vi =E8 stato recapitato per errore e non siete fra i<BR>destinatari =
elencati,=20
  siete pregati di darne immediatamente avviso al<BR>mittente. Le =
informazioni=20
  contenute non devono essere mostrate ad altri, n=E9<BR>utilizzate, =
memorizzate o=20
  copiate in qualsiasi forma.<BR><BR>CONFIDENTIAL: This&nbsp; =
e-mail&nbsp;=20
  and&nbsp; any attachments are confidential and may<BR>contain reserved =

  information. If&nbsp; you are not one of the named =
recipients,<BR>please=20
  notify the sender immediately. Moreover, you should not disclose=20
  the<BR>contents to any other persons, nor should the information =
contained be=20
  used<BR>for any purpose or stored or copied in any=20
form.<BR><BR></BLOCKQUOTE></FONT></FONT></BODY></HTML>

------=_NextPart_000_002E_01C37671.EBC45340--




More information about the Koha mailing list