<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">57799</controlfield>
        <controlfield tag="005">20200221144318.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.4103/1008-682X.188451</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">97119</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2016-97119</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="a">Soler, C.</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">Afterword to Sperm morphometrics today and tomorrow special issue in Asian Journal of Andrology</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2016</subfield>
        </datafield>
        <datafield tag="506" ind1="0" ind2=" ">
            <subfield code="a">Access copy available to the general public</subfield>
            <subfield code="f">Unrestricted</subfield>
        </datafield>
        <datafield tag="520" ind1="3" ind2=" ">
            <subfield code="a">The problems associated with the subjective assessment of human sperm morphology have been well aired in another Asian Journal of Andrology Special Issue 1 that marked the publication of the 5 th edition of the WHO Semen analysis manual, and contrary views have subsequently been presented. 2 However, the vagaries of the eye-brain system in assessing whether a sperm head is large or small can be eliminated by objective assessment where definitive structures are defined by their dimensions. These can then be classified automatically into as many categories as the data permit, conventionally on the basis of preset upper and lower limits, but also by more comprehensive analysis as discussed here...</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">by</subfield>
            <subfield code="u">http://creativecommons.org/licenses/by/3.0/es/</subfield>
        </datafield>
        <datafield tag="590" ind1=" " ind2=" ">
            <subfield code="a">2.996</subfield>
            <subfield code="b">2016</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">ANDROLOGY</subfield>
            <subfield code="b">1 / 5 = 0.2</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q1</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">UROLOGY &amp; NEPHROLOGY</subfield>
            <subfield code="b">22 / 76 = 0.289</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q2</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="592" ind1=" " ind2=" ">
            <subfield code="a">0.793</subfield>
            <subfield code="b">2016</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Urology</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Medicine (miscellaneous)</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="655" ind1=" " ind2="4">
            <subfield code="a">info:eu-repo/semantics/article</subfield>
            <subfield code="v">info:eu-repo/semantics/publishedVersion</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Cooper, T.</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Valverde, A.</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0001-5316-1703</subfield>
            <subfield code="a">Yániz, J.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">2008</subfield>
            <subfield code="2">700</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Produc.Animal Cienc.Ali.</subfield>
            <subfield code="c">Área Producción Animal</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">18, 6 (2016), 895-897</subfield>
            <subfield code="p">Asian J. Androl.</subfield>
            <subfield code="t">Asian journal of andrology</subfield>
            <subfield code="x">1008-682X</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">241890</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/57799/files/texto_completo.pdf</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">141365</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/57799/files/texto_completo.jpg?subformat=icon</subfield>
            <subfield code="x">icon</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:57799</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2020-02-21-13:40:19</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>