<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.5pt;
        font-family:Consolas;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:Consolas;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Okay, I think this is the end of our conversation from the
tail end of June through 1<sup>st</sup> of July on the GPS subgroup data entry
question (below). We all agreed that everything except the GPS points for
subgroups would still go into the handwritten subgroup notes and this seems to
be still occurring just fine (though more extensive notes on Ositeti subgroups when
they appear in other group notes would be handy for figuring out who is in
which group and getting a better handle on fission dynamics). It was also
agreed to put an S at the end of GPS points that are taken for subgroups, which
I think is being more consistently implemented now than it was in the spring (yes,
Lacey?).<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I see now which part was unresolved – how to link the GPS
points to particular subgroups. I just spoke to Catherine about this and she
doesn’t think this can easily be done in the GPS device. Certainly
if someone is with a subgroup for a distinct chunk of time, as in the 4 Sept
example of CLF’s, it makes sense to go ahead and put B for begin and E
for end (and maybe designate them as S1 and S2 and record which subgroup is
which in the written notes?). One thing this does not tell us is whether
the group began/ended or was found already in existence and then was left still
in existence at those times. This is another reason why consistency in the
handwritten notes is very important. What we both agree would be very
helpful is if start and end times spent with a subgroup were more consistently
recorded in the handwritten notes (currently there is a high probability that
one or both time is not recorded, which means a good deal of cross referencing
with both SWERB data and the handwritten notes would be required to possibly
tease out which subgroup the observers were with at any given time). The
team and other observers should also more consistently note whether the
subgroup was already present upon their arrival and departure. As far as
I can tell they usually make note of when a group forms or rejoins while they
are there but sometimes forget to note the time (particularly on rejoin) and only
sometimes specifically note that the group was already formed or was still separate
when they left – it would be good to have this consistent so we can state
with full confidence whether the group was in existence before and after the
recorded start and end times.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Lacey, would consistently including start and end times in
the handwritten notes (along with group composition, group formation/rejoining,
group location, etc.) eliminate the need for the GPS notes you have been seeing
or is there other oddball information in there that would not normally be
written in the subgroup notes?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks – hope this helps.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Niki<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><u>Susan wrote:<o:p></o:p></u></b></p>
<p class=MsoPlainText>Points:<o:p></o:p></p>
<p class=MsoPlainText>1. Other groups notes will not change in the way they are
taken. The team will still hand write all inter group encounters, will still
hand write the GPS readings that are associated with intergroup encounters,
will still note when other groups use resources (water, groves). The only thing
that will change is that when a GPS reading is taken solely on an "other
group sighting" (not an intergroup encounter) it will be entered as a
waypoint, rather than written in the notebooks. Sounds OK?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>2. Subgroups: Yes they have been consistently recording
formation, composition and dissolution of subgroups when they detect them. This
has not slipped. They have done nothing about location of subgroups.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>3. Jeanne said: WE CAN'T TELL FROM THIS HOW THEY RECORD
THEIR COMINGS AND GOINGS BETWEEN<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> SUBGROUPS NOW OR THE LOCATIONS OF THE SUBGROUPS. IN
OTHER WORDS, IS <o:p></o:p></p>
<p class=MsoPlainText>> THAT INFORMATION BEING RECORDED IN THE HANDWRITTEN
RECORDS, JUST NOT <o:p></o:p></p>
<p class=MsoPlainText>> IN THE GPS RECORDS, OR NOT RELIABLY RECORDED AT ALL?<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>It is not recorded at all.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>We could not think of any easy and natural way to record
this information (and are not sure exactly what information would be recorded).<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>What would you suggest?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><u>Katherine wrote:</u></b><o:p></o:p></p>
<p class=MsoPlainText>The decisions on the Other Group notes sound terrific -
I'm excited about that plan. Also, that's wonderful confirmation
regarding the consistency of record keeping with the hand-written Subgroup
notes - thanks!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText>I'm stumped on a quick and easy way to record this. Jeanne
mentioned yesterday that it could be queried after data collection by checking
which animals were the subject of focal follow-throughs against membership
lists for each of the subgroups. The only time I think that wouldn't work
is when the team moves between subgroups throughout the day, whether for
observations or just GPS readings. I'm not sure how often the team tries
to sample both subgroups on days when a group breaks apart, though - maybe it
is uncommon enough to not be a concern?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>