holding field location

[hhansen12]

Hello, I wonder if it would be possible to include subfields from holding 852(8#)? Specifically I'd like to print subfield $$g and/or $$x on the label. Unfortunately I couldn't find them in the existing fields.

Many thanks, Christoph

[Orshahar91]

Thanks, Christoph. Printing 852 $g / $x is possible only if those subfields are present in the item/holdings XML that SpineOMatic retrieves from Alma.

Please try:

1. In SpineOMatic, enable RESTful API, then Review → Scan a barcode and tick “Don’t convert XML ”
2. Check whether your 852 data appears in the payload (often $x maps to a holdings non-public note element).

• If you see the fields: add that element to a Custom label (using the field picker or the element name as shown in the XML) and it should print.
• If you don’t see them: SpineOMatic can’t access them via the current item call. Options would be to map/copy 852 $g/$x in Alma to a field returned by the Items API (e.g., a holdings note that is exposed).

[hhansen12]

Dear Or, thank you very much for your reply! Unfortunately I'm not able to use the solution you suggested thus I only have access to the cloudapp of SpineOMatic. Is there maybe some approach "852 $g / $x" is going to be included among the fields in the configuration-section?
All the best, Christoph

[Orshahar91]

Hi Christoph,

Thanks for the clarification and the follow-up.

First, this repository is for the Windows SpineOMatic client. For future questions and feature requests about the SpineOMatic Cloud App, please use:
https://github.com/ExLibrisGroup/spineomatic-cloudapp/issues

About 852 $g / $x in the Cloud App:

• The Cloud App does retrieve the full 852 holdings record (including $g and $x) from Alma.
• However, those subfields are not currently exposed in the template editor field list, so there isn’t a configuration-only way to add them to labels today.
• Making them available would require a code change in the Cloud App (adding 852 $g / $x to the field list and mapping them in the print component).

So at the moment the only workaround is still to copy that information in Alma into a holdings field that is exposed (for example a note/description) and use that field in the template.

If you’d like, you can open a feature request in the Cloud App repo asking to expose 852 $g / $x as template fields; the technical side is feasible, but it would need to be prioritized and implemented there.

Best regards,
Or