Proyecto Primates Protocols Main Menu (para español presione aquí)

Version 2009-07-01


Welcome to the Proyecto Primates Protocol Site! In the following pages you will find detailed information on the different protocols that are being used for data collection, as well as protocols that are necessary for the management of the project and for collecting samples both in Yasuní National Park, Ecuador and in Formosa, Argentina. Anyone working in collaboration with Dr. Anthony Di Fiore and Dr. Eduardo Fernandez-Duque needs to read and follow these protocols. It is the information contained in the protocols that you are responsible for following, not the information passed on to you by other colleagues, students, assistants or even Dr. Di Fiore or Dr. Fernandez-Duque (since even we sometimes cannot remember everything that is included here). If you notice a discrepancy between something that we you and what is written here in the protocols, please bring that to our attention so that we can correct the protocols accordingly.

The protocols included here are divided into several different sections, not all of which need to be read by everyone on the project. For example, if you are not collecting phenological data or are not involved in processing captured animals, you need not read those particular protocols. However EVERYONE must read (and regularly REREAD) the basic information included following the Table below, as well as the PROJECT AND DATA MANAGEMENT protocols and the relevant BEHAVIORAL DATA and ECOLOGICAL DATA protocols for the project(s) you are affiliated with.Welcome to the Proyecto Primates Protocol Site! In the following pages you will find detailed information on the different protocols that are being used for data collection, as well as protocols that are necessary for the management of the project and for collecting samples both in Yasuní National Park, Ecuador and in Formosa, Argentina. Anyone working in collaboration with Dr. Anthony Di Fiore and Dr. Eduardo Fernandez-Duque needs to read and follow these protocols. It is the information contained in the protocols that you are responsible for following, not the information passed on to you by other colleagues, students, assistants or even Dr. Di Fiore or Dr. Fernandez-Duque (since even we sometimes cannot remember everything that is included here). If you notice a discrepancy between something that we you and what is written here in the protocols, please bring that to our attention so that we can correct the protocols accordingly.


The protocols included here are divided into several different sections, not all of which need to be read by everyone on the project. For example, if you are not collecting phenological data or are not involved in processing captured animals, you need not read those particular protocols. However EVERYONE must read (and regularly REREAD) the basic information included following the Table below, as well as the PROJECT AND DATA MANAGEMENT protocols and the relevant BEHAVIORAL DATA and ECOLOGICAL DATA protocols for the project(s) you are affiliated with.

BEHAVIORAL DATA

Monogamous Primates Project

Atelin Juvenile Project

Ateles Fission-Fusion  Project

Salt Lick Camera and Video Study

Titi Playback Study

RANGING DATA AND MAPPINGGPS and Ranging DataFlagging, Trail Maintenance, and Mapping

ECOLOGICAL DATA

Climatological Data Collection

Fruit Morphology Data Collection

Phenological Data Collection


 

DATA MANAGEMENT

Use of Palm Data Recorders

Installing HanDBase Templates

Reviewing and Storing Data

Data Management and Backup

Laboratory Maintenance and Equipment Care

SAMPLE COLLECTION

Fecal Samples for Hormone Extraction

Fecal Samples for DNA Extraction - RNA Later or Silica

Fecal Samples for DNA Extraction - Two-Step Method

Urine Samples for Hormone Extraction

Plant Photos and Voucher Specimens

ANIMAL HANDLING

Darting and Capturing

Processing Captured Animals

 

 

 

LOGISTICS

Obtaining a Visa and Censo Card

Station Rules and Regulations

Collection and Export Permits

Institutional Liability Release and Signature Page

Position on Data Property and Signature Page

MISCELLANEOUS

Daily Maps

Telemetry Information and Tips

Monthly Reports

Computer Notes

Safety in the Forest


WHAT IS A PROTOCOL?

CHARACTERISTICS OF OUR PROTOCOL

TYPES OF DATA TO BE COLLECTED

HIERARCHICAL ORGANIZATION OF THE MAIN PROYECTO PRIMATES DATABASE

DESCRIPTIONS OF FORMS, SUBFORMS AND TABS IN THE DESKTOP AND PALM DATABASES


WHAT IS A PROTOCOL?

A protocol consists of a detailed description of the methods used to collect data. The reality is that, no matter what anyone might say, no one can read a published scientific paper and precisely replicate the described methods, because the methods published in articles are not sufficiently detailed to allow that. But, everyone should be able to replicate the methods of a study by following the “protocol” used for the study. The use of protocols is common in laboratory settings, where it is important to have explicit instructions. For example, a protocol would indicate if you should centrifuge a reaction for 10 or 12 seconds. Although protocols do not appear to be used that often by field biologists, we are convinced that they are extraordinarily useful.

The secret to checking if a protocol is complete and ready to be followed is to “visualize” the entire data collection process: close your eyes, think about what you are going to do step by step, and make sure the protocol details that process precisely. For example, you are watching an animal and the alarm on your watch beeps: What do you see? What data you write down? In formulating a protocol, you need to be very explicit and leave little in doubt or ambiguous about what data an observer should be recording. Never think, “It’s obvious”! Instead, try to leave a minimum of things open to the interpretation of the observer.

In this project, you will be part of one of the first studies (we think THE first study!) where researchers are trying to collect truly comparable data on four different species of primates in two different countries with a set of unified protocols. The emphasis of our protocol is on the QUALITY of the data we aim to collect, not the quantity.

CHARACTERISTICS OF OUR PROTOCOL

Our sampling procedure is designed so that all data can be collected by a single person. There is a lot of different kinds of data to collect, and we expect it to be collected, recorded, and entered into the computer in a very specific way, so you MUST reread all the protocols pertinent to your work once a month during the first week of the month to make sure you remember everything you need to be doing.

