<?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>00959nam a22001337a 4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">533894</subfield>
    <subfield code="d">533894</subfield>
  </datafield>
  <controlfield tag="008">260713b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Patil, Suresh and  Bhowmick, Aditi </subfield>
    <subfield code="9">61622</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a"> Details matter: Insights from Karnataka for a caste census</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Economic &amp; Political Weekly  </subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">61(25), Jun 20, 2026: p.36-118</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Opponents of the caste census highlight the complexities and challenges associated with conducting a caste census, including the fluidity of caste identity, interchangeable caste names, internal migration, and changes in faith, to assert that such an exercise will generate inconsistent data. Focusing on Karnataka, this article delves into the complexities of caste identities and provides tangible examples to better inform the conduct of a future caste census. &#x2013; Reproduced 

https://www.epw.in/journal/insight/details-matter.html
</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="a">Economic &amp; Political Weekly  </subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">AR</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">409079</subfield>
    <subfield code="a">IIPA</subfield>
    <subfield code="b">IIPA</subfield>
    <subfield code="d">2026-07-13</subfield>
    <subfield code="h">61(25), Jun 20, 2026: p.36-118</subfield>
    <subfield code="p">AR139353</subfield>
    <subfield code="r">2026-07-13</subfield>
    <subfield code="y">AR</subfield>
  </datafield>
</record>
