<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01565nam a22002657a 4500</leader>
  <controlfield tag="001">9435</controlfield>
  <controlfield tag="003">OCLRC</controlfield>
  <controlfield tag="005">20260730103743.0</controlfield>
  <controlfield tag="008">210503t        xxu||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">OCLRC</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Bulock, Chris</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">OA in the library collection:</subfield>
    <subfield code="b">the challenges of identifying and maintaining open access resources/</subfield>
    <subfield code="c">Chris Bulock, Nathan Hosburgh, &amp; Sanjeet Mann.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2015.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">https://doi.org/10.1080/0361526X.2015.1023690</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">While librarians, researchers, and the general public have embraced the concept of Open Access (OA), librarians still have a difficult time managing OA resources. To find out why, Bulock and Hosburgh surveyed librarians about their experiences managing OA resources and the strengths and weaknesses of management systems. At this session, they shared survey results, reflected on OA workflows at their own libraries, and updated audience members on relevant standards and initiatives. Survey respondents reported challenges related to hybrid OA, inaccurate metadata, and inconsistent communication along the serials supply chain. Recommended solutions included the creation of consistent, centralized article-level metadata and the development of OA collection development principles for libraries.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Open Access, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Metadata, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Knowledgebases, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Link resolver, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Discovery services, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Electronic services </subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Hosburgh, Nathan</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Mann, Sanjeet</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ELEC</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">9435</subfield>
    <subfield code="d">9435</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">LRC</subfield>
    <subfield code="b">LRC</subfield>
    <subfield code="d">2026-07-30</subfield>
    <subfield code="l">0</subfield>
    <subfield code="r">2026-07-30 10:37:43</subfield>
    <subfield code="w">2026-07-30</subfield>
    <subfield code="y">ELEC</subfield>
  </datafield>
</record>