Our protocols have been designed to ensure that the collection of CERTAIN kinds of data is done in an exactly comparable manner for all primate species being studied both in Ecuador and Argentina. There is another set of data that are being collected so that they are totally comparable for the four monogamous species under investigation. Clearly, it is impossible to collect ALL kinds of data using comparable methods, given, for example, the nocturnal habits of owl monkeys and the intrinsic habitat differences between the Amazonian rainforest and the gallery forest of the Argentine Gran Chaco. Nonetheless, our aim is that certain kinds of data, and the analyses to be performed on these data, will be COMPLETELY comparable.

To accomplish this goal, is of paramount importance that the protocols take precedence over what other students, assistants, or even the senior researchers may say. You are responsible for reading the protocols and following them. You must not assume that what you are being told is correct!

TYPES OF DATA TO BE COLLECTED

There are a great number of different types of data that you will be recording in the field and/or laboratory. The data we are collecting is organized in a hierarchical or nested fashion. All “inner level” data pertain to corresponding higher levels, but not all “higher level” data have associated “inner level” data. In the table above, we have included all of the different protocols that you may need to become familiar depending on the specifics of your work. Regardless of the kind of data you will be collecting, however, there are three key types of data (and associated data record numbers) that are extremely important. These data are collected by everyone, and the relevant data record numbers need to be entered consistently everywhere. These numbers are OBSERVER SAMPLE NUMBERS, AVISTAJE NUMBERS and FOCAL SAMPLE NUMBERS. In Ecuador, the GROUP SCAN NUMBER is treated the same; we have not yet implemented group scans in Argentina. All of these numbers are entered directly on the PALM DATA RECORDERS if you are collecting data on a PDA. If you are collecting data on paper (which you should only be doing if your Palm Data Recorder is not working) you MUST write the OS, AV, and FS numbers in ALL PERTINENT PLACES in your DATA BOOKS (i.e., all observer data should have the OS number listed; avistaje data should have both the OS and AV numbers listed; and focal samples should have OS, AV, and FS numbers listed). Detailed instructions for each of these types of data follow below.

HIERARCHICAL ORGANIZATION OF THE MAIN PROYECTO PRIMATES DATABASE


DESCRIPTIONS OF FORMS, SUBFORMS AND TABS IN THE DESKTOP AND PALM DATABASES

OBSERVER SAMPLES FORM

OBSERVER SAMPLES serve to organize almost all of the data being collected by each individual person on this project and also give us an idea of how observers are spending their time. This constitutes the highest level of organization of the main Proyecto Primates Database, and EVERY person affiliated with Proyecto Primates in Ecuador or Proyecto Mirikiná in Formsa must fill out an Observer Sample record for each day you are associated with the project. Ideally, we would like this data for everyone who works on the project for more than a few days (e.g., volunteers, SIT students) because this data can be used in grant applications (e.g., NSF) to QUANTIFY the Broader Impacts of our work in terms of training students, etc.

The use of OBSERVER SAMPLES to organize your data collection is simple and MANDATORY – these data MUST be collected each and every day, and there is no excuse for not doing it. The desktop and Palm databases have been organized so that this information must be included. Almost everything else present in these databases is pegged to a particular OBSERVER SAMPLE. OBSERVER SAMPLES are collected into the PP Observer Samples database on the Palm Data Recorder or into the Observer Samples section of your data book if collecting data on paper.

You will enter OBSERVER SAMPLES for every day you are associated with the project. This forms the “highest” level of organization of our data.

  • All observer samples are identified by a UNIQUE OS number, which must have seven characters. It begins with "OS" and then has five digits.

  • Each person on the project should have a set of dedicated numbers. The project managers in Ecuador and Argentina will assign you a range of OS numbers to use.

Every Observer Sample MUST have the following fields filled out when entered into the main Proyecto Primates Database:

  • Observer Sample Number – Make sure the OS number is UNIQUE!

  • Date – Dates in the main Proyecto Primates Database (and in your Data Books if collecting data on paper) should all have the same format: DD-MMM-YY, e.g., "21-JUL-06".

  • Rev by PI – This field is only present in the main Proyecto Primates Database. This is for the PIs to check after reviewing the data. Do not enter anything here.

  • Rev by Assistant – This field is only present in the main Proyecto Primates Database. After finishing entering your data or uploading it from the Palm to the main computer database, you need to review it to make sure that there no were mistakes made when typing the data and that all the fields that are supposed to be filled in fact are. This is a CRITICALLY important thing to do! You should check this box to verify that you have done this. We expect you to do this step, so do not omit it.

  • Notes – Enter briefly any significant comments about the observer sample.

  • Daily Summary – Beginning in January 2008, enter here a two to three sentence summary of your activity for the day, including any notable occurrences or behaviors seen (intergroup interactions, mating, severe aggression, etc.). These data are only entered in the main Proyecto Primates Database, not in the databases on the Palm Data Recorders. We expect EVERYONE to do this step, so do not omit it.

IMPORTANT NOTE:

  • If data for a particular field are not available or not recorded, then you must enter or select the values "Not Available" or “Not Recorded” as appropriate – do NOT leave a required field blank!

  • The fields "Avistaje Link", "Obs Activity Link", "Weather Link", "Biological Sample Link", and "Phenology Link" should ALL simply match the "Obs Sample ID" – these fields are redundant in MS Access but are used by HanDBase to link tables. These fields are not seen in the forms, only in the tables. When you port your data into the main Proyecto Primates Database, you should verify that all these link fields match the “Obs Sample ID” (i.e., the OS number).


OBSERVER ACTIVITY SUBFORM

These data provide an overview of how various members of the project team are spending their time. These data are to be collected in the PP Obs Act Data Database on the Palm Data Recorder (or in the Observer Activity Data section of your Data Book if collecting data on paper) and entered into the Observer Activity Subform of the main Proyecto Primates Database. You should note when you begin and end various types of field and camp activities. The main aim in collecting this kind of data is so that we can see how long particular kinds of data collection activities take (e.g., phenological monitoring, mapping) and so that we can estimate the total number of OBSERVER HOURS spent in the forest. Note that we are asking for very general information on observer activities and have tried to make entering these data as simple as possible.

