Restrictions on 9XX Fields

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Restrictions on 9XX Fields

Charles Kelley
Hi, all!

    I'd like to thank everyone for the help I have received in the past.

    My library would like to begin tracking changes we make to the catalog
records. I already know Koha does keep track of changes, for when I click
on "Modification Logs", I see a rich history.

    What I had in mind was something that we did in another library job of
mine: rededicated a 9XX field to log a brief synopsis of the changes we
made. Mostly just the cataloger's name or initials, timestamp, and a few
words, e.g.,

949  \\ $a Kelley, Charles. $b 2020-02-28 $c Added subject field. $c
Romanized Cyrillic title.
949  \\ $a Sloshkin, Victoria. $b 2020-02-29 $c Added editor [700]. $c
Added series title.
949 \\ $a Watanabe, Junko. $b 2020-02-30 $c Fixed title indicators.
949 \\ $a Watanabe, Junko. $b 2020-02-31 $c OK.

    Nothing more involved or detailed than the illustrations. If we really
need the detail, we'll look at the modification logs.

    I know the 9XX fields are locally defined, but as far as I can
determine, Koha uses the 942, 952, and 999 fields and they are to be
avoided. Are there other 9XX fields that we ought to avoid? I have added to
the avoidance list the CANMARC fields and the other fields in the Koha
default framework.

    I understand I'll have to add the brief change log field (949 in my
examples)and its subfields to the frameworks.

    Many thanks for your help.

--
    -- Charles.

    Charles Kelley, MLS
    PSC 704 Box 1029
    APO AP 96338

    Charles Kelley
    5-2 Tsukimino 1-Chome #210
    Yamato-shi, Kanagawa-ken
    〒242-0002 JAPAN

    +1-301-741-7122 [US cell]
    +81-80-4714-5490 [JPN cell]

    [hidden email] [h]
    [hidden email] [p]

    linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls>
    Meeting Your Information Needs. Virtually.
_______________________________________________

Koha mailing list  http://koha-community.org
[hidden email]
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Restrictions on 9XX Fields

Caroline Cyr-La-Rose
Hi Charles,

As far as I know, Koha only uses those three MARC fields (942, 952 and 999).

Also, have you looked at the following system preferences
MarcFieldForCreatorId, MarcFieldForCreatorName, MarcFieldForModifierId
and MarcFieldForModifierName? You can enter your local 9XX fields in there.

Best,

Caroline

On 20-03-01 22 h 29, Charles Kelley wrote:

> Hi, all!
>
>      I'd like to thank everyone for the help I have received in the past.
>
>      My library would like to begin tracking changes we make to the catalog
> records. I already know Koha does keep track of changes, for when I click
> on "Modification Logs", I see a rich history.
>
>      What I had in mind was something that we did in another library job of
> mine: rededicated a 9XX field to log a brief synopsis of the changes we
> made. Mostly just the cataloger's name or initials, timestamp, and a few
> words, e.g.,
>
> 949  \\ $a Kelley, Charles. $b 2020-02-28 $c Added subject field. $c
> Romanized Cyrillic title.
> 949  \\ $a Sloshkin, Victoria. $b 2020-02-29 $c Added editor [700]. $c
> Added series title.
> 949 \\ $a Watanabe, Junko. $b 2020-02-30 $c Fixed title indicators.
> 949 \\ $a Watanabe, Junko. $b 2020-02-31 $c OK.
>
>      Nothing more involved or detailed than the illustrations. If we really
> need the detail, we'll look at the modification logs.
>
>      I know the 9XX fields are locally defined, but as far as I can
> determine, Koha uses the 942, 952, and 999 fields and they are to be
> avoided. Are there other 9XX fields that we ought to avoid? I have added to
> the avoidance list the CANMARC fields and the other fields in the Koha
> default framework.
>
>      I understand I'll have to add the brief change log field (949 in my
> examples)and its subfields to the frameworks.
>
>      Many thanks for your help.
>

--
Caroline Cyr La Rose, M.S.I.
Bibliothécaire | Responsable de produit

Tél. : 1-833-465-4276, poste 221
[hidden email] <mailto:[hidden email]>

INLiBRO | Spécialistes en technologies documentaires | www.inLibro.com
<http://www.inLibro.com>
_______________________________________________

Koha mailing list  http://koha-community.org
[hidden email]
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Restrictions on 9XX Fields

