Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When using Parsed call number in the template, is it being pulled from the holdings record still? #41

Open
MaggieMcGee opened this issue Mar 21, 2022 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@MaggieMcGee
Copy link

Hi,

If you use the parsed call number? Where is it pulling the call number from? Using the holding call number does not allow the call number parsing to work properly when using that in the template. I switched to parsed call number and it works as it should.

Thanks,
Maggie

@mgobat mgobat self-assigned this Mar 24, 2022
@mgobat mgobat added the question Further information is requested label Mar 24, 2022
@mgobat
Copy link
Collaborator

mgobat commented Mar 24, 2022

Using "parsed call number" in the template uses the call number from the item record.

@MaggieMcGee
Copy link
Author

MaggieMcGee commented Oct 11, 2022 via email

@mgobat
Copy link
Collaborator

mgobat commented Oct 11, 2022

@MaggieMcGee, what fields are you including in your template?

If you want the "Item Call Number" from the item, then include "Parsed alternative call number" or item_data.alternative_call_number.

The holdings call number should be printed if you include "Parsed call number", "Raw call number", or holdings_data.call_number.

There is no logic in the application for using one call number if the other doesn't exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants