<?xml version="1.0" encoding="UTF-8"?>
<!-- Y U make failed to load external entity "http://xmlresume.sourceforge.net/dtd/resume.dtd" errors... -->
<!-- DOCTYPE resume PUBLIC "-//Sean Kelly//DTD Resume 1.5.1//EN" "http://xmlresume.sourceforge.net/dtd/resume.dtd" -->
<resume xmlns="http://xmlresume.sourceforge.net/resume/0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <header>
    <name>
      <firstname>Aaron</firstname>
      <middlenames>Straup</middlenames>
      <surname>Cope</surname>
    </name>
    <birth>
      <date>
        <dayOfMonth>09</dayOfMonth>
        <month>12</month>
        <year>1971</year>
      </date>
    </birth>
    <contact>
      <email>resume@aaronstraupcope.com</email>
      <url>http://www.aaronstraupcope.com/</url>
    </contact>
  </header>
  <objective>
    <para>I have worked at <link href="https://www.flickr.com">Flickr</link> helping to build and nuture the beautiful monster that it became, made pretty maps at <link href="http://www.stamen.com/">Stamen Design</link>, re-opened the <link href="https://www.cooperhewitt.org/">Smithsonian Design Museum</link> re-imagining what it means for a museum to hold hands with the Internet and built a high-quality, openly-licensed <link href="https://www.whosonfirst.org/">gazetteer of all the places</link> in the world at <link href="https://www.mapzen.com/">Mapzen</link>. In my current role at the <link href="http://sfomuseum.org/">San Francisco International Airport Museum</link> I am working to develop a robust and sustainable technological practice to meet the needs and the constraints of both the cultural heritage and public sectors.</para>
    <para>The promise of the Internet is to be a bridge for cross-pollinating peoples, ideas and communities. I am looking for opportunities to design and build the tools that will continue to realize the idea of the network as a public good.</para>
  </objective>
  <skillarea>
    <title>Core Competencies</title>
    <skillset>
      <title>Programming</title>
      <skill>Go</skill>
      <skill>Python</skill>
      <skill>PHP</skill>
      <skill>Swift</skill>      
      <skill>JavaScript</skill>
      <skill>Perl</skill>
      <skill>Java</skill>
    </skillset>
    <!--
    <skillset>
      <title>System administration</title>
      <skill>BSD/Linux, Apache/nginx, Elasticsearch/Solr, MySQL/Postgres, PostGIS, AWS</skill>
    </skillset>
    -->
    <skillset>
      <title>Languages</title>
      <skill>English</skill>
      <skill>French</skill>
    </skillset>
  </skillarea>
  <history>
    <job>
      <jobtitle>Head of Internet Typing</jobtitle>
      <employer>
        <link href="https://sfomuseum.org/">San Francisco International Airport (SFO) Museum</link>
      </employer>
      <location>
        <city>San Francisco</city>
        <state>California</state>
        <country>U.S.A.</country>
      </location>
      <period>
        <from>
          <date>
            <year>2018</year>
          </date>
        </from>
        <to>
	  <present />
        </to>
      </period>
      <description>
	<para>Lead developer and architect for a project to consider what it means for a museum in an airport, an airport with over 58 million visitors in 2019, to operate in a world where (almost) everyone is connected to the internet and to learn what are the opportunities and responsibilities, as a cultural heritage organization, to everyone who passes through SFO equipped with curiosity and a computer connected to the internet.</para>
	<para>Although the museum has a long history of self-sufficiency in traditional museum-related operations it has lacked equivalent digital skills relying instead on third-parties and outside vendors to maintain its online presence. My role has been to develop the infracsture and practices necessary for the museum to take ownership of its digital needs and desires (past, present and future) while still operating within the constraints of a cultural heritage organization and local government.</para>
	<para>These efforts have been documented in detail on the <link href="https://millsfield.sfomuseum.org/blog/">Mills Field weblog</link>. These include:</para>	
      </description>
      <projects>
	<project>Designing, building and maintaining the <link href="https://millsfield.sfomuseum.org/wayfinding/">SFO Museum Wayfinding System</link>, a serverless interactive system to allow passengers to determine a route between any two points at SFO and to see related Museum programming close to those routes. Routes can also be derived by flight number or by scanning a boarding pass using an on-device, privacy-preserving barcode reader. Individual routes, and associated contemporary and historic Museum programming, can be delivered to passengers as customized PDF or EPUB publications. The Wayfinding system was developed to be both a practical resource to help passngers travel through the SFO terminal complex but also as a means to help foster an understanding of the breadth and history of SFO Museum's activities at the airport over time.</project>
	<project>Designing, building and maintaining the <link href="https://collection.sfomuseum.org/">SFO Museum Aviation Collection website</link>, the online catalog of the SFO Museum Aviation Museum and Library Collection. This website is the public face of the museum's permanent aviation collection of 140, 000 objects and the nucleus of second and third order features and projects to be developed around the collection.</project>
	<project>Designing, building and maintaining the <link href="https://www.sfomuseum.org/about/blog/interactive-historic-maps-sfo-1930-2021">Interactive Historic Maps of SFO</link> installation in the Terminal 2 SkyTerrace Observation Deck. An interactive map installation that allows visitors to view the history of SFO by browsing over three dozen aerial maps from 1930 to 2021. Originally designed as a touch-based interactive application to work entirely offline, it was updated in 2020 to allow visitors to control the map using their personal mobile devices. The installation displays a QR code that a visitor can scan which will launch a “controller” application that relays instructions from their mobile device to the application. This work was the subject of the essay "Fast &amp; Cheap, Stable &amp; Reusable: Reimagining Touch-based Interactive Installations at SFO Museum during the COVID-19 Pandemic", published in the Spring 2023 issue of AAM's <link href="https://www.name-aam.org/exhibition_spring-2023">National Association for Museum Exhibitions</link> journal.</project>		
	<project>Designing, building and maintaining the <link href="https://millsfield.sfomuseum.org/">Mills Field website</link> which acts as a public-facing proving-ground for all present and future projects including: Improving and broadening the reach of all collections-related materials, cataloging and documenting past museum activities, modeling the airport's physical geography over time, interface and interaction experiments and public and private application programming interfaces (API).</project>
	<project>Building the infrastructure for the museum's <link href="https://millsfield.org/map">online mapping efforts</link> including sourcing historical maps from the airport GIS department to producing and hosting its own contemporary basemaps.</project>
	<project>An <link href="https://millsfield.sfomuseum.org/blog/tags/iiif">open source, and serverless, image processing workflow</link> for creating mulitiple derivative image sizes in additional to tiled and zoomable images for a variety of sources including the museum collection and its social media effort.</project>		
	<project>Developing the workflow to catalog <link href="https://millsfield.sfomuseum.org/blog/tags/flightdata">historical and contemporary flight data</link> (2007 - present) at SFO integrating that data with the museum's own collection.</project>
	<project>Designing and developing secure, sustainable and low-maintenance interactive applications around the museum's collection that can be deployed throughout the airport terminals.</project>
	<project>Working with both the Airport Commission and City of San Francisco IT departments to integrate secure credentialing for museum-related websites and services.</project>		
      </projects>
    </job>
    <job>
      <jobtitle>Editor at Large – Creator, Architect and Head of Engineering for Who's On First (WOF)</jobtitle>
      <employer>
        <link href="https://www.mapzen.com/">Mapzen</link>
      </employer>
      <location>
        <city>San Francisco</city>
        <state>California</state>
        <country>U.S.A.</country>
      </location>
      <period>
        <from>
          <date>
            <year>2015</year>
          </date>
        </from>
        <to>
          <date>
            <year>2017</year>
          </date>
        </to>
      </period>
      <description>
        <para>Creator, Architect and Head of Engineering for Who's On First (WOF), an openly licensed gazetteer of all the places and all their metadata in the world, ranging from continents to neighbourhoods and venues. WOF was published as a public resource and a series of API-based services and used internally by a variety of Mapzen services including Search (geocoding) and Tiles.</para>
	<para>The goal of WOF is to provide high-quality and openly licensed location data with global coverage specifically designed for use with a broad range of applications, datastores and programming languages, while ensuring long-term durability and portability of both the data and the services.</para>
	<para>In January 2018, Mapzen announced that it would cease operations. WOF <link href="https://www.whosonfirst.org/blog/2018/01/02/chapter-two/">continues to operate</link> as a community-driven open-data and open-source project at <link href="https://www.whosonfirst.org/">whosonfirst.org</link>. All of the data and source code continues to be developed and distributed through the <link href="https://github.com/whosonfirst-data">whosonfirst-data</link> and <link href="https://github.com/whosonfirst">whosonfirst</link> GitHub organizations, respectively.</para>
	<para>To date approximately <link href="https://www.whosonfirst.org/blog/">60, 000 words of theory and practice</link> have been written about the project on the Who's On First weblog. A good introduction is the 2016 talk titled <link href="https://www.whosonfirst.org/blog/2016/08/15/mapping-with-bias/">Mapping With Bias</link> and a detailed discussion of the project's goals and motivations is the 2015 blog post <link href="https://www.whosonfirst.org/blog/2015/08/18/who-s-on-first/">Who's On First</link>.</para>
      </description>
      <projects>
	<project>Designed the <link href="https://www.whosonfirst.org/blog/2015/08/18/who-s-on-first/">overall data model and architecture</link> for the project.</project>
	<project>Designed, built and maintained public-facing services related to WOF including the <link href="https://www.whosonfirst.org/blog/2015/09/28/spelunker-jumping-into-who-s-on-first/">Spelunker</link> and the <link href="https://www.whosonfirst.org/2017/04/04/whosonfirst-api/">API</link> and the initial version of the WOF editorial tools (code named "Boundary Issues")</project>
	<project>Designed, built and maintained all of the databases, deploy tools and software libraries for both public-facing and internal editorial workflows. Software was purposefully written in a variety of languages including <link href="https://github.com/whosonfirst?language=go">Go</link>, <link href="https://github.com/whosonfirst?language=python">Python</link>, <link href="https://github.com/whosonfirst?language=php">PHP</link> and <link href="https://github.com/whosonfirst?language=javascript">JavaScript</link> specifically to ensure that design decisions around the data modeling did not encode the biases of any one language or toolset.</project>
	<project>Managed the engineering team, contractors and oversaw day-to-day technology decisions.</project>
      </projects>
    </job>
    <job>
      <jobtitle>Head of Engineering, Digital and Emerging Media</jobtitle>
      <employer>
        <link href="http://www.cooperhewitt.org/">Cooper Hewitt Smithsonian Design Museum</link>
      </employer>
      <location>
        <city>New York City</city>
        <state>New York</state>
        <country>U.S.A.</country>
      </location>
      <period>
        <from>
          <date>
            <year>2012</year>
          </date>
        </from>
        <to>
          <date>
            <year>2015</year>
          </date>
        </to>
      </period>
      <description>
        <para>Head of engineering and technical architect for all public facing and internal digital initiatives related to the re-opening of the Smithsonian Cooper Hewitt Design Museum in 2015. This work was documented in The Atlantic magazine's 2015 <link href="https://www.theatlantic.com/technology/archive/2015/01/how-to-build-the-museum-of-the-future/384646/">The Museum of the Future Is Here</link> profile and culminated with <link href="https://collection.cooperhewitt.org/pen/">The Pen</link> an NFC-enabled stylus, custom designed and manufactured by the museum, given to every museum visitor.</para>
	<para>The Pen allows visitors to collect objects on display and retrieve them post-visit as well as produce new works on multi-user interactive tables located through the museum. It works in concert with purpose-built API designed and maintained by the museum and enables both internal and third-party in-gallery experiences. Launched in March of 2015, The Pen has been in continuous use since then. As of <link href="https://collection.cooperhewitt.org/stats/">January 2018</link> it has been given out to 350, 000 visitors; used to collect objects 14 million times; and used to create over 300, 000 designs.</para>
	<para>The technical, manufacturing and institutional challenges (and successes) that were prompted The Pen are discussed at length in <link href="http://www.aaronland.info/weblog/2015/04/10/things/#mw2015">Strategies against architecture: interactive media and transformative technology at Cooper Hewitt</link>, a formal paper presented at the 2015 Museums and the Web conference and <link href="http://www.aaronland.info/weblog/2016/03/09/osha/#bespokiness">The Pendulum of Bespokiness</link>, a presentation delivered at the 2016 Bosch Connected Experience conference.</para>
      </description>
      <projects>
        <project>
	  Designed, built and maintained the <link href="https://collection.cooperhewitt.org.">Cooper Hewitt collections website</link> and <link href="https://labs.cooperhewitt.org/2014/the-api-at-the-center-of-the-museum/">API</link> which acts as a unified interface for all public-facing, internal and third-party integrations with the museum collection, including the Pen and features like <link href="http://labs.cooperhewitt.org/2013/giv-do/">search by colour</link>. The Collections website won the Best Research/Collections Website award at the 2013 Museums and the Web conference as well as the award for best Applications and API website at the 2013 American Alliance of Museums conference.
	</project>
        <project>
	  Co-curator for the Smithsonian's first acquisition of code: <link href="http://www.cooperhewitt.org/object-of-the-day/2013/08/26/planetary-collecting-and-preserving-code-living-object">Planetary</link>, an interactice music player for the iPad. <link href="http://labs.cooperhewitt.org/2013/pandas-press-planetary/">(Complete press coverage of the acquisition is listed here.)</link>
	</project>
	<project>Acted as technical liason with the Smithsonian's Office of the Chief Information Officer (OCIO) on all matters relating to the Cooper Hewitt's digital and exhibition infrastructure.</project>
	<project>Managed the engineering team and oversaw day-to-day technology decisions.</project>
      </projects>
    </job>
    <job>
      <jobtitle>Internet Typist (and general layabout)</jobtitle>
      <employer/>
      <location>
        <city>San Francisco</city>
        <state>California</state>
        <country>U.S.A.</country>
      </location>
      <period>
        <from>
          <date>
            <year>2012</year>
          </date>
        </from>
        <to>
          <date>
            <year>2012</year>
          </date>
        </to>
      </period>
      <description>
        <para>Combination self-employed and self-imposed sabbatical spent implementing and investigating the practice of archiving and of running shadow copies of popular social networking websites.</para>
      </description>
      <projects>
        <project><link href="http://www.aaronland.info/weblog/2011/10/14/pixelspace/#parallel-flickr">Parallel Flickr</link> — a tool for backing up your Flickr photos and generating a database backed website that honours the viewing permissions you've chosen on Flickr. It was presented at the Internet Archive's 2012 <link href="http://www.aaronland.info/weblog/2012/02/14/incentivize/#pda2012">Personal Digital Archiving conference</link>.</project>
        <project><link href="http://nearfuturelaboratory.com/2012/01/22/privatesquare/">Privatesquare</link> — a "looking-glass archive" web application to record and manage a private database of foursquare check-ins with the option of recording them in a public service after the fact.</project>
        <project><link href="http://www.aaronland.info/weblog/2012/04/02/haystack/#parallel-ogram">Parallel-ogram</link> — a simple web application to create a local backup of Instagram photos and "likes" and to make that archive a living, breathing website of its own.</project>
      </projects>
    </job>
    <job>
      <jobtitle>Design Technologist</jobtitle>
      <employer>
        <link href="http://www.stamen.com/">Stamen Design</link>
      </employer>
      <location>
        <city>San Francisco</city>
        <state>California</state>
        <country>U.S.A.</country>
      </location>
      <period>
        <from>
          <date>
            <year>2009</year>
          </date>
        </from>
        <to>
          <date>
            <year>2011</year>
          </date>
        </to>
      </period>
      <description>
        <para>Senior developer responsible for taming source data and designing and implementing technical systems for a wide variety of clients and research projects. Also, maps.</para>
      </description>
      <projects>
        <project>
	  <link href="http://sealevel.climatecentral.org/">Surging Seas</link> (2012) — a project with <link href="http://www.climatecentral.org/">Climate Central</link> to visualize the effects of sea-level rise and storm surges in the United States.
	</project>
        <project>
	  <link href="http://mapequalsyes.stamen.com/">map=yes</link> (2011) — a project with <link href="http://mapquest.com/">MapQuest</link> to demonstrate what their mapping APIs, and commitment to the OpenStreetMap project, affords to developers and designers alike.</project>
        <project><link href="http://prettymaps.stamen.com/">prettymaps</link> (2010) — an experimental interactive map composed of multiple freely available, community-generated data sources designed to explore and celebrate the edges of what is possible in web-based mapping.</project>
        <project><link href="http://city.stamen.com/cheerios/">Cheerio Maps</link> (2010) — an experimental map to visualize housing data in the San Francisco Bay Area.</project>
      </projects>
    </job>
    <job>
      <jobtitle>Lead Engineer</jobtitle>
      <employer>
        <link href="http://www.flickr.com/">Flickr</link>
      </employer>
      <location>
        <city>San Francisco</city>
        <state>California</state>
        <country>U.S.A.</country>
      </location>
      <period>
        <from>
          <date>
            <year>2004</year>
          </date>
        </from>
        <to>
          <date>
            <year>2009</year>
          </date>
        </to>
      </period>
      <description>
        <para>Lead engineer for the <link href="http://www.flickr.com/">Flickr</link> photo sharing/management web application; designed, implemented and maintained the geotagging and machinetag infrastructure; primary contact for security issues; primary contact for integration projects with its parent company Yahoo!.</para>
      </description>
      <projects>
        <project><link href="http://blog.flickr.net/en/2009/09/14/galleries-unleash-your-inner-curator/">Galleries</link> (2009) — a way for users to curate up to 18 public photos or videos from other Flickr users into one place around a theme, an idea or "just because"; galleries were a way to encourage Flickr users to try and see their time and involvements on the site as something other than self-promotion or collecting view counts.</project>
        <project><link href="http://code.flickr.com/blog/2008/10/30/the-shape-of-alpha/">Flickr Shapefiles</link> (2008) — we asked the question: "If we plotted all the geotagged photos associated with a particular location, would we have enough data to generate a mostly accurate contour of that place? Not a perfect representation, perhaps, but something more fine-grained than a bounding box." It turns out we did!</project>
        <project><link href="http://www.flickr.com/groups/api/discuss/72157594497877875/">Machine tags</link> (2007) — a lightweight and easy means for users to add extra semantics to their tags and to use those tags as a kind of key in to third-party services; there are currently over 2M tags with <link href="http://foursquare.com/">foursquare</link> venue IDs as well as many other smaller bespoke projects.</project>
        <project><link href="http://www.flickr.com/map">Geotagging</link> (2006) — the ability for users to geotag their photos; there were 1M geotagged photos added in the first 24 hours and today there are over 300M geotagged photos.</project>
        <project>Just keeping the site up (2005) — it was a very busy year.</project>
      </projects>
    </job>
    <!--
    <job>
      <jobtitle>Lead developer / system administrator</jobtitle>
      <employer>Vineyard.NET Inc.</employer>
      <location>
        <city>Vineyard Haven</city>
        <state>Massachusetts</state>
        <country>U.S.A</country>
      </location>
      <period>
        <from>
          <date>
            <year>2001</year>
          </date>
        </from>
        <to>
          <date>
            <year>2004</year>
          </date>
        </to>
      </period>
      <description>
        <para>Designed and built internal and customer-facing account management tools; Designed, built and maintained custom web
      applications for real-estate property management; Oversaw all web-related infrastructure.</para>
      </description>
      <projects/>
    </job>
    -->
  </history>
  <activities>
    <activity>
      <title>Public speaking</title>
      <period>
        <from>
          <date>
            <year>2007</year>
          </date>
        </from>
        <to>
          <present/>
        </to>
      </period>
      <description>
        <para>I have been <link href="http://www.aaronland.info/talks/">speaking publicly since 2007</link> on a variety of personal and work-related subjects including Flickr, maps and cultural heritage. I have been a frequent speaker at the <link href="http://www.museumsandtheweb.com/">Museums and the Web</link>, <link href="https://mcn.edu/">Museum Computer Network</link>, <link href="http://stateofthemap.org/">Openstreetmap State of the Map</link> and <link href="http://nacis.org/">North American Cartographic Information Socirty (NACIS)</link> conferences.</para>
        <para>A complete list of talks is available at <link href="https://www.aaronland.info/talks/">https://www.aaronland.info/talks</link></para>
      </description>
    </activity>
    <activity>
      <title>go-iiif</title>
      <date>
	<from>
          <year>2015</year>
	</from>
	<to>
	  <present />
	</to>
      </date>
      <description>
	<para><link href="https://thisisaaronland.github.io/go-iiif/">go-iiif</link> is a fork of the <link href="https://github.com/greut/iiif">iiif</link> package that moves all of the processing logic for the <link href="http://iiif.io/api/image/">IIIF Image API</link> in to discrete Go packages and defines source, derivative and graphics details in a JSON config file. There is an additional caching layer for both source images and derivatives.</para>
	</description>
    </activity>
    <activity>
      <title>Brooklyn Integers</title>
      <date>
	<from>
          <year>2012</year>
	</from>
	<to>
	  <present />
	</to>
      </date>
      <description>
	<para><link href="http://brooklynintegers.com/">Artisanal Integers as a service</link>. A very elaborate joke, but a useful one. The canonical text on artisanal integers is the <link href="https://www.aaronland.info/weblog/2012/12/01/coffee-and-wifi/#timepixels">time pixels</link> keynote from the 2012 <link href="http://www.ndf.org.nz/">New Zealand National Digital Forum</link> but a more approachable introduction is neverendingbook.org's <link href="http://www.neverendingbooks.org/artisanal-integers">artisanal integers</link>.</para>
      </description>
    </activity>
    <!--
    <activity>
      <title>prettymaps, Talk To Me exhibition (MoMA)</title>
      <date>
        <year>2011</year>
      </date>
      <description>
        <para>In 2011, the prettymaps project was <link href="http://www.moma.org/interactives/exhibitions/2011/talktome/objects/146211/">included</link> in the Museum of Modern Art's <link href="http://www.moma.org/visit/calendar/exhibitions/1080">Talk to Me: Design and the Communication between People and Objects</link> exhibition, in New York City. This was very exciting.</para>
      </description>
    </activity>
    <activity>
      <title>Advisory Board, Built Works Registry</title>
      <period>
        <from>
          <date>
            <year>2011</year>
          </date>
        </from>
        <to>
          <date>
            <year>2013</year>
          </date>
        </to>
      </period>
      <description>
        <para>In 2011 I was invited to be a member of the advisory board for the <link href="https://builtworksregistry.wordpress.com/">Built Works Registry</link>, a joint endeavor of the Avery Architectural &amp; Fine Arts Library at Columbia University, ARTstor and Getty Research Institute funded by a three-year National Leadership Grant from the Institute of Museum and Library Services.</para>
      </description>
    </activity>
    <activity>
      <title>prettymaps, 20x200 prints</title>
      <period>
        <from>
          <date>
            <year>2010</year>
          </date>
        </from>
        <to>
          <present/>
        </to>
      </period>
      <description>
        <para>Starting in 2010, the prettymaps project was selected by the <link href="http://20x200.com/">20x200</link> project for a series of limited-edition prints. To date <link href="http://www.20x200.com/artist/210-aaron-straup-cope">editions for ten cities</link> have been printed.</para>
      </description>
    </activity>
    <activity>
      <title>The Papernet</title>
      <period>
        <from>
          <date>
            <year>2007</year>
          </date>
        </from>
        <to>
          <present/>
        </to>
      </period>
      <description>
        <para><link href="http://www.aaronland.info/papernet/">The Papernet</link> is the name for an on-going investigation of how and why and where to bridge the digital and analog world. It was first introduced at the 2007 XTech conference, in Paris.</para>
      </description>
    </activity>
    <activity>
      <title>Aaron's New York Times Widgets</title>
      <period>
        <from>
          <date>
            <year>2002</year>
          </date>
        </from>
        <to>
          <date>
            <year>2010</year>
          </date>
        </to>
      </period>
      <description>
        <para><link href="http://www.aaronland.info/nytimes/">Tools, and visualizations, for data-mining the New York Times.</link> This project was stopped with the introduction of the New York Time's "pay-wall".</para>
      </description>
    </activity>
    -->
    <activity>
      <title>The Mirror Project</title>
      <period>
        <from>
          <date>
            <year>2001</year>
          </date>
        </from>
        <to>
	  <present />
        </to>
      </period>
      <description>
        <para><link href="http://www.mirrorproject.com/">The Mirror Project</link> was one of the earliest community-driven photo-sharing websites to promote built to encourage and showcase "adventures in reflective surfaces". In a world before selfies...
	</para>
      </description>
    </activity>
  </activities>
  <academics>
    <degrees>
      <degree>
        <level>Studies</level>
        <major>Studio arts</major>
        <period>
          <from>
            <date>
              <year>1993</year>
            </date>
          </from>
          <to>
            <date>
              <year>1997</year>
            </date>
          </to>
        </period>
        <institution>
          <link href="http://www.nscad.ca/">Nova Scotia College of Art and Design</link>
        </institution>
        <location>
          <city>Halifax</city>
          <province>Nova Scotia</province>
          <country>Canada</country>
        </location>
      </degree>
    </degrees>
  </academics>
  <pubs>
    <pub>
      <artTitle>
	<link href="https://www.name-aam.org/exhibition_spring-2023">Fast &amp; Cheap, Stable &amp; Reusable: Reimagining Touch-based Interactive Installations at SFO Museum during the COVID-19 Pandemic</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher> exhibition (AAM National Association of Museum Exhibitions)</publisher>
      <date>
	<year>2023</year>
      </date>
    </pub>
    <pub>
      <artTitle>
	<link href="https://mw20.museweb.net/paper/capacity-planning-for-meaning/">Capacity Planning for Meaning</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher>MW2020: Museums and the Web 2020</publisher>
      <date>
        <year>2020</year>
      </date>
    </pub>
    <pub>
      <artTitle>
	<link href="https://mw19.mwconf.org/paper/mapping-space-time-and-the-collection-at-sfo-museum/">Mapping Space, Time, and the Collection at SFO Museum</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher>MW2019: Museums and the Web 2019</publisher>
      <date>
        <year>2019</year>
      </date>
    </pub>    
    <pub>
      <artTitle>
        <link href="http://onlinelibrary.wiley.com/doi/10.1111/cura.12118/abstract">Strategies against architecture: interactive media and transformative technology at Cooper Hewitt.</link>
      </artTitle>
      <author>Seb Chan</author>
      <author>Aaron Straup Cope</author>
      <publisher>Curator, The Museum Journal</publisher>
      <date>
        <year>2015</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="http://mw2015.museumsandtheweb.com/paper/strategies-against-architecture-interactive-media-and-transformative-technology-at-cooper-hewitt/">Strategies against architecture: interactive media and transformative technology at Cooper Hewitt.</link>
      </artTitle>
      <author>Seb Chan</author>
      <author>Aaron Straup Cope</author>
      <publisher>MW2015: Museums and the Web 2015</publisher>
      <date>
        <year>2015</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="http://mw2014.museumsandtheweb.com/paper/collecting-the-present-digital-code-and-collections/">Collecting the present: digital code and collections</link>
      </artTitle>
      <author>Seb Chan</author>
      <author>Aaron Straup Cope</author>
      <publisher>MW2014: Museums and the Web 2014</publisher>
      <date>
        <year>2014</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="https://www.museumsandtheweb.com/mw2012/papers/archiving_flickr_and_other_websites_of_interes.html">Archiving Flickr and Other Websites of Interest to Museums
