ExLibrisGroup / spineomatic-cloudapp

Cloud App version of SpineOMatic
BSD 3-Clause "New" or "Revised" License
5 stars 5 forks source link

Expose the item's alternative call number individual parts for inclusion in a label template #132

Open AdrianMenti opened 2 weeks ago

AdrianMenti commented 2 weeks ago

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:

Screenshot_000111

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:

Screenshot_000114

I wish you a nice day.

Best regards,

Adrian

mgobat commented 2 weeks ago

@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 commented 2 weeks ago

Hello mgobat

Thank you for your reply! We use in general the item call number for our labels, like in the picture.

image

Would it be possible to do for those or is it only possible for the parsed call number?

Best regards, Adrian

mgobat commented 2 weeks ago

@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.

mgobat commented 2 weeks ago

@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.

AdrianMenti commented 2 weeks ago

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, Adrian

mgobat commented 2 weeks ago

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:

  1. Parsed alt call number part one
  2. Parsed alt call number part two
  3. Parsed alt call number part three
  4. Parsed alt call number part four
  5. Parsed alt call number part five
  6. Parsed alt call number part six
  7. Parsed alt call number part seven
  8. Parsed alt call number part eight
  9. Parsed alt call number part nine
  10. Parsed alt call number part ten

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.

Here's an example template: altCallNumber

AdrianMenti commented 1 week ago

Hello mgobat

Thank you for your answer and sorry for the late reply! Yes, this would be perfect but I have a few questions.

  1. "Note that this would require the parsed alternative call number to have empty parts."

    • In ALMA we have written our labels like this: PC 13:-1(Ed.7)+2
    • So we would have to change our labels like this for example "PC 13: -1 (Ed.7) +2" for it to work. Is that correct?
  2. Would it cost something to implement this enhancement? If yes, how much would it cost?

I wish you a nice day.

Best regards, Adrian

mgobat commented 1 week ago

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. There is no cost for Cloud App enhancements, though generally enhancements of interest to more than one customer get priority.

AdrianMenti commented 1 week ago

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, Adrian

mgobat commented 1 week ago

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.