<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="3289" 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://repositorio.febab.org/items/show/3289?output=omeka-xml" accessDate="2026-11-13T05:12:39+00:00">
  <fileContainer>
    <file fileId="2371">
      <src>https://repositorio.febab.org/files/original/24/3289/2324-2341-1-PB.pdf</src>
      <authentication>368c3d7957c0903d679e13743af7cae6</authentication>
    </file>
  </fileContainer>
  <collection collectionId="24">
    <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="26064">
                <text>CBBD - Edição: 28 - Ano: 2019 (Vitória/ES)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26065">
                <text>Biblioteconomia&#13;
Documentação&#13;
Ciência da Informação</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26066">
                <text>FEBAB</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="26067">
                <text>2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26068">
                <text>Português</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26069">
                <text>Evento</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="26070">
                <text>Vitória (Espírito Santo)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="8">
    <name>Event</name>
    <description>A non-persistent, time-based occurrence. Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, and responsible agents associated with an event. Examples include an exhibition, webcast, conference, workshop, open day, performance, battle, trial, wedding, tea party, conflagration.</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="38204">
              <text>Mapeamento de processos: uma experiência nas bibliotecas do IFSP</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="38205">
              <text>Angela Halen Claro Franco</text>
            </elementText>
            <elementText elementTextId="38206">
              <text>Felipe Augusto Arakaki</text>
            </elementText>
            <elementText elementTextId="38207">
              <text>Jessica Cristiane Pereira da Silva</text>
            </elementText>
            <elementText elementTextId="38208">
              <text>Rosana da Silva Gomes</text>
            </elementText>
            <elementText elementTextId="38209">
              <text>Greissi Gomes Oliveira</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="38210">
              <text>Vitória (Espírito Santo)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="38211">
              <text>FEBAB</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="38212">
              <text>2019</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="38214">
              <text>Eixo 6: Gestão de bibliotecas</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="38215">
              <text>Objetiva-se relatar a experiência do Instituto Federal de Educação, Ciência e Tecnologia de São Paulo acerca do mapeamento dos processos das suas coordenadorias de bibliotecas. A partir da utilização do método Modelagem de Processos e Negócio e do software FreeMind, elaborou-se a árvore dos processos das bibliotecas da instituição. Obteve-se como resultados a construção de uma árvore de processos com 196 atividades, divididas em três grandes grupos:  realizar a gestão organizacional da biblioteca, gerenciar o acervo da biblioteca e gerenciar a prestação de serviços da biblioteca. Pode-se compreender que o mapeamento dos processos permite conhecer os processos realizados nas bibliotecas do IFSP, apresentando um diagnóstico situacional. Ademais, a elaboração da árvore de processos permite observar a complexidades das atividades realizadas nas bibliotecas, e explicitar a necessidade pela busca da eficácia das mesmas. Tem-se como próximas etapas do trabalho a realização da análise dos processos mapeados e a modelagem dos processos.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="38216">
              <text>Evento</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="67171">
              <text>pt</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
  <tagContainer>
    <tag tagId="17">
      <name>cbbd2019</name>
    </tag>
  </tagContainer>
</item>
