<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="40" 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://com395.omeka.chass.ncsu.edu/items/show/40?output=omeka-xml" accessDate="2026-07-01T15:35:58+00:00">
  <fileContainer>
    <file fileId="40">
      <src>https://com395.omeka.chass.ncsu.edu/files/original/2fbf7c2827634cf41234fcb949bce2a3.JPG</src>
      <authentication>c6bc0d3ebd1bd9a14326209c3e6b5c8e</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="209">
                <text>Everyday Objects</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="210">
                <text>Week One and Two COM 395 Collection</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="211">
                <text>This is the collection from week one and two, which are miscellaneous items that students photographed and wrote about.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="212">
                <text>Hal Meeks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="213">
                <text>Students from COM 395</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214">
                <text>CC Licensed</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="215">
                <text>Digital Images</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="6">
    <name>Still Image</name>
    <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</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="301">
              <text>Farmacy "Green Clean" Makeup Cleansing Balm</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="302">
              <text>Cosmetics &amp; Packaging</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="303">
              <text>So, one of the jobs I have is that I'm a cashier at Sephora. With this, it means that several days a week I'm in a full face of makeup for 6+ hours at a time. This also means that I need a good way to take off said makeup. This balm is one of the best I've used, but I'm not even here to talk about the formulation of the product, but rather the physicality of the packaging.&#13;
As shown in the picture, there are 3 main pieces that make this product. The lid, the tub, and the plastic plate that sits between the two and holds the scoop for the balm. This is really clever design because it doesn't add anything to the product in terms of having to deal with another part that came along side it. This is set within the packaging so it's easy to keep track of and it fits nicely within it. This scoop is also very helpful from a sanitation standpoint. Dipping your fingers in the tub to get the product out isn't the most sanitary way to use it, especially if you're a makeup artist who has to use it on multiple people or if maybe you and your roommate share it. The scoop is also wide enough to get a substantial amount of product on it, and the square shape aids that as well. In my experience, rounded scoops in that scale don't do as good of a job as a flat edge.&#13;
The packaging is sturdy plastic which prevents it from being broken or flattened in a cosmetics case or by dropping it. And since the jar is cylindrical, it's easy to keep a good grip.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="304">
              <text>Chloe Bain</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="305">
              <text>1/19/20</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
