<?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>02275nam a22002417a 4500</leader>
  <controlfield tag="001">9444</controlfield>
  <controlfield tag="003">OCLRC</controlfield>
  <controlfield tag="005">20260730103743.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">Masten, Yondell</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Due diligence in the open-access explosion era: choosing a reputable journal for publication</subfield>
    <subfield code="c">Yondell Masten</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2017.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">https://doi.org/10.1093/femsle/fnx206</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Faculty are required to publish. Na&#xFFFD;ve and &#xFFFD;in-a-hurry-to-publish&#xFFFD; authors seek to publish in journals where manuscripts are rapidly accepted. Others may innocently submit to one of an increasing number of questionable/predatory journals, where predatory is defined as practices of publishing journals for exploitation of author-pays, open-access publication model by charging authors publication fees for publisher profit without provision of expected services (expert peer review, editing, archiving, and indexing published manuscripts) and promising almost instant publication. Authors may intentionally submit manuscripts to predatory journals for rapid publication without concern for journal quality. A brief summary of the open access &#xFFFD;movement,&#xFFFD; suggestions for selecting reputable open access journals, and suggestion for avoiding predatory publishers/journals are described. The purpose is to alert junior and seasoned faculty about predatory publishers included among available open access journal listings. Brief review of open access publication, predatory/questionable journal characteristics, suggestions for selecting reputable open access journals and avoiding predatory publishers/journals are described. Time is required for intentionally performing due diligence in open access journal selection, based on publisher/journal quality, prior to manuscript submission or authors must be able to successfully withdraw manuscripts when submission to a questionable or predatory journal is discovered.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">open access,</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">predatory journals,</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">predatory publishers,</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">characteristics of ethical and unethical publishing practices,</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">due dilegence activities for selecting reputable journals</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Ashcraft, Alyce</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ELEC</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">9444</subfield>
    <subfield code="d">9444</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>
