<?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>01792nmm a22002657a 4500</leader>
  <controlfield tag="003">ES-BaAUN</controlfield>
  <controlfield tag="005">20230110120535.0</controlfield>
  <controlfield tag="008">221102| ||||go||d|||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">2575-5374</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">ES-BaAUN</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">ES-BaAUN</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Przybylski, Maya</subfield>
    <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Towards Ecologically-Informed Methods: Design&#x2019;s Confrontation with Complexity</subfield>
  </datafield>
  <datafield tag="260" ind1="3" ind2=" ">
    <subfield code="b">urbanNext,</subfield>
    <subfield code="c">September 14, 2017.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">3197 words.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Actar, Bracket 3 [at extremes], Energy and sustainability, Essay, Maya Przybylski, No Density, Technology and fabrication, Urban Paradigms</subfield>
  </datafield>
  <datafield tag="501" ind1=" " ind2=" ">
    <subfield code="a">Built landscape, Canada, Challenge, Design, Digital identity, Digital landscape, Ecological activation, Ecological footprint, Ecological urbanism, Ecology, Emerging ecology, Essay, Evolutionary ecology, Hybridization, New Statements on Nature, Urban exploration, Urban Paradigms</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Excerpt from "Bracket 3 [at extremes]" -- https://actar.com/product/bracket-3/</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Check Bracket Organization -- https://brkt.org/</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">As we understand an extreme as a position away from a balanced, predictable and familiar centre, it is reasonable to examine a condition of extreme as it relates to complexity. In particular, if complexity is understood as a characterization of the degree to which something is composed of many parts, the degree to which those parts are interrelated and, further, the sophistication of the processes that define these very relationships, it is possible to imagine moving towards an extreme complexity.</subfield>
  </datafield>
  <datafield tag="653" ind1="0" ind2="0">
    <subfield code="a">Extremes</subfield>
  </datafield>
  <datafield tag="653" ind1="0" ind2="0">
    <subfield code="a">Complexity</subfield>
  </datafield>
  <datafield tag="653" ind1="0" ind2="0">
    <subfield code="a">Design</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://urbannext.net/towards-ecologically-informed-methods-designs-confrontation-complexity/</subfield>
    <subfield code="z">Access to info</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">CF</subfield>
    <subfield code="n">0</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">1441</subfield>
    <subfield code="d">1441</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="a">9876543210</subfield>
    <subfield code="b">9876543210</subfield>
    <subfield code="d">2023-01-10</subfield>
    <subfield code="l">0</subfield>
    <subfield code="r">2023-01-10</subfield>
    <subfield code="w">2023-01-10</subfield>
    <subfield code="y">CF</subfield>
  </datafield>
</record>
