[Wactclc-alma] Help with normalization rule

Fri Jun 14 11:27:35 PDT 2019

Hi Heather,

That is interesting, because the rule I use in my import profile to remove subject headings we don't want uses 6**, several times:

  removeField "6**" if(exists "6**.{*,3}")
  removeField "6**" if(exists "6**.{*,4}")
  removeField "6**" if(exists "6**.{*,5}")
  removeField "6**" if(exists "6**.{*,6}")
  removeField "6**" if(exists "6**.{*,7}")

And when I tested using "removeField "650" if (exists "650.z.United States")", it stopped working if I put United States in parentheses - but yours works with parentheses in the rule even if they aren't in the MARC field?

It'd be nice to have hard and fast rules we can rely on, but I'm glad you got yours working, anyway!

Hannah Micona

Cataloger, Holman Library

Green River College

(253) 833-9111 ex. 2098

________________________________
From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu> on behalf of Heather Jean Uhl <huhl at everettcc.edu>
Sent: Friday, June 14, 2019 11:12:40 AM
To: WACTCLC Alma Discussion
Subject: Re: [Wactclc-alma] Help with normalization rule

CAUTION: This email originated from outside of Green River College. Please do not click any links or open attachments unless you know the sender and know the information is safe. Even if you know the sender, if the request or information seems unusual please check with the sender first before clicking a link or opening the attachment. If you are unsure, contact the IT Help Desk at x2222 or email ithelpdesk at greenriver.edu<mailto:ithelpdesk at greenriver.edu>.

Please do not give out or enter your Green River email, network login, password information on non-Green River websites.

Hi, Hannah.

It turns out the trouble was truncating the 6XX fields.  The rule works when I used an exact list of all possible fields (650, 651, 655, etc.) rather than trying to truncate to cover all of them (6**).  Interesting, yes?  A big thank you to Patt from Arizona State for chiming in with their rule.

Thanks very much for your thoughts and for extending the conversation to the quirks between subfields that work and don't work with rules.  I'm not sure what to make of those inconsistencies.  I'm very, very new to Normalization Rules, so I look forward to learning more from you and our community.

Heather Jean Uhl, Faculty Librarian (pronouns: she / her)
Acquisitions & Cataloging Department Supervisor
Everett Community College - Library Media Center
huhl at everettcc.edu<mailto:huhl at everettcc.edu> | (425)388-9139

Library Liaison for English, Journalism, Communications, Theater
Japanese Culture Club Adviser

On Fri, Jun 14, 2019 at 9:00 AM Hannah Micona <HMicona at greenriver.edu<mailto:HMicona at greenriver.edu>> wrote:

Hi Heather,

I strip these out on import, so I can't test your exact rule myself, but from just looking at it, do your subfield 2s say "fast" or do they say "(fast)"? The couple of records with FAST headings I looked at in OCLC don't have parentheses, and having them in the rule will cause it not to match.

