2014 Blogging Archaeology eBook

that they did not want me there and wanted to try to sue the regulatoryagencies to get us to go away. However, no reader of my blog wouldknow who my clients were, much less which ones were in either of thesecamps.Know what belongs to you, to the archaeologicalcommunity, and what belongs to your client oremployer.Some of the information generated by your work belongs to thearchaeological community; some of it belongs to your client. Know thedifference and act accordingly.A separate issue is that of ownership of information and materials. Formost projects, it should be assumed that, at the very least, the projectlocation, description (that is, the description of what the client wishes todo/build), and project photographs are client property. This means thatyou should not discuss them in your blog entries. This is typically simple –most archaeology blog readers aren’t going to care overly much aboutthe technical specifications of an electrical peaking station, or that itwas placed in Bigol County and not Goodolboy County.However, it is common to see CRM archaeologists post photographstaken during fieldwork to their blogs (I have even done it in the past,though I have stopped doing so now). Most of the time, your clientswon’t care, but you should always err on the side of caution. Onoccasion, it might even get you fired (hey, if Chris Webster can get firedfor simply announcing where he is on Twitter or mentioning publiclyknown information on his blog [Webster 2013], don’t assume that yourjob is secure if you post things that are literally your client’s property). Ifyou must post photos of your project area, be sure to not describe thetype of project, and to post photos taken A) with your own personalcamera, B) outside of work hours, and C) from publicly accessibleplaces.Blogging Archaeology Page 27