<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="274" 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://cpw.cvlcollections.org/items/show/274?output=omeka-xml" accessDate="2026-06-05T11:57:59+00:00">
  <fileContainer>
    <file fileId="441">
      <src>https://cpw.cvlcollections.org/files/original/d756d4688fe6721b441a1ec8dd636302.pdf</src>
      <authentication>82f966bc32880025e908ed7bc80bf700</authentication>
      <elementSetContainer>
        <elementSet elementSetId="4">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="92">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="5014">
                  <text>The research in this publication was partially or fully funded by Colorado Parks and Wildlife.

Dan Prenzlow, Director, Colorado Parks and Wildlife • Parks and Wildlife Commission: Marvin McDaniel, Chair • Carrie Besnette Hauser, Vice-Chair
Marie Haskett, Secretary • Taishya Adams • Betsy Blecha • Charles Garcia • Dallas May • Duke Phillips, IV • Luke B. Schafer • James Jay Tutchton • Eden Vardy

�Methods in Ecology and Evolution 2016, 7, 499–504

doi: 10.1111/2041-210X.12503

APPLICATION

CPW Photo Warehouse: a custom database to facilitate
archiving, identifying, summarizing and managing photo
data collected from camera traps
Jacob S. Ivan* and Eric S. Newkirk
Colorado Parks and Wildlife, Fort Collins, CO 80526, USA

Summary
1. Contemporary methods for sampling wildlife populations include the use of remotely triggered wildlife cameras (i.e., camera traps). Such methods often result in the collection of hundreds of thousands of photos that must
be identiﬁed, archived, and transformed into data formats required for statistical analyses.
2. CPW Photo Warehouse is a freely available software based in Microsoft AccessÒ that has been customized for
this purpose using Visual BasicÒ for Applications (VBA) code. Users navigate a series of point-and-click menu
items that allow them to input information from camera deployments, automatically import photos (and image
data stored within the photos) related to those deployments, and store data within a relational database. Images
are seamlessly incorporated into the database windows, but are stored separately from the database.
3. The database includes menu options that (i) facilitate identiﬁcation of species within the images, (ii) allow
users to view and ﬁlter any subset of the databased on study area, species, season, etc., and (iii) produce input ﬁles
for common analyses such as occupancy, abundance, density and activity patterns using Programs MARK, PRESENCE, DENSITY and the R packages ‘secr’ and ‘overlap’.
4. Our database makes explicit use of multiple observers, which greatly enhances the eﬃciency and accuracy with
which a large number of photos can be identiﬁed. Modular subsets of the data can be distributed to an unlimited
number of observers on or oﬀ site for identiﬁcation. Modules are then re-incorporated into the database using a
custom import function.

Key-words: camera traps, database, multiple observers, photos, wildlife cameras
Introduction
Ecologists have employed remotely triggered cameras
(camera traps) to sample wildlife for many decades
(Kucera &amp; Barrett 2011). In recent years, however, signiﬁcant technological advances have been made in battery
life, sensor quality, overall reliability and memory card
capacity (Kucera &amp; Barrett 2011) such that camera traps
have become a very eﬃcient, even preferred, means of collecting information on a broad array of taxa including
mammals, birds and herpetofauna. Such information can
be used to assess distribution, abundance and behaviour
to inform conservation and management decisions (Kucera
&amp; Barrett 2011). Accordingly, use of these devices has
erupted. A search of published literature in the Web of
Science database (Thompson Reuters 2015) returned only
six citations for “camera trap” in 2005, 37 in 2010, and
92 in 2014.
A common characteristic of studies that employ camera
traps is the generation of a large quantity of data. Even single surveys or sampling sessions routinely generate hundreds
*Correspondence author. E-mail: Jake.Ivan@state.co.us

