<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="7363" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.socictopen.socict.org/items/show/7363?output=omeka-xml" accessDate="2026-04-19T08:31:13+00:00">
  <fileContainer>
    <file fileId="7363">
      <src>https://www.socictopen.socict.org/files/original/826d38dab46bf71c5a898cc67fd78510.pdf</src>
      <authentication>149d920ecca19da71d938f92ea2c13c5</authentication>
    </file>
  </fileContainer>
  <collection collectionId="1">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1">
                <text>Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2">
                <text>Dominio científico: Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="64653">
              <text>Airport Landside Sustainable Capacity and Level of Service of Terminal Functional Subsystems</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="64654">
              <text>Paola Di Mascio, Laura Moretti, Massimiliano Piacitelli</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="64655">
              <text>The airport terminal is a complex building composed of many functional subsystems dimensioned to host passenger traffic, considering an appropriate level of service (LoS). The most widely known method to assess the LoS and design the terminal areas is the Airport Development Reference Manual by the International Air Transport Association (IATA). Based on this, a calculation tool in Microsoft Excel® was implemented to assess the capacity and dimension of the facilities for each functional subsystem of the terminal. The tool, composed of nine correlated spreadsheets, is a useful model to design new structures, evaluate the LoS currently offered, plan interventions, and face the new rules of passenger distancing due to the COVID-19 emergency. An international airport terminal with 20 million/year including Schengen and extra-Schengen passengers was studied. The LoS of the terminal subsystems was assessed and the areas needed for each subsystem were calculated. In the analyzed case study, most subsystems (departure hall, check-in, boarding gates, baggage claim, and arrival halls) were over-designed, according to the definition of the IATA LoS. This means that available spaces for queues and holding are sufficiently large to easily face the new rules of social distancing for passengers due to the recent COVID-19 emergency.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="64656">
              <text>2020</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="64657">
              <text>facilities, Level of Service (LOS), landside capacity, functional subsystems requirements, typical peak hour passenger (TPHP), COVID-19 emergency distancing rules</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="64658">
              <text>10.3390/su12218784</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="64659">
              <text>Biotemas</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="64660">
              <text>Universidade Federal de Santa Catarina</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="64661">
              <text>Environmental effects of industries and plants, Renewable energy sources, Environmental sciences</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
