[Evergreen-general] Ideas about 245 display

[Kate Coleman]

This may be a cataloging question, but there is big-picture, code-y stuff
too, so I sent this to a wider audience.

We have a big issue with the way the 245 displays when an .$n and ,$p field
are in use. The lack of punctuation and field order make the title nearly
unreadable. An example is attached. Our support vendor says "Evergreen
displays the 245 title as instructed by mods32 and LoC.
https://www.loc.gov/standards/mods/v3/mods-mapping-3-2.html#title"

This seems like something that other Evergreen users would have complained
about before, so I'm wondering if other Evergreeners have come up with a
workaround?

(For my cataloging cohorts, I do know the use of a :$b field after a ,$p
field isn't something seen often, but this series is WEIRD and after
several seasoned catalogers looked at book in hand, we decided to run with
it).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20230912/e885388c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot 2023-09-12 092250.jpg
Type: image/jpeg
Size: 112877 bytes
Desc: not available
URL: <http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20230912/e885388c/attachment-0001.jpg>