If nobody minds me adding to the pile...While trying to test simply the syntax (I think that's the term?) of Heather's rule, on other subfields, I ran into the following: For Clinton's book Living History, which has a 650 of "$$a Women legislators $$z United States $$v Biography", the following rule, using "when TRUE", works fine:

removeField "650" if (exists "650.z.United States")

but if I simply change the z to a v and the United States to Biography, like so:

removeField "650" if (exists "650.v.Biography")

it won't remove it. Has anyone else run into something like this, or know why it might have broken?

Thanks,

Hannah Micona

Cataloger, Holman Library

Green River College

(253) 833-9111 ex. 2098

________________________________
From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu<mailto:wactclc-alma-bounces at lists.ctc.edu>> on behalf of Heather Jean Uhl <huhl at everettcc.edu<mailto:huhl at everettcc.edu>>
Sent: Thursday, June 13, 2019 4:23:56 PM
To: WACTCLC Alma Discussion
Subject: Re: [Wactclc-alma] Help with normalization rule

CAUTION: This email originated from outside of Green River College. Please do not click any links or open attachments unless you know the sender and know the information is safe. Even if you know the sender, if the request or information seems unusual please check with the sender first before clicking a link or opening the attachment. If you are unsure, contact the IT Help Desk at x2222 or email ithelpdesk at greenriver.edu<mailto:ithelpdesk at greenriver.edu>.

Please do not give out or enter your Green River email, network login, password information on non-Green River websites.

Hi, Normalization Rule Friends.

I'm struggling with a similar bit of trouble.  I want to create a normalization rule that will delete any 6XX field that is a FAST heading.  These fields will always have subfield 2 with the value "fast."  I can get the rule to work for any 6XX field that has a second indicator 7, but I don't want to lose local fields and second indicator 7 subject fields that include valid lcgft headings.

Below is my rule.  What am I missing?  Thank you so much for your eyes and expertise.... >_<*

rule "delete FAST 6XX fields"
when
exists "6**.2.(FAST*)"
  (TRUE)
then
  removeField "6**" if (exists "6**.2.(FAST*)")
end

Heather Jean Uhl, Faculty Librarian (she / her pronouns)
Acquisitions & Cataloging Department Supervisor
Everett Community College - Library Media Center
huhl at everettcc.edu<mailto:huhl at everettcc.edu> | (425)388-9139

Library Liaison for English, Journalism, Communications, Theater
Japanese Culture Club Adviser
Japanese Anime & Manga Arts Festival Chair
Instructor ART228D The World of Anime & Manga

On Thu, May 23, 2019 at 8:39 AM Elena Bianco <Elena.Bianco at skagit.edu<mailto:Elena.Bianco at skagit.edu>> wrote:

Hi Hannah:

Amazing! It worked when I used the asterisk in both. Thank you!!

Elena

Elena Bianco

Systems & Technical Services Librarian

Skagit Valley College Library

2405 E. College Way

Mount Vernon, WA 98273

(360) 416-7624

________________________________
From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu<mailto:wactclc-alma-bounces at lists.ctc.edu>> on behalf of Hannah Micona <HMicona at greenriver.edu<mailto:HMicona at greenriver.edu>>
Sent: Thursday, May 23, 2019 7:53 AM
To: WACTCLC Alma Discussion
Subject: Re: [Wactclc-alma] Help with normalization rule

Elena,

If your 035 looks like I think it does, you're asking it to remove the 035 only if the field text is exactly "(WaMtvS)" when what you want is for it to remove the 035 if the field text STARTS with "(WaMtvS)". Try putting an asterisk after both instances of (WaMtvS) in your code. (Actually I think you don't need the first one, I think that can just be 'when TRUE,' but I don't think it matters one way or the other.)

Hannah Micona

Cataloger, Holman Library

Green River College

(253) 833-9111 ex. 2098

________________________________
From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu<mailto:wactclc-alma-bounces at lists.ctc.edu>> on behalf of Elena Bianco <Elena.Bianco at skagit.edu<mailto:Elena.Bianco at skagit.edu>>
Sent: Wednesday, May 22, 2019 5:14:49 PM
To: WACTCLC Alma Discussion
Subject: [Wactclc-alma] Help with normalization rule

CAUTION: This email originated from outside of Green River College. Please do not click any links or open attachments unless you know the sender and know the information is safe. Even if you know the sender, if the request or information seems unusual please check with the sender first before clicking a link or opening the attachment. If you are unsure, contact the IT Help Desk at x2222 or email ithelpdesk at greenriver.edu<mailto:ithelpdesk at greenriver.edu>.

Please do not give out or enter your Green River email, network login, password information on non-Green River websites.

So, I am trying to eliminate our old Millennium bib numbers that got moved to the 035 field during migration. I came up with this normalization rule:

rule "replace -element- with  -text-"

#where -element- is:

#035.a.(WaMtvS)

    when

        TRUE

    then

        removeField "035"

end

It works, but the problem is, it deletes all the 035’s, including the one that has the OCLC number that I want to retain.

Then I tried this:

rule "035 (WaMtvS)"

when

exists "035.a.(WaMtvS)"

then

removeField "035" if (exists "035.a.(WaMtvS)")

end

That did nothing.

How can I tell it to ONLY remove the 035 that has this element? Help!

Thanks,

Elena

Elena Bianco, Systems & Technical Services Librarian

Skagit Valley College

2405 E. College Way

Mount Vernon, WA 98273

(360)416-7624

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20190614/9c1d3ad6/attachment-0002.html>