Call number parsing problem

[R1ckyYg]

We have tested printing the spine label by the holding call number (field = item_data.call_no), there is no problem in call number parsing.

However, the parsing failed if we changed to use item call number (field = item_data.alt_call_no).

[R1ckyYg]

We expect the call number "HF1379" can be separated into two lines instead of showing in one line.

[mgobat]

@R1ckyYg, what are your "Call number" settings under "Other options" in the Template you are using?

[R1ckyYg]

@mgobat

[mgobat]

Thanks, @R1ckyYg.

[mgobat]

@R1ckyYg, what is your "Call Number Parsing Type" defined in Alma?

https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Physical_Resource_Management/070_Configuring_Resource_Management/060_Configuring_Call_Number_Parsing_when_Printing_Labels

[mgobat]

@R1ckyYg , I don't think this is a Cloud App problem. My test case has a call number of "KZ6385 .L37 2014" and an alt call number of "KZ6385 .L37345 2014". My parsing routine for LC Call numbers is set to Parsing Routine 5 in Alma..

For the call number, the Cloud App gets the following from Alma: call number passed to getCallNo = ["KZ","6385",".L37","2014"]

For the alt_call_no, the Cloud App gets the following from Alma: call number passed to getCallNo = ["KZ6385",".L37345","2014"]

It appears that Alma isn't applying parsing routine 5 to the alt_call_no. I don't know if this is a defect in Alma or done by design. I will try to find out.

[R1ckyYg]

@mgobat We are using Parsing Routine 5 too

[R1ckyYg]

@mgobat Do you have any solution that we can parse the alt call number "KZ6385 .L37345 2014" to ["KZ","6385",".L37345","2014"]? Please let me know if you have any suggestions or updates, thank you.

[mgobat]

@R1ckyYg, this is apparently an issue outside the Cloud App. It might be a good idea to open a Support case. https://support.proquest.com/s/submit-a-case