Charles Kelley
In reply to this post by Charles Kelley
Hi, Caroline

    This is good to hear. Thanks for the confirmation, and the suggestion
of the additional MARC tag fields. They may be a better solution.

    In our latest exchange, on 2 Mch. 2020, at 11:21, Caroline Cyr-La-Rose
wrote:

> As far as I know, Koha only uses those three MARC fields (942, 952 and
999).
>
> Also, have you looked at the following system preferences
MarcFieldForCreatorId, MarcFieldForCreatorName, MarcFieldForModifierId and
MarcFieldForModifierName? You can enter your local 9XX fields in there.

    Quoting my question of 2 Mch. 2020, 12:29, to wit:

>    My library would like to begin tracking changes we make to the catalog
records. I already know Koha does keep track of changes, for when I click
on "Modification Logs", I see a rich history.
>
>    What I had in mind was something that we did in another library job of
mine: rededicated a 9XX field to log a brief synopsis of the changes we
made. Mostly just the cataloger's name or initials, timestamp, and a few
words, e.g.,

> 949  \\ $a Kelley, Charles. $b 2020-02-28 $c Added subject field. $c
Romanized Cyrillic title.
> 949  \\ $a Sloshkin, Victoria. $b 2020-02-29 $c Added editor [700]. $c
Added series title.
> 949  \\ $a Watanabe, Junko. $b 2020-02-30 $c Fixed title indicators.
> 949  \\ $a Watanabe, Junko. $b 2020-02-31 $c OK.

--
Caroline Cyr La Rose, M.S.I.
Bibliothécaire | Responsable de produit

Tél. : 1-833-465-4276, poste 221
[hidden email] <mailto:[hidden email]>

INLiBRO | Spécialistes en technologies documentaires | www.inLibro.com <
http://www.inLibro.com>

--
    -- Charles.

    Charles Kelley, MLS
    PSC 704 Box 1029
    APO AP 96338

    Charles Kelley
    5-2 Tsukimino 1-Chome #210
    Yamato-shi, Kanagawa-ken
    〒242-0002 JAPAN

    +1-301-741-7122 [US cell]
    +81-80-4714-5490 [JPN cell]

    [hidden email] [h]
    [hidden email] [p]

    linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls>
    Meeting Your Information Needs. Virtually.
_______________________________________________

Koha mailing list  http://koha-community.org
[hidden email]
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Restrictions on 9XX Fields

Katrin Fischer-2
In reply to this post by Charles Kelley
Hi Charles,

just something to keep in mind: the keyword index in Koha searches the
whole record. So if you use full names like in your example below,
searching for an author Charles, would also turn up the records edited
by you. It might make sense to work with codes or abbreviations.

Katrin

On 02.03.20 04:29, Charles Kelley wrote:

> Hi, all!
>
>      I'd like to thank everyone for the help I have received in the past.
>
>      My library would like to begin tracking changes we make to the catalog
> records. I already know Koha does keep track of changes, for when I click
> on "Modification Logs", I see a rich history.
>
>      What I had in mind was something that we did in another library job of
> mine: rededicated a 9XX field to log a brief synopsis of the changes we
> made. Mostly just the cataloger's name or initials, timestamp, and a few
> words, e.g.,
>
> 949  \\ $a Kelley, Charles. $b 2020-02-28 $c Added subject field. $c
> Romanized Cyrillic title.
> 949  \\ $a Sloshkin, Victoria. $b 2020-02-29 $c Added editor [700]. $c
> Added series title.
> 949 \\ $a Watanabe, Junko. $b 2020-02-30 $c Fixed title indicators.
> 949 \\ $a Watanabe, Junko. $b 2020-02-31 $c OK.
>
>      Nothing more involved or detailed than the illustrations. If we really
> need the detail, we'll look at the modification logs.
>
>      I know the 9XX fields are locally defined, but as far as I can
> determine, Koha uses the 942, 952, and 999 fields and they are to be
> avoided. Are there other 9XX fields that we ought to avoid? I have added to
> the avoidance list the CANMARC fields and the other fields in the Koha
> default framework.
>
>      I understand I'll have to add the brief change log field (949 in my
> examples)and its subfields to the frameworks.
>
>      Many thanks for your help.
>
_______________________________________________

Koha mailing list  http://koha-community.org
[hidden email]
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha