It’s “year-end list season”, and Jim Gill of Hanzo is a man for the season with the top 20 Hanzo posts of the year over two blog posts!
Complex data sources – such as chat messages or a SaaS application’s user interface – are called that for a reason in the world of ediscovery: namely because it’s challenging to reproduce the data in a way that’s useful for attorneys and investigators.
In recent case law, there have been a number of examples of courts requesting screenshots as a way to present the evidence at hand. But do screenshots meet the “best evidence rule?”
And here’s one from this week’s post:
Just because an API is available, doesn’t mean it may be suited for the task at hand. Some APIs are limited in the data and metadata they capture. So even if there is an API and a solution can connect to it, doesn’t mean you’ll get what you need. In other cases, there may be more than one API available for a particular data source, where one may be more effective for a particular use case than another. A good example of this is with Google Drive.
So, what do you think? Did you miss any? If so, catch them via these two posts! Please share any comments you might have or if you’d like to know more about a particular topic.
Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by my employer, my partners or my clients. eDiscovery Today is made available solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Today should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.