<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Thank you for raising (perhaps again) this point - I hope it doesn't get lost in your rather specific subject line.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I've just been struggling with trying to analyze certain major vendor ebook subscription collections via the marc records they've provided us, and I am absolutely horrified at the poor quality of some key metadata they are providing, such basic stuff as pubdate and publisher name.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">MARC/AACR/RDA standards are written so loosely to accommodate individual librarian/library preferences for individual books, and I think content providers are taking advantage of such flexibility to give us metadata that makes it extremely difficult to manage large sets of records/holdings.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">ISO is in the middle of doing a major revision of their standard for "Information and documentation -- Presentation and identification of periodicals"</div><div class="gmail_default"><font face="arial, helvetica, sans-serif"><a href="https://www.iso.org/standard/67723.html">https://www.iso.org/standard/67723.html</a></font><br></div><div class="gmail_default"><font face="arial, helvetica, sans-serif">part of their Information and Documentation series:</font></div><div class="gmail_default"><font face="arial, helvetica, sans-serif"><a href="https://www.iso.org/ics/01.140.40/x/">https://www.iso.org/ics/01.140.40/x/</a><br></font></div><div class="gmail_default"><br></div><div class="gmail_default"><font face="arial, helvetica, sans-serif">I think we need to develop a standard or at least "recommended practice" for ebooks, with comparable detail and requirements for consistency of metadata.</font></div><div class="gmail_default"><font face="arial, helvetica, sans-serif">In the NASIG "Standards" group, we're just beginning a discussion about ebook metadata, initially focused on just the problems of ISBNs, but Jeff's post makes me think we should look more broadly at ebook metadata and go beyond individual cataloguing rules and consider special rules about consistency within collections.</font></div><div class="gmail_default"><font face="arial, helvetica, sans-serif">If anyone knows of any work already being done on such standards/rules, please let us know.</font></div><div class="gmail_default"><font face="arial, helvetica, sans-serif"><br></font></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div><div dir="ltr" class="gmail-m_927543958594301325gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Melissa Belvadi</div><div>Collections Librarian</div><div>University of Prince Edward Island</div><div><a href="mailto:mbelvadi@upei.ca" target="_blank">mbelvadi@upei.ca</a> 9<span style="font-size:12.8px">02-566-0581</span></div><div>my <a href="http://www.google.com/calendar/embed?src=mbelvadi%40upei.ca&ctz=America/Halifax&mode=week" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(17,85,204)" target="_blank">public calendar</a></div><div><a href="https://mbelvadi.youcanbook.me/" target="_blank">Make an appointment</a> via YouCanBookMe</div><div><br></div><div><br><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Dec 21, 2018 at 10:58 AM J Siemon <<a href="mailto:jsiemon2002@gmail.com" target="_blank">jsiemon2002@gmail.com</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">OCLC Knowledge Base collection Oxford Scholarship Online Religion = OUP.osoReligion is missing the Sept 2018 Religion titles from Oxford Scholarship Online, and three older titles. OCLC and Oxford are both excellent organizations, yet sometimes even reliable vendors make mistakes.<br><br>This is a good example of a larger issue I've been discussing at conferences for the last couple years. Libraries need to devote significantly more staff resources to reviewing collection metadata. Libraries hire thousands of catalogers, who spend time reviewing MARC data for <u>individual</u> titles. I'm convinced that some of these people/staff resources need to be reallocated to review the accuracy of <u>collection</u> level data. Book and journal budgets have shifted toward purchasing collections of eResources (instead of individual titles). Library staffing needs to shift in a similar manner, toward reviewing and correcting collection level metadata in addition to individual title data. When collection level data is wrong, tens, and sometime hundreds of e-books or e-articles are not available to our patrons.<br><br>I've contacted support staff at both organizations.<br>I don't know whether Oxford neglected to send this data or OCLC neglected to load these titles. <br><br>In any case more library staff need to be devoted to noticing these collection level metadata issues, and trouble-shooting with vendors to make the corrections. See my article from the Charleston Conference, 2017, "You May Own It . . . But Can They Find It? A Panel Discussion: Part 3 of Panel Presentation: Collection-Level Cooperative Cataloging" <a href="https://dx.doi.org/10.5703/1288284316663" style="color:rgb(5,99,193);text-decoration:underline" target="_blank">https://dx.doi.org/10.5703/1288284316663</a>
or some of my presentations at slideshare <a href="https://www.slideshare.net/jsiemon/presentations" style="color:rgb(5,99,193);text-decoration:underline" target="_blank">https://www.slideshare.net/jsiemon/presentations</a>
<span></span>
<p class="gmail-m_927543958594301325gmail-m_5339727546991814189gmail-MsoNoSpacing" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span> </span></p>
<p class="gmail-m_927543958594301325gmail-m_5339727546991814189gmail-MsoNoSpacing" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">All the best,<span></span></p>
<p class="gmail-m_927543958594301325gmail-m_5339727546991814189gmail-MsoNoSpacing" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Jeff Siemon<span></span></p>
</div>
_______________________________________________<br>
Eril-l mailing list<br>
<a href="mailto:Eril-l@lists.eril-l.org" target="_blank">Eril-l@lists.eril-l.org</a><br>
<a href="http://lists.eril-l.org/listinfo.cgi/eril-l-eril-l.org" rel="noreferrer" target="_blank">http://lists.eril-l.org/listinfo.cgi/eril-l-eril-l.org</a><br>
</blockquote></div>
</div>