</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <author>Ryan Donahue</author>
      <publisher>MW2012: Museums and the Web 2012</publisher>
      <date>
        <year>2012</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="https://www.museumsandtheweb.com/mw2012/programs/buildingyes.html">building=yes</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher>MW2012: Museums and the Web 2012</publisher>
      <date>
        <year>2012</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="https://builtworksregistry.wordpress.com/imagining-the-built-works-registry-by-aaron-straup-cope-christine-kuan/">Imagining the Built Works Registry</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <author>Christine Kuan</author>
      <date>
        <year>2011</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="http://www.museumsandtheweb.com/mw2010/papers/cope/cope.html">Buckets and Vessels</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher>Museums and the Web 2010: Proceedings. Toronto: Archives &amp; Museum Informatics</publisher>
      <date>
        <year>2010</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="http://www.museumsandtheweb.com/mw2009/abstracts/prg_335001944.html">The Interpretation of Bias (and the bias of interpretation)</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher>Museums and the Web 2009: Proceedings. Toronto: Archives &amp; Museum Informatics</publisher>
      <date>
        <year>2009</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="http://www.museumsandtheweb.com/mw2008/papers/straup_cope/straup_cope.html">The API As Curator</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher>Museums and the Web 2008: Proceedings. Toronto: Archives &amp; Museum Informatics</publisher>
      <date>
        <year>2008</year>
      </date>
    </pub>
    <pub>
      <artTitle>
        <link href="http://www.xml.com/pub/a/2005/02/16/edfg.html">Eat Drink Feel Good Markup Language</link>
      </artTitle>
      <author>Aaron Straup Cope</author>
      <publisher>XML.com (O'Reilly Media Inc.)</publisher>
      <date>
        <year>2005</year>
      </date>
    </pub>
  </pubs>
  <misc>
    <para>Code samples and current projects are available for review on the <link href="https://github.com/aaronland">@aaronland</link> and <link href="https://github.com/whosonfirst">@whosonfirst</link> and <link href="https://github.com/sfomuseum">@sfomuseum</link> GitHub organizations. Older code is available for review on the <link href="https://www.github.com/straup">@straup</link> and <link href="https://www.github.com/thisisaaronland/">@thisisaaronland</link> GitHub accounts.</para>
    <para>
      <link href="http://www.aaronland.info/weblog/">I have been maintaining a personal weblog since 1999.</link>
    </para>
    <para>This document is available in the following formats :
     <link href="http://www.aaronstraupcope.com/resume/en/aaronstraupcope-resume-en.txt">Plain-text</link>, 
     <link href="http://www.aaronstraupcope.com/resume/en/aaronstraupcope-resume-en.html">HTML</link>,
     <link href="http://www.aaronstraupcope.com/resume/en/aaronstraupcope-resume-en.pdf">PDF</link>
     and
     <link href="http://www.aaronstraupcope.com/resume/en/aaronstraupcope-resume-en.xml">XML</link>.

     The code used to generate these documents is available as <link href="https://github.com/straup/xmlresume-tools/">open source software</link>.
    </para>
  </misc>
  <r:referees xmlns:r="http://xmlresume.sourceforge.net/resume/0.0">
    <!--Available upon request.-->
  </r:referees>
  <lastModified>
    <date>
      <month>August</month>
      <year>2023</year>
    </date>
  </lastModified>
</resume>
