Jim Gill of Hanzo keeps providing great posts that drill down into the specifics of different ESI sources. In his latest article, he pits Google Drive API vs. Vault.
The article Google Ediscovery Best Practices: Drive API vs. Vault, Jim discusses that just because an Application Programming Interface (API) is available, doesn’t mean it may be suited for the eDiscovery 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.
Not only that, but 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, which has more than one API which can give 3rd party software access: Drive API and Google Vault.
So, how do each of the Google APIs work? And what are the considerations you need to keep in mind when comparing Drive API vs. Vault? You’ll have to read his blog post here to find out! It’s just one more click!
Webinar alert! Hanzo is conducting its next installment in its Luminary Series (How Recent Regulatory Rulings Are Shaping Compliance) on July 28th at 1pm ET! This installment will feature a discussion with former United States Magistrate Judge for the District of New Jersey, Ron Hedges, who is a Senior Counsel with Dentons.
In this Luminary Chat with Jim and Judge Hedges, you’ll learn:
- How settlement agreements entered by the Federal Trade Commission have shaped compliance policy
- Two approaches to cybersecurity best practices
- Which standards are deemed reasonable under the New York Shield Act
- Compliance Guidelines of the US Department of Justice
Register here to attend!
So, what do you think? Do you have a preference between Drive API vs. Vault when it comes to eDiscovery? Please share any comments you might have or if you’d like to know more about a particular topic.
Disclosure: Hanzo is an Educational Partner and sponsor of eDiscovery Today
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.