<div dir="ltr">Honestly, a big +1 to Tiffany's suggestion.<div><br></div><div>Could this be better in the database? Sure. Does MARC formatting make that harder than it should be? Yes.</div><div><br></div><div>Is it easier / faster to make Excel do the cleanup? 100%.</div><div><br></div><div>ABN</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 19, 2024 at 11:43 AM Tiffany Little via Evergreen-reports <<a href="mailto:evergreen-reports@list.evergreen-ils.org">evergreen-reports@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 dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">For what it's worth, although there are definitely places in the reporter that could make output more useful straight out of the gate, in this case I'd advocate for just cleaning up the data in Excel. At bare minimum, just doing a Find/Replace on copyright dates, brackets, etc could clean that right up so you could do an easy average formula to get what you need.</div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><span><br><div dir="ltr" style="margin-left:0pt" align="left"><table style="border:none;border-collapse:collapse"><colgroup><col width="89"><col width="414"></colgroup><tbody><tr style="height:123pt"><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.44;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:75px;height:75px"><img src="https://lh6.googleusercontent.com/8c2XlzLbIIC6nDoa4yqQ8MzA0npF4WXpUnhhoK_uTqralZtjqVXRwPgmRep3jGYP6q41Sb0ULXqxX-QppYTC8cQyIfBAdqzLBgqvcQwVczkqqiunlj0KIbvy-R3bp-E0mlhF0A4v" width="75" height="75" style="margin-left: 0px; margin-top: 0px;"></span></span></p></td><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.44;margin-left:9pt;margin-top:0pt;margin-bottom:0pt"><span></span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Tiffany Little, PINES Bibliographic Projects Manager</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"></p><hr><p></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Georgia Public Library Service</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341</span></p><p dir="ltr" style="line-height:1.44;margin-left:9pt;margin-top:0pt;margin-bottom:0pt"><span></span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9pt;font-family:Verdana,sans-serif;color:rgb(30,67,155);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">(404) 235-7161 | <a href="mailto:tlittle@georgialibraries.org" target="_blank">tlittle@georgialibraries.org</a></span></p><br><p dir="ltr" style="line-height:1.44;margin-left:9pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:36px;height:36px"><img src="https://lh6.googleusercontent.com/ql1so1R8csbb2W7DW5vjWe3mTAcApuM7a5CMXbsYnhmF1bDmG62LM_C1BOOyWdkb2PZGKGlaYRIceHjsSvsWPXNw6HPCKqtFLMKCJiPVU0RXu2dAey13WZ02Q6E6FmzNDJ_d9iBf" width="36" height="36" style="margin-left: 0px; margin-top: 0px;"></span></span><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:35px;height:35px"><img src="https://lh3.googleusercontent.com/2qSr0-AREIyPSTC1gMsjyXLaBT-yQ7kS6iKvd1L9XrCXxhJDWCRo5eXBHCi7f35AZASOOyiH2Si-wtuXNR8YaA2j-17GWBmmo1mpGxXa7m-JwF4AzUD_5tZZE9n1NVilAJcnGtQs" width="35" height="35" style="margin-left: 0px; margin-top: 0px;"></span></span><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:35px;height:35px"><img src="https://lh6.googleusercontent.com/-jM_GEWd7EZGo5MFiR1koKEkiupb_lmwNEMpNiQE3U6k1C2FkyuiNjtGKlWWGfX8zbZ1135yhOHnJSINmMTXgEQuu2RlHIg5hDKxaJ9cmh3Nr6el_vN4ZHlXcAmoCPPWduwXi26m" width="35" height="35" style="margin-left: 0px; margin-top: 0px;"></span></span></p></td></tr><tr style="height:21pt"><td colspan="2" style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.44;text-align:center;margin-top:0pt;margin-bottom:0pt"><a href="http://georgialibraries.org/" target="_blank"><span style="font-size:8pt;font-family:Verdana;color:rgb(17,85,204);background-color:transparent;font-style:italic;vertical-align:baseline;white-space:pre-wrap">Join our email list</span></a><span style="font-size:8pt;font-family:Verdana;color:rgb(0,0,0);background-color:transparent;font-style:italic;vertical-align:baseline;white-space:pre-wrap"> </span><span style="font-size:8pt;font-family:Verdana;color:rgb(67,67,67);background-color:transparent;font-style:italic;vertical-align:baseline;white-space:pre-wrap">for stories of Georgia libraries making an impact in our communities.</span></p></td></tr></tbody></table></div></span></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 16, 2024 at 2:29 PM Terran McCanna via Evergreen-reports <<a href="mailto:evergreen-reports@list.evergreen-ils.org" target="_blank">evergreen-reports@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 dir="ltr">If you create a Wish List bug in Launchpad, I'll add heat to it :)<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 16, 2024 at 2:23 PM Blake Graham-Henderson via Evergreen-reports <<a href="mailto:evergreen-reports@list.evergreen-ils.org" target="_blank">evergreen-reports@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">All,<br>
<br>
Thanks for your considerate responses. What Mike said is the conclusion <br>
I had come to, and I was wondering if anyone else needs the publication <br>
year to be an actual number so that the reporter can do things like <br>
average,min,max,etc. From the sounds of it, no one is currently using <br>
the Evergreen reporter to produce such a thing (I don't see how you <br>
could). I suppose no one is using an external program to make it happen <br>
(to meet collection reporting needs from the higher-ups)?<br>
<br>
I agree with Mike, in that the best place to get the publication year <br>
(right now) is the Simple Record Extracts, because it hunts it down from <br>
several places in the bib record. Walking it backwards:<br>
<br>
reporter.materialized_simple_record -> reporter.old_super_simple_record <br>
-> metabib.wide_display_entry -> metabib.compressed_display_entry -> <br>
metabib.flat_display_entry -> metabib.display_entry<br>
<br>
Which is a trigger-created-table based upon the index definition found <br>
in config.metabib_field<br>
<br>
one of those views is hardcoded to expect "pubdate" to exist in the <br>
metabib_field definitions. Which exists with stock Evergreen <br>
definitions. Which is:<br>
<br>
"//mods33:mods/mods33:originInfo//mods33:dateIssued[@encoding="marc"]|//mods33:mods/mods33:originInfo//mods33:dateIssued[1]"<br>
<br>
Decoding that is fun. Suffice it to say: the pubyear can come from <br>
several places in the record, and I like that better than only looking <br>
in one place.<br>
<br>
So, in conclusion, if a patch were written, I think it would be smart to <br>
piggy back on this logic. It might be fairly straightforward to get the <br>
first occurrence from the JSON string and cast it to an integer <br>
(stripping out non-numeric characters first). That's where my thoughts <br>
are right now. I don't think we're going to be writing the patch anytime <br>
soon, just thinking through it with everyone.<br>
<br>
If everyone agrees that this is something that Evergreen should have, <br>
and we agree on the method, I might champion the bug and patch for <br>
future meetings and releases!<br>
<br>
-Blake-<br>
Conducting Magic<br>
Will consume any data format<br>
MOBIUS<br>
<br>
_______________________________________________<br>
Evergreen-reports mailing list<br>
<a href="mailto:Evergreen-reports@list.evergreen-ils.org" target="_blank">Evergreen-reports@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-reports" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-reports</a><br>
</blockquote></div>
_______________________________________________<br>
Evergreen-reports mailing list<br>
<a href="mailto:Evergreen-reports@list.evergreen-ils.org" target="_blank">Evergreen-reports@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-reports" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-reports</a><br>
</blockquote></div>
_______________________________________________<br>
Evergreen-reports mailing list<br>
<a href="mailto:Evergreen-reports@list.evergreen-ils.org" target="_blank">Evergreen-reports@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-reports" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-reports</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="color:rgb(136,136,136);font-size:12.8px"><span style="font-size:12.8px">Andrea Buntz Neiman, MLS</span><br></div><div style="color:rgb(136,136,136);font-size:12.8px">Project Manager for Software Development | Product Specialist</div><div style="color:rgb(136,136,136);font-size:12.8px">Equinox Open Library Initiative</div><div style="color:rgb(136,136,136);font-size:12.8px"><a href="mailto:abneiman@equinoxoli.org" target="_blank">abneiman@equinoxOLI.org</a></div><div style="color:rgb(136,136,136);font-size:12.8px"><span style="font-size:12.8px">1-877-OPEN-ILS </span><span style="font-size:12.8px">(673-6457)</span><br></div><div style="color:rgb(136,136,136);font-size:12.8px"><span style="font-size:12.8px">Direct: 770-709-5583</span></div><div><font color="#0000ee"><u><a href="https://www.equinoxOLI.org/" target="_blank">https://www.equinoxOLI.org/</a></u></font><br></div></div></div></div></div></div>