IMPORTANT NOTES:

  • Observer Activity Data should each have a "Start Time" and an "End Time". As always, times should be entered in 24 hour format (i.e., HH:MM).

  • For the "Observer Activity" field, enter a brief description of your activity or choose the most appropriate activity from the popup menu on the Palm Data Recorder.  If necessary, you can add additional items to the popup menu.

  • The Notes section should be used to add any other pertinent details (for example, if you are doing “Field Work – Darting” or “Field Work – Search for Groups”, use the Notes section to indicate which group you are working with.

  • Your observer activity data should begin between 05:30 and 06:30 and should end no earlier than 17:30. That is, it should be a complete record of your activity throughout the day.  Be sure to review your observer actvity data each day and ensure that it is complete with no gaps: when one record ends, the next should begin!


AVISTAJES SUBFORM

The majority of the data you will collect in the field are organized around AVISTAJES (“sightings”) or encounters, either with your focal group of animals or with other groups or species. These data are to be collected in the PP Avistajes database on the Palm Data Recorder (or in the Avistajes section of your Data Book if collecting data on paper) and entered into the Avistajes Subform of the main Proyecto Primates Database.

You must collect AVISTAJE data EVERY TIME you encounter monkeys of any species, no matter whether you collect any other kind of data on them that day. This includes the animals you see while doing any field work activity. Every separate encounter you have within a given observer-day in the field constitutes a new AVISTAJE. For example, suppose you are with a group of sakis in the morning and you go back to camp for lunch (which should be rare!) or heavy rains force you to stop data collection. If you then return to the same group and do more sampling in the afternoon, the afternoon sampling session is considered a new AVISTAJE (since your original encounter “ended”) and the session should get a new number when the data are entered into the main Proyecto Primates Database.

How much data you will collect and the time spent in collecting AVISTAJE data will depend on the situation. For example, in Ecuador, if you are working on the "Monogamous Primate Project", AVISTAJE data should be collected as completely as possible for Pithecia, Aotus, and Callicebus. For other taxa, you must record at least the time and location of your encounter. Additional information may or may not be collected, depending on how it will interfere with your current activity.

  • All AVISTAJES are identified by a UNIQUE AV number. The AV number must have seven characters. It begins with "AV" and then has five digits.

  • Each person on the project should have a set of dedicated numbers. The project managers in Ecuador and Argentina will assign you a range of AV numbers to use.

For each Avistaje, ALL of the following fields MUST be filled in when entered into the main Proyecto Primates Database:

  • Avistaje Number – Make sure the AV number is UNIQUE!

  • Taxon

  • Group – Be sure to use UNK if the group is not a named group or if you cannot tell what group it is, but DO NOT leave this field blank.

  • Data Book – This field is only present in the main Proyecto Primates Database. You should enter here the name of the Data Book where the original copy of your data is recorded, if you collected data on paper, or the name of the Palm Data Recorder you used to collect the data. The name of your Data Book should have your last name in CAPITALS plus a space, then the book number ("01","02").

  • Time Enc – Times should always be entered in 24 hour format, i.e., HH:MM.

  • Loc Enc M

  • Loc Enc Deg

  • Loc Enc Pto Ref

  • Loc Enc Comments

  • Time Left

  • Loc End M

  • Loc End Deg

  • Loc End Pto Ref

  • Loc End Comments – If the location where you end an Avistaje is the same as the encounter location, you should select or enter “Same as Enc Loc” for the Loc End Comments field and leave the default values of 0 for Loc Enc M, 0 for Loc Enc Deg, and blank for Loc End Pto Ref.

  • Vocalizations Heard – For two taxa, Callicebus and Alouatta, we also record data on all vocal contacts with the animals (click the box marked Voc on the Palm), as these are the majority of encounters you will have. Beginning in January 2008, we also record data on Ateles long calls in this way.

  • Vocalization Distance – For all vocal contacts with Callicebus, Alouatta, and Ateles, you should record a subjective estimate of the distance you are from the callers (i.e., you will need to estimate the distance as “Near”, “Medium”, “Far”, or “Very Far” away).

  • Beh When Enc – On the Palm Data Recorder, pick one of the choices ("Resting", "Moving", etc.); for vocal contacts, choose “Vocalizing”

  • How Ended – On the Palm Data Recorder, pick one of the choices ("Left Animals", "Lost Animals", etc.); for vocal contacts, chose “Not Applicable”

  • Rev by PI – This field is only present in the main Proyecto Primates Database. This is for the PIs to check after reviewing the data. Do not enter anything here.

  • Rev by Assistant – This field is only present in the main Proyecto Primates Database. After finishing entering your data or uploading it from the Palm to the main computer database, you need to review it to make sure that there no were mistakes made when typing the data and that all the fields that are supposed to be filled in fact are. This is a CRITICALLY important thing to do! You should check this box to verify that you have done this. We expect you to do this step, so do not omit it.

IMPORTANT NOTES:

  • If data for a particular field are not available or not recorded, then you must enter or select the values "Not Available" or “Not Recorded” – do NOT leave a required field blank!

  • The fields "Range Data Link", "Focal Sample Link", "Feeding Bout Link", "Marked Tree Link", and "Ad Lib Data Link" should ALL have simply match the "Avistaje Sample ID" – these fields are redundant in Access but are used by HanDBase to link tables. They are not shown in the forms, only in the tables. When you port your data into the main Proyecto Primates Database, you should verify that all these link fields match the “Avistaje Sample ID” (i.e., the AV number).

If you are entering data only on the Palm Data Recorder, it is especially important to review your Avistaje data immediately after you have transferred it to make sure you have entered EVERYTHING that needs to be entered (i.e., that none of the required fields are blank or contain odd pieces of information. Do not simply upload and forget about it! Do this BEFORE you delete the data from your Palm. Please be sure to follow in detail the protocol for Using the Palm Data Recorder.

For each AVISTAJE there will be a number of additional types of data you will be collecting, including Demography and Census Data, Ranging Data, Marked Trees Data , Feeding Bouts Data, Focal Samples Data, Group Scan Data, Juvenile Ad Libitum Data, and Other Ad Libitum Data. These are recorded in different databases on the Palm Data Recorder (or in separate places in your Data Book, if you are collecting data on paper). In the main Proyecto Primates Database, the Avistajes Subform has multiple Tabs that address each of the different kinds of data.

Demography and Census Data Tab

NEED TO DO THIS

Ranging Data Tab

Throughout a follow, you will record the location of the group being observed every 20 minutes – on the hour and at 20 and 40 min past the hour – even if those points fall during a FOCAL SAMPLE or GROUP SCAN (see below). If you cannot take the position during a FOCAL SAMPLE or GROUP SCAN, try to remember where you were and take the position after the end of the sample or scan.

Some of the ranging data are recorded with the AVISTAJE for the group you are following since the AVISTAJE asks for the time and position where you first encounter monkeys and where you leave or lose them. The additional data on group locations recorded during a follow are collected in the PP Ranging Data database on the Palm Data Recorder or in the Ranging Data section of your Data Book if you are taking data on paper.

Positions should always be noted as distances and angles from reference points on the trails and transects or trees that have already been mapped. Whenever you can, it is better to take a position using a trail point rather than a tree as a reference point, but a nearby tree is better than a much further trail point. You can also take the ranging reference point using your GPS (see the GPS and Ranging Data Protocol for information on using GPSs for recording Daily Tracks and for ranging data collection).  In this case, if you use a GPS location as your ranging point, you would score the distance and bearing as 0 m and 0 deg and the reference point as [GPS NAME] HH:MM (i.e., the name of the GPS and the time of the location to the nearest minute).

If taking data on paper, all location data should be recorded in your Data Book in the form of “Distance, Compass Angle, Reference Point”. Do NOT record location data in any other way! Use the codes “m” for meters and “d” for degrees without inserting spaces after the commas. Example: “09:20 20m,250d,AV-05-021”.

You should practice estimating distances as you walk on the trails, which are marked at regular intervals. Count your paces for 25 meters and then use that to guide your distance estimates. You will get pretty good at estimating distances of up to 40 or 50 meters using your paces! From time to time, bring out the laser range finder and check yourself!

IMPORTANT NOTE:

  • When you record an angle, the angle should be AS IF YOU WERE STANDING AT THE MAPPED REFERENCE POINT. This means that if you take an angle from where the monkeys are back to a mapped point, you will have to invert the angle (e.g., an angle of 180 degrees read from where the monkeys are back to a reference point corresponds to an angle of 360 degrees from the reference point).

For each ranging point that you record, you must also record a Ranging Data Comment, qualitatively classifying each ranging data point as one of the following:

  • GOOD – You saw the animals and were able to measure or estimate the location visually with good precision because it was a short distance.

  • ESTIMATED – You had to estimate a distance of less than ~30m visually or by pacing.

  • ROUGH – You had to estimate a distance that was quite long (>30 m) and thus your estimate is rough.

  • BEHIND – The animals are moving ahead and you estimate the location from far behind them or you are completely unable to make a location estimate.

  • SIGNAL ONLY – You do not see the animals but have a strong clean telemetry signal. This means you can localize the signal to within 15-20 meters but cannot figure out precisely which tree your subjects are in.

We cannot stress enough how absolutely critical the accurate and systematic collection of the ranging data is for this project. You should not be missing more than a few ranging points in any given full day follow. Be especially conscientious of writing down the CORRECT tree number if you use a tree as a mapping point. It is very easy to accidentally invert two digits or to assume you know the tree number without looking at the metal tag, but this causes a lot of problems if you are wrong, because such errors are VERY HARD to correct post hoc. If you are far away from a reference point or simply cannot stop to take the ranging data, and especially you are in a seldom used part of the group’s range or far away from trails, the ranging data are especially important. In this case, you may need to put up a temporary flag with the date and time and find your way back to that spot on a different day to map it. When you do this, be sure to go back and enter it IN THE CORRECT PLACE on the Palm Data Recorder or write it in the APPROPRIATE PLACE in your Data Book. Please do this sparingly, however, and REMOVE the temporary flagging once you go back to map the point.

Ranging data should be entered as follows:

  • Time should always be entered in 24 hour format, i.e., HH:MM.

  • Loc M should be entered as an integer number.

  • Loc Deg should be entered as an integer number from 0 to 359. Be sure to never enter numbers greater than 359. Use 0 for North, not 360. DO NOT use names for cardinal positions (e.g., do not use "NE" for 45 degrees).

  • Loc Pto Ref must be a mapped trail point or tree. FOLLOW THE FORMATING CONVENTIONS EXACTLY when entering reference point names!

  • Enter trees as XX-XX-XXX, with the first two digits being the initials of the primate species the tree pertains to in CAPITALS, the next two digits being the last two digits of the YEAR, and the last three digits being a sequential number within the year. 

  • For trees that do not have the format above, enter the tree number plus T or L in CAPITALS with NO SPACE between the number and the letter T or L.

  • Use only PA-, CD-, LL-, AB-, AV-, SS-, CA- (i.e., Calb, but just record as CA-), and FT trees for mapping. The format for FT trees is "FTX" plus a space plus 5 or 6 letters that reflect the date.

  • Enter trail points and transect points as the FULL trail name, followed by a space, then the meter number for a flagged position. The first letter of trail names should be CAPITALIZED.

  • DO NOT estimate a meter number for an unflagged location on the trail (e.g., do not record a position from 10m along the trail from Puma 200 as "Xm,Xdeg,Puma 210"; instead, map from Puma 200 or 225.

  • For trail crosses or trees with more than one ID, enter only ONE of the equivalent tags.

  • DO NOT score a location as "Near such and such" a place.

  • DO NOT record locations with reference to miscellaneous flags you see in the forest that are not part of the primate project.

  • Only as a last resort should you record a previous LOCATION as the Loc Pto Ref for a new location. If you do this, then you MUST use a specific format for recording this information. Say you are doing a follow on July 21st, 2006 and you need to use the 9:20 location as the Loc Pto Ref for your 9:40 location. You would then enter in the database "LOC 09:20 21-JUL-06" in the Loc Pto Ref field. DO NOT use "Last Point" as your Loc Pto Ref. Also, try to avoid using "P.R." or "Ref Point" flags as many of these are not mapped.

  • If you are far away from a marked point, you can, as a VERY LAST RESORT, make a "Reference Point" – a marked point to enter in the database and from which you can map temporarily, BUT if you do this, you MUST find your way back there within a few days and MAP the reference point, just as if it were a marked tree. Enter these new reference points in the MARKED TREES section of the database as if they were a marked tree, but note "Ref Point" in the "Kind of Tree" field. The reference point should include the time and the date you mark it and should be labeled EXACTLY as follows, both on the tape in the field and in the MARKED TREES section of the database: "Ref Point HH:MM DD-MMM-YY", e.g., "Ref Point 09:46 03-JUL-06".  Note: as always, the use of military time and the format for the date!

REMEMBER, the goal is to automate the assignment of actual X and Y coordinates to your ranging points... we cannot look up the X and Y values for a reference point that does not exist in the database (or that cannot be found), thus the above conventions are ESSENTIAL to successfully search the database for reference point location.

Note that you can also use a GPS point as a reference point. To do so, enter “GPS ” plus a two or three digit code for the particular GPS used (e.g., “MM” for Mike Montague, “YS1” for Yukiko Shimooka 1, "PP1" for Proyecto Primates 1), plus the name or time you assign to the point on the GPS (e.g., “GPS MM SS0007" or "GPS YS1 11:54"). If you do this, however, you MUST be sure to download your GPS data properly as noted in the GPS and Ranging Data Protocol , including noting some measure of the precision of the GPS point (either the DOP or the average error) and whether the point was taken with 2D or 3D navigation.

IMPORTANT NOTE:

  • Always use WGS84 as the coordinate system for your GPS and, where called for, set the projection as UTM 18S.

Additionally, you will use the 0, 20, and 40 minute ranging data points to keep a running record of the group's General Activity, as well as an informal running record of weather conditions, which we can use to examine the relationship between weather variables and particular behaviors such as army ant foraging by saki monkeys. There are two different weather variables to record at the 20 minute point: Light/Rain conditions and Wind conditions. Light/Rain should be classified on a scale representing the degree of cloud cover and rain: “Rain”, “Drizzle”, “Cloudy”, “Partly Cloudy”, “Slightly Cloudy”, “Mostly Cloudy”, and "Full Sun" for daytime observations, “Clear Night”, “Moon Visible”, “Moon Partially Visible”, “Moon Not Visible” and “Dark” for nighttime observations. Wind condition is classified on a 3-point scale: “No Wind”, “Slight Breeze”, and “Windy”.

In Ecuador, for some projects, you will also use the ranging data points to note down several other pieces of information: the Group Speed, the Group Spread, whether the group is associated with another primate species, and, if so, the distance between the closest members of the two taxa. You will also note the average Group Height in the canopy at which the animals you are following are seen and the average Canopy Height in the forest at that location. For both, height categories are given in 5m increments (e.g., 0 to 5m, 5 to 10m, etc.).

  • Group Speed – Noted subjectively as “No Movement”, “Very Slow”, “Slow”, “Medium” or “Fast”,

  • Group Spread – Assigned with the popup menu on the Palm Data Recorder.

  • Associated With – All species associated with should be listed, separated by slashes and with a slash at the end.

  • Association Distance – Assigned with the popup menu on the Palm Data Recorder.

  • Group Height – Average height of the detectable group members. Heights are noted in 5m increments.

  • Canopy Height – Average height of the canopy in the area around the group. Heights are noted in 5m increments.


Marked Trees Tab

To continue gathering data on the diets and ecological strategies of the taxa we are studying, we mark and map the locations of feeding trees and we estimate the time spent in feeding patches of various species. Thus, each time you find your target taxon feeding in a food patch, you will mark the tree and record a number of pieces of data concerning the feeding source. These data are recorded in the PP Marked Trees database on the Palm Data Recorder or in the Marked Trees section of your Data Book if you are taking data on paper.

You only need to mark only patches fed in by a group or individual monkey for more than five “group-feeding” minutes (i.e., “major” food sources: those fed in by a single animal for 5 minutes, or by several animals for a total of 5 “monkey minutes” over the course of the day). You should train your ears to listen for the sound of falling fruits and you should get in the habit of looking at your watch when you first hear fruits dropping in order to accurately assess whether or not to mark a patch.

You will mark with plastic tape all those trees used for foraging as described above plus trees that you know the animals sleep in (sakis, titis, and owl monkeys all reuse at least several sleeping trees). Mark sleeping and feeding trees (or the trunk supporting the feeding source in the case of epiphytes, hemiepiphytes, lianas, vines, or bromeliads) in the following way.

  • In Ecuador, all monkey feeding trees get marked with a unique letter and number combination that includes information on the primate species using the tree, the year in which the tree was marked, and a sequential number. The first two digits of the tree number correspond to the first letter of the genus and species of the primate using the tree followed by a dash (“PA-” for Pithecia aequatorialis, “CD-” for Callicebus discolor, “AV-” for Aotus vociferans, “AB-” for Ateles belzebuth, “LL-” for Lagothrix lagotricha, “AS-” for Alouatta seniculus). Then, the rest of the tree number consists of 2 digits corresponding to the year in which the tree was 1st used, a dash, and then a three digit sequential number (“001”, “002”, etc.). For example, the 1st tree marked in 2005 for owl monkeys was given the code “AV-05-001”, the second given “AV-05-002”, etc.).

To mark the tree, write the tree number on PINK FLAGGING TAPE (please ONLY use pink!) and tie the tape around the tree, preferably UNDER (rather than around) any lianas hanging down or attached to the trunk. You should also write the date (in “mmm yy” format) and the initials “PP” for “Proyecto Primates” on the tape, and you should write on the tape “Sleep” if the tree is a sleeping tree or the Life Form of the feeding source if the tree is a feeding tree. Finally, you should write the tree number on a metal “write-on” or engravable tag that you then put on the tree with an aluminum nail. Go over the engraving with a black sharpie marker to make the number stand out at a distance. Do not hammer the nail all the way in; you should leave about an inch or so of shaft exposed on the nail to allow the tree to grow without swallowing the tag.

Note that if you are marking a liana or other epiphytic plant that spans several trees, you need only tag the trunk that supports the bulk of the liana. In Ecuador, every new life form marked on a given trunk should be tagged as a different number. For example, say one day the titi monkeys eat fruit from a tree that you tag as “CD-05-104” and then they eat, a few days later, from a liana in the same tree crown, the liana should get a NEW TAG NUMBER. Similarly, if multiple species eat from the same life form, you should put up a tag and tape for each species. Thus, a given tree may be marked with 2 or more metal tags and pink flags. If you do record a new number for a previously marked tree, enter all the other tags separated by slashes (and with a slash at the end) in the “AKA” section of the marked tree table in the database. Also note in this section any numbers on the metal tags from other projects (e.g., "FT" tree numbers from Abigail Derby's work on howler monkeys; the numbers from Mark Mulligan and collaborators' HERB projects).

The following data about each tree must be also noted on the PP Marked Trees database on Palm Data Recorder or in the Marked Trees section of your Data Book if you collect data on paper.

  • Metal Tag – This box checked or not to indicate whether or not you marked the tree with a metal tag. If you do not do this when you flag the tree, you must go back and do it later.

  • Kind of Tree – “Feeding”, “Sleeping”, “Ref Point”, or “Other”.

  • Life Form – If the tree represents a feeding source, indicate the life form from which they feed: Liana (“L”), Epiphyte (“E” e.g., aroids), Unknown (“U”), Hemiepiphyte (“H”, e.g., many figs), Bromeliad (“B”), Vine (“V”), Other (“O”), Canopy Tree (CT) (the crown of the tree is located principally in the main canopy level), Subcanopy Tree (“ST”) (the crown of the tree is located principally below the crowns of surrounding trees) or Emergent Tree (“ET”) (the entire crown of the tree sticks out above the surrounding canopy) [Note the database has all of these categories for life form, with "emergent tree" having been added in Summer 2006.] You will become good at following trunks and supported life forms up to the canopy with your binoculars, so most of the time identifying the life form will be pretty easy. Most feeding sources will probably be trees or lianas. If you do score a life form as “Unknown” but are able to figure it out at a later date (perhaps because they feed on another exemplar of that species where you are able to get a better look), go back to the Marked Trees section of your data book and the database and correct the data in both places.

  • Support Class – The class of the tree or supporting trunk being mapped. This field should only be used if the feeding source is NOT a tree, and the options are Emergent Tree (“ET”), Canopy Tree (“CT”), or Subcanopy Tree (“ST”) as per the definitions above.

  • Part Eaten – “Fruits”, “New Leaves”, “Mature Leaves”, “Flowers”, “Seeds”, “Unknown”, or “Fruits and Seeds”.

  • Fruits/Seeds Collected – Box checked or not to indicate if you collected samples of fruits. PLEASE try to do this for any new item consumed and for those you do not recognize.

  • Leaves Collected – Box checked or not to indicate if you collected samples of leaves. PLEASE try to do this for any new item consumed and for those you do not recognize.

  • Distance, Compass Angle, Reference Point – The information needed to map the position of the tree. All tree location data should be recorded as “distance,compass angle,reference point”. Do your best to map the tree at the time you are there, it will be much more difficult to do it later or some other day. Most measurements between 20 and 40 meters can be paced off from a reference point. It is ESSENTIAL to be precise and map trees as accurately as possible as these data will be entered into a GIS location database. Thus, if a tree with tape or tag is encountered later, you can use the tag information to find the location without having to map it again. If you do not have the chance to map a tree well on the day that it is marked, be sure to return to it on a different day, map it well, and record the location in the appropriate place in the Marked Trees database on the Palm Data Recorder (i.e., with the other data on that tree) or in the Marked Trees section of your data book.

IMPORTANT NOTE:

  • Remember, again, that when you note an angle, the angle should be AS IF YOU WERE STANDING AT THE MAPPED REFERENCE POINT. This means that if you take an angle from a tree back to a mapped point, you will have to invert the angle (e.g., an angle of 180 degrees read from where the monkeys are back to a reference point corresponds to an angle of 360 degrees from the reference point). Be very careful to not map a tree 180 degrees off from its true location!

  • CBH (circumference at breast height) – You will measure the circumference at breast height of the feeding source (or the supporting trunk in the case of lianas or epiphytes). CBHs should be measured at a standard 130 cm from the ground, with 130 cm being measured along the trunk, on the UPSLOPE side of the trunk for trees that are on an incline. For trees such as Iriartea or Socratea palms that have root cones that can extend above 130 cm and for trees that have buttresses that rise higher than 130 cm, the CBH should be measured ABOVE the level of the root cone or buttresses. For these trees, note the height at which the CBH was measured (in the database, this information goes in the Measure Comments section).

  • For trees with very big buttresses, where it is impossible to reach (or climb) high enough to measure the CBH above, you can ESTIMATE the DBH (diameter as breast height, not circumference) by visualizing that the trunk of the tree just above the buttresses extends down to the ground – e.g., visualize two vertical lines extending down from the sides of the trunk as you look at the tree – and measuring the distance between those lines. Estimated DIAMETERS or DBHs should be noted very clearly in the Notes section of the PP Mapped Trees database on the Palm Data Logger or in the Marked Trees section of your Data Book if taking data on paper, along with the height that your estimated diameter refers to. These should then be entered in the appropriate section of the Marked Trees Tab in the main Proyecto Primates Database. Note that prior to Summer 2006, these data were noted in the CBH Measure Level Comments section of the main Proyecto Primates Database.

  • Family – Enter the name if you are sure of it, if not indicate you are in doubt.

  • Genus – Enter the name if you are sure of it, if not indicate you are in doubt.

  • Species – Enter the name if you are sure of it, if not indicate you are in doubt.

  • ID By – Enter the full name of the person who identifies the tree. DO NOT use initials for "ID By".

Some additional useful definitions for tree measurements, even if not prompted to enter them in the databases:

  • Tree Height refers to the distance from the ground to the top of the tree. Tree heights can be measured using the laser range finder and clinometer for taller trees (heights can be estimated for trees up to 10m).

  • Crown Height is the distance from the lowest branch in the canopy (ignoring small branches that may project from much lower on the trunk) to the top of the tree. The best way to calculate crown height is to determine the height of the lowest canopy branch (by visual estimation for heights up to 10m and by direct measurement with the range finder and clinometer for greater heights) and then subtract this from the tree height.

  • Crown Breadths are the diameters of the horizontal projection of the tree crown. To estimate crown breadths, pace off the dimensions of the crown in TWO perpendicular directions and convert your paces into meters. (To do this accurately, you will need to know your pace – you should determine this by counting your steps between 25m flags on the marked trails and regularly check your pace over the course of the study).


Feeding Bouts Tab

Additionally, for each marked tree – and for feeding sources that you are unable to mark – you will record feeding bout data in the PP Feeding Bouts database on the Palm Data Recorder (or in the Feeding Bouts section of your Data Book if collecting data on paper) for all bouts greater than five “monkey minutes”. You need not worry about recording bout data for bouts lasting less than five minutes.

For each feeding bout, note the time (to the nearest minute) at which the first feeder(s) entered the tree and began feeding (e.g., if recording data on paper, you would note “10:45 BE AV-05-001” for “Begin Eat AV-05-001 at 10:45”) and when the last feeder(s) finished feeding (e.g., “11:15 EE AV-05-001” for “End Eat AV-05-001 at 11:15”).

If you are following some animals and arrive at a food patch where animals are already feeding, score your arrival time as “BE Late” (“begin eat late”) or check the box “Late?” on the Palm Data Recorder. If you need to leave a tree before the last feeders have left (e.g., if your focal animal leaves the feeding patch while others are still eating), record the ending time as “EE Early” (“end eat early”) or check the box “Early?” on the Palm Data Recorder. If you miss a BE or EE time, score it as “Not Recorded”, but please be aware that this is a code of last resort, introduced to deal with when observers forgot to collect data that they were supposed to collect.

With the BE and EE times, we can calculate a minimum number of minutes that the group spent feeding in a particular patch. If the animals stop feeding in a patch for more than five minutes, and they return to the same tree, record another set of BE and EE times.

If the animals are feeding but you do not know from which tree you may record it as PA-05-XXX, meaning the monkeys are having a feeding bout but you cannot be sure on which tree, therefore you cannot mark it. Also, record the maximum number of individuals that you see feeding in the patch simultaneously (e.g., using the Max Feeders field popup menu on the Palm Data Recorder). For certain portions of the "Ateline Primate Project", you will also keep a running tally of the number of feeders in the tree each minute; to do this, use the Feeding Rec button on the Palm Data Recorder or note these data in the Feeding Bouts section of your Data Book.

If the food item is one that you do not recognize or that you have not collected previously, MAKE A COLLECTION of both the leaves and the fruit of the plant (note what collections you have made in the PP Marked Trees database on the Palm Data Recorder or in the Marked Trees section of your Data Book and in the main Proyecto Primates Database; you will enter specific information on the collection in the Plant Collections section of the main database later). It is important to do these collections to allow us to identify the plants being eaten. To make collections, look carefully at the tree through binoculars to get a good idea of the appearance of the leaves and fruits and then look for these on the ground under the tree. Carry plastic bags with you at all times to shove these collections into until you get back to the lab. In Argentina, if you cannot identify the species, write down in the last page of the Avistaje yellow book the information on the tree so that the Botanist David Iriart can identify the tree when he goes to Formosa. In Ecuador, when you return to the lab with your collection, process the samples according to the Plant Voucher Specimens protocol.

Finally, if the Feeding Bout is not in a marked tree, you should enter location data for the bout in the same format we use for all location data (XXm,Xxdeg,Loc Pto Ref).


Focal Samples Tabs and Focal Data

Behavioral data collected during focal samples are collected into different Palm Data Recorder databases, depending on the project you are associated with.  For the "Monogamous Primates Project", these include the databases PP Mono Foc Samples and PP Mono Focal Data.  For the "Ateline Primates Project", these include the databases PP Atel Foc Samples, PP Atel Focal Data, PP Juv Foc Samples, and PP Juv Focal Data . If you are collecting data on paper, these data would go in the Focal Data section of your Data Book if collecting data on paper. Detailed information on how to collect these data is included in other protocols. Here, we simply note some key points regarding how data must be entered.

When completing FOCAL SAMPLES:

  • There should NEVER be a focal sample on an UNKNOWN individual.

  • The TIME START field for a focal sample should NEVER be blank.

  • If you are recording focal data on a dictaphone for later transcription, enter the name of the dictaphone file in the appropriate text box.

  • Choose the appropriate popup box to indicate how complete your focal sample was (“aborted” = abandonded within the 1st 10 minutes of the sample, “incomplete” = reached 10 minutes of sampling but focal lost before the end of the sample, or “complete” = reached the full 20 minutes. When entering focal data into the main Proyecto Primates Database, DO NOT “fill out” data for the two minute sampling points past the time you stopped sampling with “FV” but DO fill these out with the code “XX” such that every focal sample contains 10 lines of data, one for each two minute sampling point.

When completing FOCAL DATA:

  • All behavior and partner data need to be followed by the slash ("/") character when entered into the database, as this is the signal for our text parsing routines for the end of a piece of data. This is done automatically when you take data on the Palm Data Recorder.

  • For points where there is some social behavior involving a partner, the number of behaviors you record and number of partners MUST match, even if the partner is the same one. So, for example, if your focal is Kong and you see him grooming and tail twining with Kelly on the beep, you would record for behavior "SGMA/STT/" and you would record for the partner "KE/KE/". The reason for this is that it allows us to AUTOMATE the parsing of the text data to pull out what we are interested in easily.

  • It is a little more complicated if your focal is doing one nonsocial and one social activity, but we still need a consistent way to parse the data in each column. So, you need to use a "dummy" partner code ("---") for the nonsocial activity. Thus, if Kong is resting vigilant at the observer while tail twinning with Kelly, you would need to record "RVO/STT/" for the behavior and "---/KE/" for the partner are we doing three hyphens?

  • Please note that during the group scans taken within a focal sample, if you record some social activity for an animal other than your focal, then you MUST also record the partner for that activity!

  • For the "Monogamous Primates Project", you also MUST record scan data for all other known individuals in the group if they are present, even if they are not seen. Thus, for a scan on Callicebus L group when Lineo is your focal, you must record SOMETHING for Lulu and the juvenile, even if you do not see them – in this case, record "FV" for their behavior. This tells us that you tried to take the data but did not see them rather than simply forgetting to take the data!

  • NOTE: EVERY FOCAL SAMPLE SHOULD HAVE DATA FOR EVERY 2 MINUTE POINT (that means if you lose a focal partway through, you should enter “XX” for each remaining 2 minute point in the sample, even if you start another sample before what would have been the end of the sample (this is to facilitate data analysis so that each focal has a consistent number of lines of data).


Group Scan Tab

The priority for data collection is to collect focal samples. However, this is not always possible as often the animals are difficult to see or (especially for the monogamous primate project) disappear into the tops of trees for stretches of time. In order to have a better idea of how the animals are spending their time, we started, in Ecuador in summer 2007, to implement GROUP SCANS every 10 minutes (i.e., at 0, 10, 20, 30, 40, and 50 minutes past the hour) AT TIMES WHEN YOU ARE NOT IN THE MIDST OF A FOCAL. Again, the PRIORITY is focal samples, but at any 10 minute point during the day when you cannot, for some reason, do a focal, you should be doing a group scan. For the "Monogamous Primates Project", we have discontinued this practice as of December 2008.

Behavioral data collected during groups scans are collected into the PP Mono Group Scans or PP Atel Group Scans databases on the Palm Data Recorder (depending on which project you are affiliated with) or are noted in the Group Scans section of your Data Book if collecting data on paper.

For the group scan procedure, you should look at each visible member of the group, count off 5 seconds in your head, and record its predominant behavior(s) (using the codes in the relevant ethogram), nearest neighbor(s), and distance(s) to its nearest neighbor(s) (record data for all nearest neighbors if more than one are present in the nearest neighbor category). When recording NN data during group scans, for any individual who has an INFANT in contact record NN data for BOTH THE INFANT AND THE NEXT NEAREST NEIGHBER. Thus, for a female carrying an infant whose next nearest neighbor is an adult male 5 to 10 meters away, you would note for NN: INF/AM/ and for NN Dist: CON/5-10m/. You should also check the appropriate checkbox indicating whether or not a scanned animal is carrying an infant.


Juvenile (Nursing and Feeding) Ad Lib Data and Other Ad Lib Data Tabs

In these tabs you will enter data pertaining to observations that may have happened outside of FOCAL SAMPLES or GROUP SCANS or that were not amenable to the systematic data collection. JUVENILE NURSING AD LIB and JUVENILE FEEDING AD LIB DATA are collected as part of the Ateline Juvenile Primates project, while OTHER AD LIB DATA are collected for all projects. The data are collected into the PP Nursing BoutsPP Juv Forage Bouts, and PP Ad Lib, databases on the Palm Data Recorder or in the Ad Lib Data section of your Data Book if collecting data on paper.


PHENOLOGY SUBFORM

This subform, accessed from the OBSERVER SAMPLES form, is used to enter data on PHENOLOGICAL PATTERNS in the forest (see the Phenological Data Collection protocol). These data are collected into the PP Phenology database on the Palm Data Recorders.


MAPPING DATA SUBFORM

This subform, accessed from the OBSERVER SAMPLES form, is used to enter MAPPING DATA for trails and transects around the site (see the Flagging, Trail Maintenance, and Mapping protocol). These data are collected in the PP Mapping database on the Palm Data Recorders.


BIOLOGICAL SAMPLES SUBFORM

This subform, accessed from the OBSERVER SAMPLES form, is used to enter data on any BIOLOGICAL SAMPLES you collect (see the protocols for Plant Voucher Specimens, Plant Nutrient Samples, Fecal Samples for DNA Extraction - RNA Later or SilicaFecal Samples for DNA Extraction - Two Step Ethanol plus Silica, Fecal Samples for Hormone Extraction, and Urine Samples for Hormone Extraction). These data are collected into the PP Biol Samples database on the Palm Data Recorders.


CAPTURE RECORDS SUBFORM

This subform, accessed from the OBSERVER SAMPLES form, is used to enter data on darted and captured individuals (see the protocols for Darting and Capturing and for Processing Captured Animals). These data are collected into the PP Capt Measurements and PP Capture Data databases on the Palm Data Recorders.