<div dir="ltr"><div>Hi,</div><div><br></div><div>To build on Jason's response, since NLM call numbers were designed to be formatted (almost) exactly like LC call numbers, the "asset.label_normalizer_lc" normalizer should do the trick. I did a tiny bit of empirical testing to double-check that.<br><br></div><div>Regards,</div><div><br></div><div>Galen<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 10, 2021 at 4:55 PM Jason Boyer via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">I thought I had more about this before I hit send but I guess not. The point of the normalizers are to pull the call number labels apart and make them sort consistently, so that the case doesn’t matter and the numbers sort the way we expect rather than the way a computer would normally do it. Looking at the label_sortkey field of asset.call_number for various types of call numbers should make it more obvious what the existing ones are doing.<div><br></div><div>Jason<br><div>
<div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div><br>-- <br>Jason Boyer<br>Senior System Administrator<br>Equinox Open Library Initiative<br><a href="mailto:JBoyer@equinoxOLI.org" target="_blank">JBoyer@equinoxOLI.org</a><br>+1 (877) Open-ILS (673-6457)<br><a href="https://equinoxOLI.org/" target="_blank">https://equinoxOLI.org/</a></div></div></div></div>
</div>
<div><br><blockquote type="cite"><div>On Jun 10, 2021, at 4:51 PM, Jason Boyer <<a href="mailto:JBoyer@equinoxOLI.org" target="_blank">JBoyer@equinoxOLI.org</a>> wrote:</div><br><div><div style="overflow-wrap: break-word;">Hi Jennifer, there isn’t an interface to manage this yet and while the Angular client’s auto-grid feature will allow you to see the table, you’re not able to add or edit any entries. One reason there’s no interface for it is that one of the required fields is the name of a database procedure to perform the necessary normalization for sorting.<div><br></div><div>These are the steps you’d need to take to add a new classification scheme today:</div><div><br></div><div>Look at the existing call number classification normalization functions to see if one of them is applicable to the new scheme: asset.label_normalizer_generic, asset.label_normalizer_dewey, and asset.label_normalizer_lc. If none of these normalizers will work for the new scheme a new normalizing function will need to be written. (We’ll assume you have to put together an asset.label_normalizer_nlm for now)</div><div><br></div><div>Insert a new row into asset.call_number_class:</div><div><font face="Courier New">name | normalizer | field</font></div><div><font face="Courier New">National Library of Medicine | asset.label_normalizer_nlm | 060ab,(other fields / subfields)</font></div><div><div>
<div dir="auto" style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div><br></div><div>Then the opensrf.settings service (at least?) may need to be restarted. I’m not entirely certain about the extent of that.</div><div><br></div><div>And then it’s time to test because I’ve not actually done this myself but I don’t believe classification schemes are hard-coded anywhere. :) </div><div><br></div><div>Jason</div><div><br>-- <br>Jason Boyer<br>Senior System Administrator<br>Equinox Open Library Initiative<br><a href="mailto:JBoyer@equinoxOLI.org" target="_blank">JBoyer@equinoxOLI.org</a><br>+1 (877) Open-ILS (673-6457)<br><a href="https://equinoxOLI.org/" target="_blank">https://equinoxOLI.org/</a></div></div></div></div>
</div>
<div><br><blockquote type="cite"><div>On Jun 10, 2021, at 3:43 PM, Jennifer Pringle via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> wrote:</div><br><div><div><br>Hello everyone,<br><br>I'm hoping someone can point me in the right direction for information about the classification schemes in Evergreen. I've looked through the official docs and the Evergreen wiki but I haven't been able to find anything that talks about how the classifications schemes are set up or what would be needed to set up a new one.<br><br>We've recently had a medical library join our consortium and they use National Library of Medicine as their classification scheme so I'm looking into what would be involved in adding NLM as an option in Evergreen.<br><br>Thanks,<br><br>Jennifer<br>-- <br>Jennifer Pringle (she/her)<br>Co-op Support - Training Lead<br>BC Libraries Cooperative<br>Toll-free: 1-888-848-9250<br><a href="mailto:jennifer.pringle@bc.libraries.coop" target="_blank">Email:jennifer.pringle@bc.libraries.coop</a><br>Website: <a href="http://bc.libraries.coop" target="_blank">http://bc.libraries.coop</a><br><br>Gratefully acknowledging that I live and work in the unceded Traditional Territory of the St'at'yemc Nations.<br><br>_______________________________________________<br>Evergreen-general mailing list<br><a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br><a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br></div></div></blockquote></div><br></div></div></div></blockquote></div><br></div></div>_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br><a href="mailto:gmc@equinoxOLI.org" target="_blank">gmc@equinoxOLI.org</a><br><a href="https://www.equinoxOLI.org" target="_blank">https://www.equinoxOLI.org</a> <br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581<br><a href="http://evergreen-ils.org" target="_blank"></a></div></div>