<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></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jake,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You and Alan are to be commended for all of your hard work in developing and launching some great tools.  We realize they’re a work in progress and refinement will take some time and lots of ideas.  Let’s all contribute and see how it shakes out.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree with Scott’s comments regarding liars.  They’ve always been around and always will be.  Nothing will stop a truly determined person.  In trying to stop them you risk frustrating good folks too.  This happened with the OFVC logbooks in the 90’s.  Access was restricted and many gazers refused to report observations.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>People do make mistakes.  Questionable reports might first be kicked back (R U sure?) to allow a reporter to correct an error.  Next the report should be flagged.  The flag might say “Pending confirmation” or some such thing.  Confirmation should be done preferably by a reliable source, certainly not by the original reporter.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Sources making an uncorrected honest error should not be instantly restricted.  Perhaps assign a strike for each bad entry.  3 strikes and you’re out.  Of course, someone could resurface under another guise.  Perhaps their IP address or other background identifier could be included in their grade.  I suggest displaying the reporter’s grade in the detailed report, perhaps only for certain “high-level” users to see.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";color:#007600'>Thanks,</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <br></span><span style='font-size:13.5pt;font-family:"Script MT Bold";color:#007600'>Udo Freund</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br><br></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> geysers-bounces@lists.wallawalla.edu [mailto:geysers-bounces@lists.wallawalla.edu] <b>On Behalf Of </b>Jacob Young<br><b>Sent:</b> Tuesday, October 11, 2011 6:29 PM<br><b>To:</b> 'Geyser Reports'<br><b>Subject:</b> EXTERNAL: [Geysers] Online Logs (Young)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='background:white'><span style='color:black'>As the developer of GeyserTimes.org, one of the online logs for geyser data, I would like to enter a few points for the discussion about the online logs that was started by an erroneous report of Giant Geyser erupting.<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>  <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>Overview<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>Both Alan Glennon (geysers.net and associated Geyser Notebook Android App) and I have developed similar systems for collecting and reporting geyser information.  We've been treating this first season (2011) as beta-testing of the concept of storing geyser data in this way.  Neither of us have formally announced the existence of these sites, but they have quickly grown to be used by not just gazers, but casual visitors as well.  So far, it has been going quite well and we continue to be very excited by the possibilities going forward.<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>For now, there are two separate sites with slightly different focuses, but we are sharing reports openly with each other.  GeyserTimes.org requires entrants to have a user account; geysers.net/Android App does not.  Both sites receive erroneous reports.  The current methods in place for controlling user reports is through "flagging" of erroneous reports by other users.  <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>Erroneous Entries<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>Over 1,000 people have downloaded Alan's Geyser Notebook App this season.  We often get anonymous reports of Anemone (first geyser on the list) and White Dome (last geyser on the list) and also Old Faithful.  Anemone reports are difficult to dismiss as false.  A White Dome report can likely be dismissed if it was entered within minutes of the eruption time (there's no internet/cell service at the Lower Geyser Basin).  Old Faithful is watched very faithfully by webcam watchers and they do a fine job of keeping (daytime) Old Faithful data clean.<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>Now, the issue of the Giant entry.  It was entered by "guest" (ie anonymous) at 3am for a 0250 eruption.  While initially very exciting, it's not very probable that Giant did erupt and should be met with much skepticism because 1) Giant hasn't erupted for awhile. 2) It's an anonymous report with no comments.  3) Who was out in the basin at 3 in the morning in mid-October?<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'>As it happened, a few gazers took a look at Giant the next day and saw (based on the in-place signs) that it had not erupted and the report was flagged away.<o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='color:black'><br>I don't know what the best way is to handle these situations and I look to the gazer community to help decide.  This is exactly the time to address these types of issues while the sites are still in their infancy.  You might say to disallow anonymous reports, but what if Giant really had erupted and someone didn't want to go through the trouble of creating a login?  Perhaps there should be a secondary hoop to jump through before being allowed to enter such a major geyser eruption.<br><br>Purpose of Online Logs<br><br>There seems to be three primary purposes of the online log:<br>1) As a tool to help real-time geyser gazing (if you have access to a smart-phone or internet at Old Faithful)<br>2) As a tool to help NEAR-time geyser gazing (i.e. people driving in from West Yellowstone)<br>3) Long-term data storage/retrieval system<br><br>Our Giant entry issue was pretty easy to clean up to address purpose #3, but probably caused some undue excitement for people in case #1.<br><br>Conclusion<br><br>We're working to create an universal, robust system to store geyser data.  We need the gazer community's input to do this in the best way possible.  The online log is functional and gazer response has been positive and encouraging, but it still has a long ways to go.  I want there to be a discussion about this, but also don't want to hijack the listserv so feel free to send your comments to my personal email jakefrisbee@yahoo.com if you'd like.<br><br>Happy Gazing,<br>Jake<o:p></o:p></span></p><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='color:black'><o:p> </o:p></span></p></div></div></div></body></html>