Forum - Spineomatic Call Number Line Breaks

  • This topic has 4 replies, 3 voices, and was last updated 1 week ago by Humber Humber.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #73137
    Michigan Shared System Alliance # 6 – Oakland University 01COL_OAKLAND
    Participant

    Hello! I’m learning to use the Spineomatic cloud app in hopes if replacing the desktop version for my users. I’m having no luck with the line breaks for the call number of a spine label. I have the call number fields selected for display (it does), line breaks between call number parts checked, and Default(Alma) selected for the parser. If I am understanding correctly, this setup should consult the call number parsing routine defined for this call number type in Alma configuration. It is not. Am I missing a configuration to use the call number parsing routine or misunderstanding what is meant by the Default(Alma) selection? I appreciate any help you can provide. = Sarah, Oakland University

    #73139
    Mark Gobat
    Keymaster

    Sarah, can you provide an example of the call number, the call number parsing routine selected for that call number type in Alma, and how it is printed both with the “Line breaks between call number parts” checked and not checked? Your interpretation of how it should work does sound correct to me. Thanks.

    #73140
    Michigan Shared System Alliance # 6 – Oakland University 01COL_OAKLAND
    Participant

    Here is the 852 data:
    852 0_ |b OU-KL |c pop |h PS3602.E66347 |i I46 2018

    I have chosen Parsing Routine 5 for library of congress call numbers.

    Whether I have the line breaks option checked or not checked, the data looks like this:

    PS3602.E66347
    I46 2018

    The I46 line is centered under the preceding line, I don’t know how it will save.

    #73444
    Michigan Shared System Alliance # 6 – Oakland University 01COL_OAKLAND
    Participant

    Has anyone else had trouble getting the Cloud Apps Spineomatic to work with the assigned parsing routine?

    #76197
    Humber Humber
    Participant

    Hi Sarah,

    Not really sure what the problem might be with your setup, but I can share what worked for us:

    Template:

    We included the parsed call number field in the template
    {{field:item_data.call_no}}

    Enabled line breaks between call number parts

    Set call number parser to Default (Alma)

    This is an example of a 050 field
    050 _4 |a KEO1114.74 |b .O57

    We chose parser routine number 5 for the Library of Congress classification and got our desired line breaks:

    KEO
    1114.74
    .O57

    Best regards,
    Daniel

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.