<?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>00910nam a22001337a 4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">533184</subfield>
    <subfield code="d">533184</subfield>
  </datafield>
  <controlfield tag="008">260428b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Dias, Michelle</subfield>
    <subfield code="9">60301</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Kanji as commons: Everyday food and politics of traditional knowledge</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(12), Mar 21, 2026: p.21-23</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">In India, kanji is more than food; it is a social practice, a medicinal comfort, and an ecological memory of rice cultivation. The preparation of kanji encodes knowledge of rice varieties, seasonal rhythms, fermentation, and the gendered labour of caregiving. Yet, despite this richness, kanji and similar forms of everyday food knowledge rarely figure within the frameworks of traditional knowledge protection in India.-Reproduced 

https://www.epw.in/journal/2026/12/commentary/kanji-commons.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">408355</subfield>
    <subfield code="a">IIPA</subfield>
    <subfield code="b">IIPA</subfield>
    <subfield code="d">2026-04-28</subfield>
    <subfield code="h">61(12), Mar 21, 2026: p.21-23</subfield>
    <subfield code="p">AR138696</subfield>
    <subfield code="r">2026-04-28</subfield>
    <subfield code="y">AR</subfield>
  </datafield>
</record>