of thousands of photos which must be processed and
archived before data can be extracted from them for analyses. At least ﬁve general approaches have been authored for
the sole purpose of handling the large quantity of photographic data generated from research that employs camera
traps. These range from manual organization of photos into
ﬁle structures that can be used by DOS programs to perform
summaries (Renamer + CamTrap, Harris et al. 2010), to
spreadsheet-based applications (Photospread, Kandel et al.
2007; Sundaresan, Riginos &amp; Abelson 2011), to tailored use
of commercial photographic archive systems (e.g., Picasa,
Sundaresan, Riginos &amp; Abelson 2011), and custom relational
desktop databases such as Aardwolf (Krishnappa &amp; Turner
2014) and Camera Base (Tobler 2014). Additionally, sophisticated server-based databases exist that automatically
archive data from numerous projects across multiple jurisdictions (e.g., eMammal, http://emammal.si.edu/; DeskTEAM,
Fegraus et al. 2011). Until recently, these latter developments
required a project to be part of a larger, exclusive monitoring
eﬀort. Both now oﬀer versions of their software that
are available for independent research (the publically available version of DeskTEAM is known as Wild.ID;
http://www.teamnetwork.org/wildlife-monitoring-solutions).

© 2015 The Authors. Methods in Ecology and Evolution published by John Wiley &amp; Sons Ltd on behalf of British Ecological Society.
This is an open access article under the terms of the Creative Commons Attribution-NonCommercial License, which permits use,
distribution and reproduction in any medium, provided the original work is properly cited and is not used for commercial purposes.

�Windows, MacOS
Yes
Unlimited
No
Yes
Yes
Yes
No
Yes
Yes
No
Yes
No
No
Yes15

Operating System
Single, relational platform
Storage capacity
Automatic import3
Assign multiple species
Record individuals
Record ancillary data6
Double observer
Batch ID
Crowd source ID
Record active days9
Filter, query data
Auto-generate input ﬁles
Auto-generate reports
Help

http://www.snapﬁles.com/
downloads/denrenamer/
dldenrenamer.html;
http://esapubs.org/archive/
bulletin/B091/002/
suppl-1.htm
Windows
No
Unlimited
No
No4
No4
No
No
No
No
Yes
No
Yes10
Yes
Yes15

Renamer + CamTrap

Windows
Yes
c. 2,000,0001
Yes
No5
Yes
Sex Only
No
Yes7
No
Yes
Yes
Yes11
Yes
Yes15

http://www.atriumbiodiversity.org/
tools/camerabase/

Camera Base

Windows, MacOS
Yes
Unlimited
Yes
Yes
Yes
Yes
No
Yes
No8
No
Yes
No
Yes14
No

http://sourceforge.net/
projects/aardwolf/

Aardwolf

Windows
Yes
Unlimited
Yes
Yes
Yes
No
No
Yes7
No
Yes
Yes
No
No
Yes15

http://www.
teamnetwork.org/
wildlife-monitoringsolutions

Wild.ID

Windows, MacOS
No
Unlimited
Yes
Yes
Yes
No
Yes
Yes7
No
No
Yes
Yes12
Yes
Yes

http://emammal.
si.edu/

eMammal

Windows
Yes
c. 800,000–2,000,0002
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes13
Yes
Yes16

http://cpw.state.co.us/
learn/Pages/Research
MammalsSoftware.
aspx

CPW Photo Warehouse

2

Assumed based on its use of Microsoft Access, which has a 2,000,000-record limit per table.
Depending on whether the user employs double observers for each photo (c. 800,000) or only a single observer (c. 2,000,000).
3
Photos and associated metadata can be imported to database structure automatically without the need to manually enter or manipulate data.
4
Multiple species or number of individuals can be assigned to each photo if the user copies photos to multiple folders.
5
Multiple species can be assigned to each photo if the user imports photos multiple times, once for each species present.
6
Includes ability to record custom details for each photo such as sex, behaviors, radio collars, tags, etc.
7
Photo data can be auto-ﬁlled within a single photo burst or within a certain period of time of the focal photo but the user cannot auto-ﬁll across bursts or longer (user-deﬁned) periods of time.
8
Authors state that porting the software to a web interface would make this possible– unclear if the functionality is currently available and implemented.
9
Allows users to record and/or manage the days over which each camera was active and operating properly.
10
Software produces input ﬁles for use in Program PRESENCE; limited to a single occasion length (10 days).
11
Software produces input ﬁles for Programs MARK (closed capture), CAPTURE, PRESENCE, R ‘RMark’ (occupancy), DENSITY, and ESTIMATES.
12
Software produces input ﬁles for Program PRESENCE and R ‘unmarked’ and produces output graphs from R ‘overlap’, and R ‘vegan’.
13
Software produces input ﬁles for Programs MARK (closed capture, occupancy), PRESENCE, DENSITY, R ‘secr’, and R ‘overlap’.
14
Basic reports available (total photos, number of photos per camera, total species). More advanced reports require SQL coding.
15
User manual available for download.
16
User manual available for download; context speciﬁc help available within each form.

1

http://infolab.stanford.edu/
� paepcke/shared-documents/
PhotoSpread/

Website

PhotoSpread

Table 1. Comparison of software available for archiving and managing photo data collected from independent camera trap projects

500 J. S. Ivan &amp; E. S. Newkirk

© 2015 The Authors. Methods in Ecology and Evolution published by John Wiley &amp; Sons Ltd on behalf of British Ecological Society,
Methods in Ecology and Evolution, 7, 499–504

�Software for identifying and managing photo data 501
We suggest that software used in camera trap research
should at a minimum provide the user with means of (i) automatically importing photos and photo metadata into a relational database setting to minimize data entry errors, (ii)
facilitating eﬃcient and accurate identiﬁcation of species in a
potentially overwhelming number of photos including the ability to batch identify a series of photos, crowd-source the identiﬁcation process to maximize eﬃciency, and make use of
double observers to maximize accuracy, (iii) quickly sorting
and querying photographic information once identiﬁcation is
complete, (iv) auto-generating summary reports, and (v) autogenerating input ﬁles for further analysis in software such as
Program MARK (White &amp; Burnham 1999) to minimize errors
and time required to complete analyses.
Each of the current software programs mentioned above
oﬀers useful solutions that cover at least some of the desired
functionality (Table 1). Thus each has relative strengths subject to user preference. However, to our knowledge, none of
them oﬀer the full array of properties and capacities necessary
to maximize eﬃciency with which camera trap data can be utilized in a research context. Here, we describe a new application
(CPW Photo Warehouse, CPW) that combines all of these features into a single solution (Table 1). The application and
manual are freely available for download from Colorado
Parks and Wildlife (thus the CPW moniker and recursive acronym) at: http://cpw.state.co.us/learn/Pages/ResearchMammalsSoftware.aspx.

Specifications
CPW is a Microsoft AccessÒ database that uses extensive
Visual BasicÒ for Applications (VBA) code to bring the complex functionality of the database to the user in the form of an
intuitive, easily accessible graphical user interface. The current
application operates on any modern WindowsÒ operating system (XP or newer), with MicrosoftÒ Access 2007, 2010 or
2013. Windows users who do not own an AccessÒ license can
use the database after downloading free AccessÒ Runtime software. Mac users have successfully used CPW to manage their
photos by installing Windows in a virtual machine environment, and the same solution will work with Linux operating
systems. Because the database is distributed as an .accdb ﬁle,
all of the design elements of the database (including VBA code)
can be accessed by closing the startup form. Thus, if necessary,
intermediate users can make modiﬁcations to suit the needs of
a speciﬁc project by leveraging the user-friendly interface and
built-in functions provided by AccessÒ. Advanced users can
further modify the software by altering the VBA or SQL code
we provide.
Photos are stored separately from CPW but link seamlessly into forms and windows when called. Links to photo
locations can be updated easily from within the database if
photos are moved to a new location. Depending on
whether the user opts to make use of the double-observer
functionality (see below), the database can store data from

Fig. 1. Photo ID form within CPW Photo Warehouse. Images and data ﬁelds are presented simultaneously in a single form to facilitate data entry
and minimize mistakes. Identiﬁcations can be entered via keyboard, using drop down lists, or shortcut keys. Filters can be used to focus work to a
speciﬁc season, location, and/or only those photos that still need identiﬁcation.
© 2015 The Authors. Methods in Ecology and Evolution published by John Wiley &amp; Sons Ltd on behalf of British Ecological Society,
Methods in Ecology and Evolution, 7, 499–504

�502 J. S. Ivan &amp; E. S. Newkirk
c. 800,000 (double observer) to c. 2,000,000 (single observer) photos when operating as a single ﬁle on a personal
computer. For large, recurring projects CPW can be modiﬁed so that it functions as a ‘front-end’ with tables stored
in a more robust enterprise-level database such as SQL ServerÒ. In this case, storage of photo data is unlimited.

Photo import
The structure of CPW follows a logical hierarchy similar to
that reported by previous authors (e.g., Krishnappa &amp;
Turner 2014). Cameras are organized ﬁrst according to
study areas, which are groups of cameras that the user may
later want to summarize or compare to other groups based
on attributes such as geographic areas, treatments and controls, or habitat strata. Within study areas, locations are
speciﬁed for each camera (or set of cameras if they are
deployed in pairs, as is often the case with mark-recapture
studies); within locations, information is stored from each
time a camera was deployed, checked or retrieved. Once
design information regarding study area(s), locations and
visits has been entered, photos can be added using the
Import Photos form. Users specify which visit the photos
should be associated with, which folder contains the photos,
and whether and how to copy/rename the photos. This
automated import process eliminates the need for manually
creating a spreadsheet row or database record for each
photo, thus minimizing opportunity for mistakes.

Photo identification
Once photos have been imported, the user logs in to the Photo
ID form and navigates through the images in sequential order,
providing identiﬁcations (ID) of the species in each photo.
Photos and data ﬁelds appear together in the form and the user
can type in identiﬁers, select them from a menu, or use shortcut
keys (including one to repeat all information from the previous
photo) to quickly populate the ﬁelds (Fig. 1). Each user can
customize keyboard shortcuts to suit them, and ﬁlters can be
employed to focus on photos from a speciﬁc location and/or
season and/or only those photos that yet need identiﬁcation.
Users can quickly highlight images of particular importance so
they can be easily retrieved later for use in reports and presentations. Double-clicking on an image opens it in an external
program so users can edit or zoom as needed to assist in identiﬁcation. The form can record any number of species and individuals present in a given image. A batch ID mode is also
available such that a particular ID can be applied to an unlimited series of photos in a single stroke.

Double observers to improve accuracy
The database is designed such that each photo is viewed by
two observers, which improves accuracy of the resulting data.
Thus, when a user clicks the ﬁlter to only view those images
that need ID, the program shows those photos that have not
yet been identiﬁed by that user and that need identiﬁcation

Fig. 2. The Photo Viewer form provides a means for the user to easily ﬁlter the data and associated photos based on any combination of study area,
location, ﬁeld season, species, highlights, dates, and times. Images that meet the ﬁlter criteria appear in the ﬁlm strip to the left, and any image can be
selected for enlarged viewing (center). The user can copy all photos that meet the ﬁlter criteria to a new folder or to a separate Photo ID module. They
can also view the results of the query in tabular view in Access, or delete all photos and associated records that meet the criteria.
© 2015 The Authors. Methods in Ecology and Evolution published by John Wiley &amp; Sons Ltd on behalf of British Ecological Society,
Methods in Ecology and Evolution, 7, 499–504

�Software for identifying and managing photo data 503
from at least one more user. Once photos have been subjected
to two observers the database manager or a third observer can
then log in to the Compare ID form, which displays those photos in which the two observers disagreed. The manager decides
which ID was correct and deletes the other. The database
tracks each observer’s IDs, even those that were deemed incorrect and deleted, so that a complete history of the observations
is maintained. Note that two observers are not strictly
required; if the database manager determines that a single
observer per photo is suﬃcient the database will still function
properly.

be identiﬁed, thus accelerating the most tedious and time-consuming aspect of research involving camera traps. For example, recently we used the module function within CPW to
identify species in 197 247 photos collected from 150 camera
traps during summer 2014. Modules were distributed simultaneously across a team of 10 observers; each photo was examined by two observers and discrepancies were rectiﬁed by the
database manager. The entire identiﬁcation process consumed
approximately 15 days. Note that it is the user’s responsibility
to independently track how photos have been distributed to
observers, which can be easily done with a simple spreadsheet.

Crowd-sourcing identification

Creating reports

To expedite the photo ID process, the database manager can
use the Photo Viewer form (Fig. 2) to quickly ﬁlter the data to
a manageable subset, which can then be exported to a modular
version of the Photo ID form and shipped to observers on or
oﬀ site. These modules contain the same species list as the master database, and observers identify photos as described above
(including logging in to the form to register who is assigning
the IDs), return the module, and the manager then uses the
Import Module form to import identiﬁcation data into the master database. As before, mismatched IDs will be ﬂagged and
can then be reconciled by the database manager. The ability to
parcel out photographs for ID across an unlimited number of
observers vastly improves the eﬃciency with which photos can

The View or Print a Report option provides a means for users
to easily generate various summary reports for a camera trap
project. For example, the ‘General Camera Summary’ includes
total cameras, total photos, average photos/camera, eﬀort
summaries (camera days), and number of photos of each species. Such a report is available at both the project and location
level, and by year. Users can also choose to print a summary of
detection data for individual animals, a photo ID summary
(list of the number of photos by location along with the number identiﬁed by one or two observers and their initials),
reports comparing performance of each observer who identiﬁed photos, or lists of cameras currently in deployment, including coordinates and access notes for each.

Fig. 3. CPW Photo Warehouse form for building custom input ﬁles for occupancy analysis using Programs MARK or PRESENCE. The user selects the
species, the number of occasions and their duration, and either a relative (sampling begins when a camera is set) or absolute (speciﬁc date) start for
the survey. Input ﬁles can be generated for speciﬁc study areas, survey years, or study extents and results can be previewed before export to Access,
MARK, or Excel. Similar forms allow the user to build input ﬁles for abundance, density, or activity pattern analyses in Programs MARK or DENSITY or
the r packages ‘secr’ and ‘overlap’.
© 2015 The Authors. Methods in Ecology and Evolution published by John Wiley &amp; Sons Ltd on behalf of British Ecological Society,
Methods in Ecology and Evolution, 7, 499–504

�504 J. S. Ivan &amp; E. S. Newkirk

Creating input files
CPW provides forms to easily generate input ﬁles for occupancy, abundance, density, or activity pattern analyses performed in Programs MARK (White &amp; Burnham 1999), PRESENCE
(Hines 2015), DENSITY (Eﬀord, Dawson &amp; Robbins 2004), and
the R (R Development Core Team 2015) packages ‘secr’
(Eﬀord 2015) and ‘overlap’ (Meredith &amp; Ridout 2015; Fig. 3).
The user can deﬁne which species the ﬁles should be built for,
and has complete control over the number and length of occasions generated. Options are available to allow the user to specify an absolute start date for a survey (e.g., June 1), or a start
date that is relative to the set date for each camera, and the user
can specify a buﬀer between when each camera was set and
when the survey (and input ﬁle) actually begins. Finally, ﬁlters
are available to create input ﬁles for a particular study area,
year, or spatial extent. The form provides a preview of the
input ﬁle and when satisﬁed, the user can export in a format
speciﬁc to software mentioned above, or as an ExcelÒ spreadsheet or AccessÒ query for further modiﬁcation.

Discussion
The practice of sampling wildlife with cameras has increased
tremendously in recent years, a trend that will likely persist into
the future as technological advances continue to improve the
eﬃciency and eﬀectiveness of these devices. This methodology,
however, produces large quantities of raw data that must be
archived and processed before analyses can be performed. CPW
Photo Warehouse provides researchers with a useful tool for
achieving this task. Our program provides essential utility collectively available in existing software programs (e.g., maximized automation of photo and metadata import to minimize
data entry mistakes, ability to auto-generate reports and
export data to input ﬁles for analysis with other software) but
also introduces important advancements that allow database
managers to formally utilize and track multiple observers during the photo identiﬁcation process. Such functionality greatly
increases eﬃciency of photo identiﬁcation (undeniably the
most time-consuming and tedious aspect of research associated
with camera traps) as an unlimited team of observers work
simultaneously to identify photos. Additionally, this new multiple observer functionality allows the database manager to
require that each photo be identiﬁed by two observers, which
improves accuracy of analyses based on photo data. CPW is
under continuous development to accommodate common uses
of photo data from camera traps and should be a helpful tool
for scientists who require the functionality encompassed here

but do not have the time or expertise to design and program
such utility themselves.

Acknowledgements
Funding for this project was provided by Colorado Parks and Wildlife and Colorado State University. We thank M. Schuette for developing critical aspects of the
initial Lynx Occupancy database upon which parts of this application are based.
We thank J. Lewis, K. Crooks, K. Blecha, S. Breck, R. Conrey, J. Halseth, R.
Much, L. Stinson, M. Strauser and C. Wait for testing, feedback and patience. D.
Johnston and K. Logan provided helpful reviews on early drafts. MicrosoftÒ,
AccessÒ, SQL ServerÒ and ExcelÒ are either registered trademarks or trademarks
of Microsoft Corporation in the United States and/or other countries. Use of
these names does not imply sponsorship, aﬃliation or endorsement of or by
Colorado Parks and Wildlife.

Data accessibility
No data were displayed, analysed or summarized in this publication.

References
Eﬀord, M.G. (2015) Package ‘secr’: Spatially explicit capture-recapture. Version
2.9.3. http://cran.r-project.org/web/packages/secr/secr.pdf.
Eﬀord, M.G., Dawson, D.K. &amp; Robbins, C.S. (2004) DENSITY: software for
analysing capture-recapture data from passive detector arrays. Animal Biodiversity and Conservation, 27, 1–12.
Fegraus, E.H., Kai, L., Jorge, A.A., Chaitan, B., Sandeep, C. &amp; Choonhan, Y.
(2011) Data acquisition and management software for camera trap data: a case
study from the TEAM Network. Ecological Informatics, 6, 345–353.
Harris, G., Thompson, R., Childs, J.L. &amp; Sanderson, J.G. (2010) Automatic storage and analysis of camera trap data. Bulletin of the Ecological Society of
America, 91, 352–360.
Hines, J.E. (2015) PRESENCE 8.3: Software to estimate patch occupancy and
related parameters. http://www.mbr-pwrc.usgs.gov/software/presence.html.
Kandel, S., Abelson, E., Garcia-Molina, H., Paepcke, A. &amp; Theobald, M. (2007)
PhotoSpread: A Spreadsheet for Managing Photos. CHI 2008. Florence, Italy.
Krishnappa, Y.S. &amp; Turner, W.C. (2014) Software for minimalistic data management in large camera trap studies. Ecological Informatics, 24, 11–16.
Kucera, T.E. &amp; Barrett, R.H. (2011) A history of camera trapping. Camera Traps
in Animal Ecology (eds A. O’Connell, J.D. Nichols &amp; K.U. Karanth), pp. 9–
26. Springer, New York, NY, USA.
Meredith, M. &amp; Ridout, M.S. (2015) Package ‘overlap’: Estimates of coeﬃcient
of overlapping for animal activity patterns. Version 0.2.4. http://cran.r-project.org/web/packages/overlap/overlap.pdf.
R Development Core Team (2015) R: A Language and Environment for Statistical
Computing. R Foundation for Statistical Computing, Vienna, Austria. http://
www.R-project.org.
Sundaresan, S.R., Riginos, C. &amp; Abelson, E.S. (2011) Management and analysis
of camera trap data: alternative approaches (Response to Harris et al. 2010).
Bulletin of the Ecological Society of America, 92, 188–195.
Thompson Reuters. (2015). Web of Science. http://thomsonreuters.com/en/products-services/scholarly-scientiﬁc-research/scholarly-search-and-discovery/
web-of-science.html
Tobler, M. (2014) Camera Base 1.6.1. http://www.atrium-biodiversity.org/tools/
camerabase/.
White, G.C. &amp; Burnham, K.P. (1999) Program MARK: survival estimation from
populations of marked animals. Bird Study, 46(Suppl), 120–138.
Received 25 August 2015; accepted 27 October 2015
Handling Editor: Patrick Jansen

© 2015 The Authors. Methods in Ecology and Evolution published by John Wiley &amp; Sons Ltd on behalf of British Ecological Society,
Methods in Ecology and Evolution, 7, 499–504

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="2">
    <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="479">
                <text>Journal Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="7018">
                <text>CPW peer-reviewed journal publications</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="4996">
              <text>CPW Photo Warehouse: a custom database to facilitate archiving, identifying, summarizing and managing photo data collected from camera traps</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4997">
              <text>&lt;p class="article-section__header section__title main"&gt;Summary&lt;/p&gt;&#13;
&lt;div class="article-section__content en main"&gt;&#13;
&lt;ol&gt;&#13;
&lt;li&gt;Contemporary methods for sampling wildlife populations include the use of remotely triggered wildlife cameras (i.e., camera traps). Such methods often result in the collection of hundreds of thousands of photos that must be identified, archived, and transformed into data formats required for statistical analyses.&lt;/li&gt;&#13;
&lt;li&gt;&lt;span class="smallCaps"&gt;&lt;i&gt;Cpw&lt;/i&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;i&gt;Photo Warehouse&lt;/i&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;is a freely available software based in Microsoft Access&lt;sup&gt;®&lt;/sup&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;that has been customized for this purpose using Visual Basic&lt;sup&gt;®&lt;/sup&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for Applications (VBA) code. Users navigate a series of point-and-click menu items that allow them to input information from camera deployments, automatically import photos (and image data stored within the photos) related to those deployments, and store data within a relational database. Images are seamlessly incorporated into the database windows, but are stored separately from the database.&lt;/li&gt;&#13;
&lt;li&gt;The database includes menu options that (i) facilitate identification of species within the images, (ii) allow users to view and filter any subset of the databased on study area, species, season, etc., and (iii) produce input files for common analyses such as occupancy, abundance, density and activity patterns using Programs&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span class="smallCaps"&gt;mark&lt;/span&gt;,&lt;span class="smallCaps"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;presence&lt;/span&gt;,&lt;span class="smallCaps"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;density&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span class="smallCaps"&gt;r&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;packages ‘secr’ and ‘overlap’.&lt;/li&gt;&#13;
&lt;li&gt;Our database makes explicit use of multiple observers, which greatly enhances the efficiency and accuracy with which a large number of photos can be identified. Modular subsets of the data can be distributed to an unlimited number of observers on or off site for identification. Modules are then re-incorporated into the database using a custom import function.&lt;/li&gt;&#13;
&lt;/ol&gt;&#13;
&lt;/div&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="80">
          <name>Bibliographic Citation</name>
          <description>A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.</description>
          <elementTextContainer>
            <elementText elementTextId="4998">
              <text>Ivan, J. S., and E. S. Newkirk. 2016. CPW Photo Warehouse: a custom database to facilitate archiving, identifying, summarizing, and managing photo data collected from camera traps. Methods in Ecology and Evolution 7:499-504. &lt;a href="https://doi.org/10.1111/2041-210X.12503" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1111/2041-210X.12503&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="4999">
              <text>Ivan, Jacob S.</text>
            </elementText>
            <elementText elementTextId="5000">
              <text>Newkirk, Eric S.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5001">
              <text>Camera traps</text>
            </elementText>
            <elementText elementTextId="5002">
              <text>Database</text>
            </elementText>
            <elementText elementTextId="5003">
              <text>Multiple observers</text>
            </elementText>
            <elementText elementTextId="5004">
              <text>Photos</text>
            </elementText>
            <elementText elementTextId="5005">
              <text>Wildlife cameras</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="78">
          <name>Extent</name>
          <description>The size or duration of the resource.</description>
          <elementTextContainer>
            <elementText elementTextId="5006">
              <text>6 pages</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="56">
          <name>Date Created</name>
          <description>Date of creation of the resource.</description>
          <elementTextContainer>
            <elementText elementTextId="5007">
              <text>2015-11-11</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5008">
              <text>&lt;div class="element-text"&gt;&lt;a href="http://rightsstatements.org/vocab/InC-NC/1.0/" target="_blank" rel="noreferrer noopener"&gt;In Copyright - Non-Commercial Use Permitted&lt;/a&gt;&lt;/div&gt;</text>
            </elementText>
            <elementText elementTextId="5009">
              <text>&lt;div class="element-text"&gt;&lt;a href="https://creativecommons.org/licenses/by/4.0/" target="_blank" rel="noreferrer noopener"&gt;Attribution 4.0 International (CC BY 4.0)&lt;/a&gt;&lt;/div&gt;</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="5011">
              <text>application/pdf</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5012">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="70">
          <name>Is Part Of</name>
          <description>A related resource in which the described resource is physically or logically included.</description>
          <elementTextContainer>
            <elementText elementTextId="5013">
              <text>Methods in Ecology and Evolution</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="7068">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
