<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="110" 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/110?output=omeka-xml" accessDate="2026-10-08T22:00:42+00:00">
  <fileContainer>
    <file fileId="107">
      <src>https://com395.omeka.chass.ncsu.edu/files/original/0d62d0e6b84cf527f71672233e2719ae.png</src>
      <authentication>3dd026229b72ec46ea3c1924346cb8e7</authentication>
    </file>
  </fileContainer>
  <collection collectionId="5">
    <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="684">
                <text>Motion</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="685">
                <text>Video, Film, Games</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="686">
                <text>This is a category that is a bit odd. We are looking at motion media pieces as designed objects. This requires thinking less about just the dialog and actors, and instead treating it's totality as designed experience.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="687">
                <text>Students of COM/ENG 395</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="688">
                <text>Students of COM/ENG 385</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="689">
                <text>Students of COM/ENG 385</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="760">
              <text>Goodfella's Tracking Shot</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="761">
              <text>Motion</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="762">
              <text>This image is a still from the most famous scene in Martin Scorsese's Goodfellas. This scene is when Henry Hill takes his date through the back of the Copacabana nightclub to their table, bypassing the long line in the front of the club. According to the film's producer, Irwin Winkler, the scene "was a way to have Henry Hill not only impress his date, Karen, but to show the audience why the world of Goodfellas was so attractive and glamorous."&#13;
&#13;
I consider this scene to be a good example of motion because it is what's called a tracking shot. The scene was one long, continuous take that snaked through an entire night club as though you, too, were following Hill and his date. Scorsese could have broken up the shot, but he didn't to purposefully convey the allure of being mobbed up at that time. The Copa shot was neat because the audience was literally dropped in the middle of the action, and were expected to flow along. &#13;
</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="763">
              <text>Martin Scorsese </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="764">
              <text>Liz Risko</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="765">
              <text>02/09/20</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
