<?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>02552nab a2200217   4500</leader>
  <controlfield tag="005">20260608201743.0</controlfield>
  <controlfield tag="008">260224s2013    xxu                 ing  </controlfield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">Ingl&#xE9;s</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Milliken, Kitty L.</subfield>
    <subfield code="9">13547</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Rudnicky, Mark</subfield>
    <subfield code="9">52951</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Awwiller, David N.</subfield>
    <subfield code="9">52952</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Zhang, Tongwei</subfield>
    <subfield code="9">52953</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Organic matter-hosted pore system, Marcellus Formation (Devonian), Pennsylvania</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">feb. 2013</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">30/10/2013 ; 30/10/2013</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">23 p.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor: The Marcellus Formation of Pennsylvania represents an outstanding example of an organic matter (OM)-hosted pore system; most pores detectable by field-emission scanning electron microscopy (FE-SEM) are associated with OM instead of mineral matrix. In the two wells studied here, total organic carbon (TOC) content is a stronger control on OM-hosted porosity than is thermal maturity. The two study wells span a maturity from late wet gas (vitrinite reflectance [Ro], ~1.0%) to dry gas (Ro, ~2.1%). Samples with a TOC less than 5.5 wt. % display a positive correlation between TOC and porosity, but samples with a TOC greater than 5.5 wt. % display little or no increase in porosity with a further increasing TOC. In a subset of samples (14) across a range of TOC (2.3-13.6 wt. %), the pore volume detectable by FE-SEM is a small fraction of total porosity, ranging from 2 to 32% of the helium porosity. Importantly, the FE-SEM-visible porosity in OM decreases significantly with increasing TOC, diminishing from 30% of OM volume to less than 1% of OM volume across the range of TOC. The morphology and size of OM-hosted pores also vary systematically with TOC. The interpretation of this anticorrelation between OM content and SEM-visible pores remains uncertain. Samples with the lowest OM porosity (higher TOC) may represent gas expulsion (pore collapse) that was more complete as a consequence of greater OM connectivity and framework compaction, whereas samples with higher OM porosity (lower TOC) correspond to rigid mineral frameworks that inhibited compactional expulsion of methane-filled bubbles. Alternatively, higher TOC samples may contain OM (low initial hydrogen index, relatively unreactive) that is less prone to development of FE-SEM-detectable pores. In this interpretation, OM type, controlled by sequence-stratigraphic position, is a factor in determining pore-size distribution.</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g"></subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">187942</subfield>
    <subfield code="d">187942</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="9">255761</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200060096</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200060096</subfield>
    <subfield code="r">2026-03-06 00:17:57</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
