-
Notifications
You must be signed in to change notification settings - Fork 5
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
Expose the item's alternative call number individual parts for inclusion in a label template #132
Comments
@AdrianMenti, have you tried using the individual call number parts when creating the label template? There are fields named "Parsed call number part one" through "Parsed call number part ten". You could place the relevant parts on separate lines in the template. Each line can have its own font formatting; bold, italic, underlined, font, font size, centered, left/right justified. Then there is a checkbox "Keep label spacing when field empty" at the bottom of the template options. Try checking that checkbox to see if it keeps the blanks in the labels when a call number part is empty. |
@AdrianMenti, unfortunately only the parsed call number's individual parts are available for inclusion in a template. To add the same functionality for the item's alternative call number is an enhancement. I've changed the summary of this issue and labeled it an enhancement. |
@AdrianMenti, you could include the "item_data.alternative_call_number" in your template, then in the "Call number" options turn on the checkbox for "Line breaks between call number parts" and select "Split By Space" for the "Call Number Parser" field. However, this won't support formatting/font options for different parts of the call number, nor keeping spacing when certain parts are missing. |
Hello mgobat Thank you for your reply and suggestion! This won't work, since we have formatted all our labels so far. Would an enhancement be possible? Just asking, so I can present the answer to my boss. Best regards, |
Hi @AdrianMenti. This is a potential enhancement for the Cloud App. Let me summarize how we might be able to implement it. Please let me know if it solves the problem. Thank you. New fields in the "Add field" dropdown when editing a template:
Adding any of these new fields to the template would take the corresponding part number from the "Parsed alternative call number" (item_data.alt_call_no) field. Each part could have its own font, font size, font characteristics (bold, etc), and alignment (left, center, right). Checking the "Keep label spacing when field empty" checkbox would keep blank lines in the label if a particular part didn't exist. Note that this would require the parsed alternative call number to have empty parts. |
Hello mgobat Thank you for your answer and sorry for the late reply! Yes, this would be perfect but I have a few questions.
I wish you a nice day. Best regards, |
Hi @AdrianMenti. I don't know the immediate answer to your first question. I'm not sure how Alma handles blanks in its call number parsing algorithm; let me learn more before I answer. |
Hello @mgobat Thank you for looking into it! Of course, we are possibly the only ones asking for this enhancement. Could you give me a rough estimate of how long it could take to implement the enhancement? I wish you a nice day. Best regards, |
The latest beta version, v1.4.0-beta-01, has the ability to include individual parts of the alternative call number in a label template. To try the beta, click the "i" (information) icon on the SpineOMatic tile in the "Cloud App Center" in Alma, then click the "Try v1.4.0-beta-01" link. Please add feedback/comments to this issue. Thank you. |
Hello!
We want to use SpinoMatic for our labels in our library and have a few questions regarding the customization of a field label.
Our labels look this:
It includes from top to bottom:
So far we can get the needed label with this field: {{field:item_data.alt_call_no}}
The problem is, that it's arranged in line instead of from top to bottom, like in the image.
Our questions are:
I wish you a nice day.
Best regards,
Adrian
The text was updated successfully, but these errors were encountered: