Alma Q&A and Chat Transcript 10/06/16

Owned by brandon dudley (Unlicensed)
Last updated: Aug 17, 2017 by Mallory DeBartolo (Unlicensed)

10/6/16: Alma Normalization Rules

Bulk change permanent locations for item-less holdings records:

1. Go to Repository Search > Physical titles > Advanced search

2. Among your search conditions, include Holding (Has items) = No. ; also limit to a

specific Resource type for sanity.

3. Save Query

4. Edit the set (Name, Active, Private yes/no, etc.)

5. Save

6. Create and save a normalization rule (MD Editor > File > New > Normalization rules)

similar to the following (example: MUS is the new library and music is the new location)--

rule "Replace all values with MUS in 852 $$b (unconditional) and all values with

music in 852 $$c (unconditional)"

when

(TRUE)

then

replaceContents "852.b.*" with "MUS"

replaceContents "852.c.*" with "music"

end

7. In Resource Management > Configuration Menu > Metadata Configuration, click MARC

21 Holding.

8. On the Normalization Processes tab, click Add Process.

9. Fill in name and description on the General Information tab.

10. On the Task List tab, check the box for Marc Drool Normalization and hit Add To

Selection.

11. On the Task Parameters tab, choose your normalization rule from Step 6 from the

dropdown.

12. Save

13. (optional but recommended) Test the process on a single holdings record by using the

MD Editor > Edit > Enhance the Record.

14. To run the batch normalization on your set of physical titles, go to Administration >

Manage Jobs > Run a Job.

15. Select the Change Holding Information job and hit Next.

16. Select your set from steps 1-5 and hit Next.

17. Check the box for "Correct the data using normalization rules".

18. Select your normalization process from steps 7-12 from the dropdown and hit Next.

19. Hit Next.

20. Review the options and hit Submit.

Changing PROBLEM to SHELVED ALPHABETICALLY BY TITLE

rule "Change call number from PROBLEM to SHEVLED ALPHABETICALLY BY TITLE"

when

exists “852.h.PROBLEM”

then

replaceContents "852.h.*" with "SHELVED ALPHABETICALLY BY TITLE"

end

Things to be aware of with a Network Zone:

 Import profiles (come back in 2 weeks!) that use the NZ will not be able to use any of

these created processes. You’ll need to create a norm rule process in the NZ for

everyone to share with their Import Profiles. This will also help to create standardization

with your NZ bib records.

 NZ bib records will have the same problem if you are enhancing the record.

 This doesn’t apply to holdings as holdings records are IZ data.

Helpful links:

http://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(English)/

Resource_Management/040Metadata_Management/070Working_with_Normalization_Rules

http://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(English)/

Resource_Management/080Configuring_Resource_Management/030Configuring_Cataloging#

Working_with_Normalization_Processes

http://knowledge.exlibrisgroup.com/@api/deki/files/42165/Rules_-

_Normalization_rule_examples.docx

CHAT TRANSCRIPT

Chat transcript

from Chico!!! to Everyone:

Are there ever other options for when to run a job besides "as soon as possible"?

from Mark B. (Los Angeles) to Everyone:

And this job has entered a queue for the entire server? (i.e., all CALS)

from SFSU to Everyone:

Will this affect the call number browse? wil this cause all of these to show up in the s

from CSUSB to Everyone:

Is there a way to preview the changes before running the job similar to III's global update? If not, is

there a way to roll back changes?

from Mark Maritime to Everyone:

How do I add a normalization rule to the NZ (so it can be used on an inport profile)?

from Megan Drake to Everyone:

from yvonne (CPP) (privately):

Normalization rules are used to manipulate bib. records data, nothing else, right?

from Fresno to Everyone:

Can you stack multiple changes into one rule ?

from Laurie to Everyone:

Last week we applied a normalization rule to bib records

from Mark Maritime to Everyone:

Could you repeat your answer - I was called away.

from Mark Maritime to Everyone:

ok

from Mark Maritime to Everyone:

I didn't think my questionable joke would be made public.

from yvonne (CPP) to Everyone:

can we move a NZ norm rule to IZ?

from Mark Maritime to Everyone:

Surry for the mass triggering.

from yvonne (CPP) to Everyone:

ok and thanks

from Victoria Vega to Everyone:

Yes

from Mark B. (Los Angeles) to Everyone:

Yes, thanks for the second example...

from Chico!!! to Everyone:

For all the steps you just did.... is this workflow written somewhere in a step by step?

from Fresno to Everyone:

Can a process contain more than one norm rule?

from North American Professional Services to Everyone:

See also the CKC articles on normalization rules -

from North American Professional Services to Everyone:

https://knowledge.exlibrisgroup.com/Special:Search?qid=&fpid=230&fpth=&path=%2FAlma%2FKnowle

dge_Articles&search=normalization

from Mark B. (Los Angeles) to Everyone:

Whew!!! (a relief)

from Fresno to Everyone:

If you run a norm rule on bibs, it can only be for local fields or local records?

from Mallory (CO) to Everyone:

so to run a norm rule on NZ bibs you would need to run the rule when signed into the NZ instance?

from Mallory (CO) to Everyone:

perfect, thanks for the distinction (that I'm sure you already made).

from Sarina Sinick to Everyone:

Is there a way to push a rule created at an institution to the NZ?

from SFSU to Everyone:

If you change the holdings in a record, e.g. in a serial add additional volumes, how do you update BOTH

the Network Zone and the IZ?

from Sarina Sinick to Everyone:

So if a local institution were to create a NZ rule, you would still need someone to login to the NZ to

create the process, correct?

from Sarina Sinick to Everyone:

great, thanks

from Mark B. (Los Angeles) to Everyone:

The Local Fields (e.g., Los Angeles) associated with a NZ bib record-- changing Local Fields is an IZ

normalize rule/process?

from Mark B. (Los Angeles) to Everyone:

Thank you.

from SFSU to Everyone:

Thanks

from North American Professional Services to Everyone:

(note: will follow up after meeting on Mark B.'s question)

from Steve (SDSU) to Everyone:

In norm rules syntax, do we have to use "\\\\" (as you with periods), prior to other punctuation such as

parentheses, when we need that punctuation as text with a field?

from Steve (SDSU) to Everyone:

I'm trying to prefix some 035s with "(OCoLC)"

from Jeremy @ SLO to Everyone:

u have to escape those characters, like with regexes

from Steve (SDSU) to Everyone:

I've been trying it but can't get it to save, and the reasons given are unintelligible to me.

from Steve (SDSU) to Everyone:

Yes, that sounds good. I'll take the question there. Thank you.

from Jeremy @ SLO to Everyone:

very cool

from Jeremy @ SLO to Everyone:

thanks

from Mark B. (Los Angeles) to Everyone:

Thank you Megan, thank you Dolph.

from Samuel to Everyone:

Thank you!

from Janee Mason (HSU) to Everyone:

thank you.

from Alice Kawakami-CSU to Everyone:

thank you

from yvonne (CPP) to Everyone:

Thanks, Megan et al!!

from North American Professional Services to Everyone:

Note: upcoming topics (order change)

from Chris CPS to Everyone:

Thanks!

from North American Professional Services to Everyone:

Next week (Oct 13) - merge rules and preferred record behavior in import profiles and external search

from North American Professional Services to Everyone:

Oct 20 - import profiles

from North American Professional Services to Everyone:

Thanks!