<?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>02341nam a22002777a 4500</leader>
  <controlfield tag="001">9458</controlfield>
  <controlfield tag="003">OCLRC</controlfield>
  <controlfield tag="005">20260730103744.0</controlfield>
  <controlfield tag="008">210504t        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">Zhao, Linlin</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Riding the Wave of Open Access: Providing Library Research Support for Scholarly Publishing Literacy</subfield>
    <subfield code="c">Linlin Zhao</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2014.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">https://doi.org/10.1080/00048623.2014.882873</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Researchers are experiencing intense pressures to publish and increase research outputs. Recently many research funders have introduced policies and mandates related to open access, which have contributed to the increasing popularity of open access journals. Dubbed gold open access, open access journals offer researchers another publishing option. However, some publishers with questionable practices and journals of dubious quality have emerged exploiting the &#xFFFD;author pays&#xFFFD; open access model and researchers' need to publish. Hence an ability to publish research outputs through the most appropriate outlet for a particular field is crucial for researchers in order to maximise the impact of their research. Notwithstanding the proliferation of open access journals, the literature indicates that some researchers may not have a full understanding of the operations, implications and issues around open access and other publishing issues. This understanding is known as scholarly publishing literacy. With knowledge of scholarly publishing and access to resources and tools, academic libraries and librarians are well-positioned to play an active role in providing support to researchers. This paper argues that scholarly publishing literacy should be treated as an extension of information literacy delivered through a broader research support framework. This paper presents a research librarian's perspective, and draws on literature and the author's practice to illustrate key points. Issues for further investigation are identified.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">scholarly publishing literacy,</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">open access,</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a"> information literacy, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">digital scholarship, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">research support, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">academic libraries, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">author pays, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">green open access, </subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">gold open access.</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ELEC</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">9458</subfield>
    <subfield code="d">9458</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:44</subfield>
    <subfield code="w">2026-07-30</subfield>
    <subfield code="y">ELEC</subfield>
  </datafield>
</record>
