[Evergreen-catalogers] FW: 245 display

[Elizabeth Davis]

Sorry, wrong listserv.

[cid:image003.png at 01D9EB9E.49A4FD90]Elizabeth Davis (she/her), Support & Project Management Specialist
Pennsylvania Integrated Library System (PaILS) | SPARK
(717) 256-1627 | elizabeth.davis at sparkpa.org<mailto:katherine.dannehl at sparkpa.org>
support.sparkpa.org<https://support.sparkpa.org/> | support at sparkpa.org<mailto:support at sparkpa.org>

From: Evergreen-catalogers <evergreen-catalogers-bounces at list.evergreen-ils.org> On Behalf Of Elizabeth Davis via Evergreen-catalogers
Sent: Wednesday, September 20, 2023 8:41 AM
To: evergreen-catalogers at list.evergreen-ils.org
Cc: Elizabeth Davis <elizabeth.davis at sparkpa.org>
Subject: [Evergreen-catalogers] FW: 245 display

Hello Everyone,

Just wanted to share this post from the Evergreen Cataloging listerv.  Does anyone use the $n and $p in their records? I didn’t see it in the sample title that Kate shared.

Thanks!

[cid:image005.png at 01D9EB9E.49A4FD90]Elizabeth Davis (she/her), Support & Project Management Specialist
Pennsylvania Integrated Library System (PaILS) | SPARK
(717) 256-1627 | elizabeth.davis at sparkpa.org<mailto:katherine.dannehl at sparkpa.org>
support.sparkpa.org<https://support.sparkpa.org/> | support at sparkpa.org<mailto:support at sparkpa.org>

From: Evergreen-catalogers <evergreen-catalogers-bounces at list.evergreen-ils.org<mailto:evergreen-catalogers-bounces at list.evergreen-ils.org>> On Behalf Of Kate Coleman via Evergreen-catalogers
Sent: Wednesday, September 20, 2023 8:21 AM
To: Evergreen Community Catalogers <evergreen-catalogers at list.evergreen-ils.org<mailto:evergreen-catalogers at list.evergreen-ils.org>>
Cc: Kate Coleman <kcoleman at jeffcolib.org<mailto:kcoleman at jeffcolib.org>>
Subject: [Evergreen-catalogers] 245 display

I originally sent this to the Evergreen general listserv last week because I thought the answers might get code-heavy, but I just need to know if any other systems experience this. I got crickets from that list, unfortunately.

We have a big issue with the way the 245 displays when an .$n and ,$p field are in use. It's even worse when a :$b is needed as well, like in the attached example. 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?

[https://ci3.googleusercontent.com/mail-sig/AIorK4y44qSWrBhGjKs9a3JDgm3D0kulOrUMrSYxOtB-3WrXdtE67SX9fTIBchZv3QMgrB-59UFJ71M]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20230920/91148d2d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10034 bytes
Desc: image001.png
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20230920/91148d2d/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 5402 bytes
Desc: image003.png
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20230920/91148d2d/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 5394 bytes
Desc: image005.png
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20230920/91148d2d/attachment-0005.png>