Re: [Koha] Restrictions on 9XX Fields

[Katrin Fischer]

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
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Restrictions on 9XX Fields

[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
caroline.cyr-la-r...@inlibro.com 

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]

mnogoja...@aol.com [h]
cmkelley...@gmail.com [p]

linkedin.com/in/cmkelleymls 
Meeting Your Information Needs. Virtually.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] koha-US March 2020 Meetings & Events

[Jason Robb]

koha-US online meetings and events are free and open to all.

See our calendar for a full list: http://koha-us.org/calendar/

*Meetings*
Board Meeting - Wednesday, March 4th @ 8:30-9:30 PT (9:30 MT / 10:30 CT /
11:30 ET)

   - Meeting Link - https://zoom.us/j/293750042
   - Agenda -
   
https://docs.google.com/document/d/12TKC2nKuasTRC-xFvbYuqgY2arBu90xXOnVMD3V5Xf4/edit?usp=sharing

General Meeting -  Wednesday, March 11th @ 8:30-9:30 PT (9:30 MT / 10:30 CT
/ 11:30 ET)

*Learning Opportunities*
Basic SQL for Koha Users - Tuesday, March 24th @ 8:30-9:30 PT (9:30 MT /
10:30 CT / 11:30 ET)

*Special Interest Groups*
Cataloging - Thursday, March 5th @ 8-9 PT (9 MT / 10 CT / 11 ET)
System Administration - Tuesday, March 10th @ 9-10 PT (10 MT / 11 CT / Noon
ET)
Acquisitions - Tuesday, March 17th @ 9-10 PT (10 MT / 11 CT / Noon ET)

See what other SIGs are in the works and join groups on topics important to
you: http://koha-us.org/special-interest-groups/

For example, do you wish certain Koha functionality was more streamlined?
Do you have strong opinions about how Koha looks and feels? Consider
joining the *Web Development SIG
* to chat
about Koha user experience and interface design, customization, and more.

Jason Robb
koha-US secretary
secret...@koha-us.org
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] 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
caroline.cyr-la-r...@inlibro.com 

INLiBRO | Spécialistes en technologies documentaires | www.inLibro.com 


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Saying farewell to QueryParser

[Renvoize, Martin]

Hi All,

As discussed at the development meeting on the 19th February

we have decided to remove the QueryParser option and code from Koha.

This decision was not taken lightly, but with the move towards
Elasticsearch and the lack of follow-through support for continued bug
fixing and improvements in the QueryParser code we decided to reduce out
maintenance debt and remove it.  We used HEA to try to ascertain if anyone
had been using the option and it appears to have little to zero adoption
(and at the time of writing, had a number of bad bugs which meant using it
was advised against for some time).

Jonathan D has worked hard to produce a patch quickly to do this work and I
intend to push this later today to reduce the risk of repetitive rebase
requirements.

So, join me in saying farewell to QueryParser, a nice idea never fully
realised.

Many thanks as ever to the koha development team,

*Martin Renvoize*



Development Team Manager

Community Release Manager (19.11, 20.05)


*Phone:* +44 (0) 1483 378728

*Mobile:* +44 (0) 7725 985 636

*Email:* martin.renvo...@ptfs-europe.com

*Fax:* +44 (0) 800 756 6384


www.ptfs-europe.com







Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30

The information contained in this email message may be privileged,
confidential and protected from disclosure. If you are not the intended
recipient, any dissemination, distribution or copying is strictly
prohibited. If you think that you have received this email message in
error, please email the sender at i...@ptfs-europe.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha