{"id":309,"date":"2012-11-26T16:23:02","date_gmt":"2012-11-26T16:23:02","guid":{"rendered":"http:\/\/jolt.richmond.edu\/wordpress\/?p=309"},"modified":"2019-03-08T19:52:38","modified_gmt":"2019-03-09T00:52:38","slug":"metadata-can-you-use-it-should-you-scrub-it-it-depends-where-you-are","status":"publish","type":"post","link":"https:\/\/blog.richmond.edu\/jolt\/2012\/11\/26\/metadata-can-you-use-it-should-you-scrub-it-it-depends-where-you-are\/","title":{"rendered":"Blog: Metadata: Can You Use It? Should You Scrub It? It Depends Where You Are"},"content":{"rendered":"<p>By Associate Tech Editor Hayley Mohr<\/p>\n<p>&#8220;If you have it, you should not show it to others. If you receive it, you cannot look at it.&#8221;\u00a0 The previous statement is not a riddle, rather; it&#8217;s a paraphrase of <a href=\"http:\/\/www.azbar.org\/Ethics\/EthicsOpinions\/ViewEthicsOpinion?id=695\">Arizona&#8217;s Ethics Opinion on the use of metadata<\/a>.\u00a0 Contrast this outlook with <a href=\"http:\/\/www.osbar.org\/_docs\/ethics\/2011-187.pdf\">Oregon&#8217;s<\/a>, among other states, which allows attorneys to use it if they do not use a&#8221;special software&#8221; to view the data \u2013 in other words, if you can find it without looking too hard, it&#8217;s yours! So, what is metadata, and why does the permissiveness of its use and transmission vary so widely from state to state?<\/p>\n<p><a href=\"http:\/\/www.niso.org\/publications\/press\/UnderstandingMetadata.pdf\">Metadata<\/a>, which exists in several different types but is often termed &#8220;data about data&#8221;, has become a near-minefield to parties to litigation and the attorneys that represent them.\u00a0 A common example of metadata is a word processor file that contains information about when the file was created, and when it was last edited.\u00a0 It becomes dangerous quickly, when one considers the vast features available in a standard word processing program: documents can contain &#8220;erased&#8221; sentences and information \u2013after all, in order for the &#8220;undo&#8221; button to work, the file has to &#8220;remember&#8221; what the previous version contained.<\/p>\n<p>One of the most changing and varied areas of law at the moment is the proper use of metadata: both when it accompanies documents produced in response to a discovery request and outside of formal discovery.\u00a0 Contrary to the &#8220;show no metadata, see no metadata&#8221; approach of many states, one of the earliest and cases to deal with the proper use of metadata, <em>Williams v. Sprint<a title=\"\" href=\"https:\/\/jolt.richmond.edu\/Users\/cf9zc\/Downloads\/metadata,%20scrubbing,%20discovery.docx#_ftn1\"><strong>[1]<\/strong><\/a><\/em>,\u00a0 held that the defendant in an age discrimination suit violated the discovery order by &#8220;scrubbing&#8221; metadata from a table of employees produced to the plaintiff.\u00a0 The court held that documents maintained in the regular course of business should be produced in the same format, and that the scrubbed metadata was relevant to the case.<a title=\"\" href=\"https:\/\/jolt.richmond.edu\/Users\/cf9zc\/Downloads\/metadata,%20scrubbing,%20discovery.docx#_ftn2\">[2]<\/a><\/p>\n<p>Certainly, many lawyers are excited by the prospect of following a digital treasure hunt\u00a0 to examine the motives and concealed actions of defendants, and other parties are terrified at the prospect of having their comment and mistakes revealed \u2013 if metadata is likely to lead to reliable and useful evidence, why prohibit it from being used?\u00a0 Many are concerned about the ability of commercial software to fully &#8220;scrub&#8221; these documents, the cost of doing so, and the fact that the technology becomes more and more sophisticated.<\/p>\n<p>Ultimately, there are no hard-and-fast rules to follow when it comes to producing, using, or cleaning files of metadata.\u00a0 What is right in one state is, literally, wrong in another. (See the <a href=\"http:\/\/www.americanbar.org\/groups\/departments_offices\/legal_technology_resources\/resources\/charts_fyis\/metadatachart.html\">ABA&#8217;s chart<\/a> for a helpful overview of the ethics standards by jurisdiction.)\u00a0 It will be interesting to observe over the next decade what internal changes and\u00a0 innovations companies will make in order to avoid the metadata minefield altogether .<\/p>\n<div>\n<p>&nbsp;<\/p>\n<hr align=\"left\" size=\"1\" width=\"33%\" \/>\n<div>\n<p><a title=\"\" href=\"https:\/\/jolt.richmond.edu\/Users\/cf9zc\/Downloads\/metadata,%20scrubbing,%20discovery.docx#_ftnref1\">[1]<\/a> 230 F.R.D. 640, (D. Kansas 2005)<\/p>\n<\/div>\n<div>\n<p><a title=\"\" href=\"https:\/\/jolt.richmond.edu\/Users\/cf9zc\/Downloads\/metadata,%20scrubbing,%20discovery.docx#_ftnref2\">[2]<\/a> For a comprehensive overview of decisions related to metadata, <em>see <\/em>Marjorie A. Shields, Annotation, Discoverability of Metadata, 29 A.L.R.6th 167 (2007).<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>By Associate Tech Editor Hayley Mohr &#8220;If you have it, you should not show it to others. If you receive it, you cannot look at it.&#8221;\u00a0 The previous statement is not a riddle, rather; it&#8217;s a paraphrase of Arizona&#8217;s Ethics Opinion on the use of metadata.\u00a0 Contrast this outlook with Oregon&#8217;s, among other states, which [&hellip;]<\/p>\n","protected":false},"author":4287,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[51366],"tags":[24534],"class_list":["post-309","post","type-post","status-publish","format-standard","hentry","category-blog-post","tag-metadata"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/paMHOZ-4Z","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/posts\/309","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/users\/4287"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/comments?post=309"}],"version-history":[{"count":0,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/posts\/309\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/media?parent=309"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/categories?post=309"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.richmond.edu\/jolt\/wp-json\/wp\/v2\/tags?post=309"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}