Name: Data, Deadlines, and Drama: Making eDiscovery Processing Less Painful
Uploaded: 2025-03-11T16:46:05.268Z
Duration: 27 min 40 s
Description: Data, Deadlines, and Drama: Making eDiscovery Processing Less Painful

Transcript for "Data, Deadlines, and Drama: Making eDiscovery Processing Less Painful": Everyone I hope everyone can hear me okay. As if you can hear me, please jump in the chat and just drop in a yes or a comment just to make sure that everything's going through properly. Just to get us started, as people are slowly getting in here, I'm gonna give us a quick introduction. Thank you so much, guys. Appreciate it. Hi, everyone. I'm Jacqueline Murphy, and I'm excited today to talk to you guys to dive into data, deadlines, and drama, making ediscovery processing less painful. Processing data has for ediscovery has traditionally been complex, requiring significant IT setup, virtual machines, and constant maintenance. But with advancements in cloud technology, that's changing. Today, we're gonna be exploring how Reveal's web based processing is transforming e discovery, eliminating outdated barriers, and giving teams greater flexibility, scalability, and speed. Today, we've got two fantastic speakers leading today's discussion, Ryan Nichols and David Shedd, both experts in ediscovery legal technology, and both guys I know personally, they're really funny and great to be with. Ryan Nichols is today is Reveal's VP of product review and processing, with eighteen years of ediscovery experience, Ryan leads our product innovation, ensuring reveals AI powered solutions simplify complex workflows for legal teams. David Shedd is our VP of sales engineering, specializing in AI, automation, and scaling legal technologies. He's play he's played a key role in shaping Reveal's platform, making it easier for teams to process massive amounts of data more efficiently. As for me, I'm Jacqueline Murphy. I'm a marketing campaigns manager here at Reveal, somebody who puts together marketing campaigns for you guys to make sure that these are hope hopeful and helpful conversations to improve your workflows and to make things more exciting. If you guys ever have any more suggestions for webinars or things like this that I can bring to you, please drop it in the chat or send an email, to marketing@revealdata.com, and I would love to hear more suggestions. But today, we're gonna be covering key improvements, like best practices, strategy that can help legal teams process data more efficiently while reducing technical headaches. Feel free to drop in your questions in the chat, and at the very end of the session, we'll try to address those as much as we can. Without further ado, I'm gonna pass this off to Ryan and to David to kick us off. Alright. Thank you so much for that introduction. Really nice to be with you here all today. So, again, my name is Ryan Nichols. I'm gonna start sharing my screen here and we're going to just kinda dive right in. What's your, looking at now is, basically our presentation here today, which is about web data processing and early case assessment. This is the general agenda that we're gonna be following. So first, we're gonna just kinda talk about the processing to the web status update. This is an initiative that we've had ongoing for a bit here at Reveal. So we're gonna talk about the current state. I'm gonna show you some updates on that. We're gonna talk a little bit about the processing grid of error handling, and then I'm gonna pass it over to my colleague David Shedd. And David is gonna talk about a new concept to reveal, which is about ECA or early case assessment and functionality, which was available in a certain flavor in the current version of reveal and pretty soon will be available in some additional, options for you. And then we'll have a brief q and a session at the end. So, to talk about the current state of the web data processing, I went ahead and put things into three buckets. So there's the delivered, which everybody has had for, you know, at least a few months at this point with being able to upload data from the web and being able to upload, data directly to review. Right? So what, what was just released very recently in our, March release year reveal, which was twenty twenty five dot two with some new workflows. So there was the upload without processing workflow and the ability to browse uploaded data. So that is in an early access stage. So it's something that we can get anybody who's a current customer in there and looking at. What's coming up is the error handling, which is previously kind of called import QC. We have the data filtering and promotion section, which was what we previously kind of referred to as selective sets. And we're also working on a local application uploader. So the web uploader is an item that we're constantly iterating on. We made quite a few additions and updates during the twenty twenty five dot two release. And that has been a very strong option. But there's gonna be situations where there is an awful lot of data that needs to be uploaded all in one go. So we are kind of working in the background here about having a local application that's gonna let you push larger amounts of data to, to your project really seamlessly still by being able to use the browser, but also kind of pair it with a local web app. So we're not ready to get into all the details on that one, but we definitely wanted to, you know, just kind of let you know that that was coming down the pipe. So, before I get into a demo of, kind of the recent functionality that we rolled out that's in that early, access phase, there's really two workflows that are relevant for Reveal and also just kind of relevant in the discovery industry in general. So on the left hand side of my screen, I have the review workflow, which is, you know, pretty standard, EDRM type model and then the ECA workflow, which is a modification. So all of these things are an iterative process. It's pretty rare or not necessarily frequent any discovery where you just get data once typically you're having data come in all the time. So you can imagine that with the workflow that we have had available, in our discovery manager web process, there has been the uploading of data and then the exception handling and then the promotion to review. That workflow is going to be very similar with ECA. But if you take a look, there's a new option that's in there, which is the promotion to ECA. And the whole idea behind this is that we want you to be able to have people preview the data before you take the action to promote it to review. And there's a lot of reasons for that. Know, part of it is you want to reduce the amount of data that's getting into review, getting into our ECA pipeline or I'm sorry, our analytic pipeline. And it's also, you know, depending on how you're working with your customers, there can be kind of that as the instance of when, your your licensing charges are gonna go up. So being able to look at the data, being able to share that information before it gets to review, is something that we've made easier than ever, and that we're really excited about. So when we are pushing out this discovery manager to web initiative or this processing to web initiative, what we are going to be doing is releasing the ECA and the processing piece, with the error handling at the same time. So that's gonna be, a joint effort that you'll be able to see. So, David's gonna get into a little bit more detail, show some actual screens about how that's gonna look. But before that happens, I'm gonna go ahead and show you some of the recent updates that are in the early access phase. What I have here is the latest version of Reveal, which is the 02/2002. I have made a project specifically for this webinar, which is this processing ECA project. I'm gonna go ahead and open it, and you can see that there is no, data that's been reviewed here. So, as you can see, there is no no data that's been pushed to review. If I go to processing, you can see there's been two, there's been one processing job, and that is from actually two uploads. So on this upload phase, you can see that there's one where we called it PST process only and one called PST upload only. So if I click on any of these upload jobs, you can see what workflow was selected during that upload process. So this is the workflow for upload and process data. What's not happening there is the promotion to review, which is why you didn't see any data in review when I was on that screen. The other piece here is upload only, and this is a really big one. We wanna make it so when you were working with your customers or your internal teams, they can upload data, but you don't necessarily have to give them the ability to process the data. They can simply upload it and keep it put. Right? So the first workflow that we showed there was the data processing workflow. So if I were to go to processing here, you can see that there was one job that was processed. Again, nothing's been promoted to review, so it's just in that phase. Now what I wanna be able to do here is is when I have data that's been uploaded, I wanna have the ability to, now choose to select it and process it. So when I come to this processing jobs section here, the data that's already been processed is obviously visible here. But we've got this new button here for process data. And what this is gonna do is show you that data upload. So this secondary upload that we did, you can now see here. And you can see that this is named in the, same way that we would upload data previously. I can choose my custodian, my location, and my source just like you would typically. And you can see that there's two workflows that are available here. The first is I now wanna process this and promote it to review, or maybe you wanna only process only. That process only is where you would use the ECA workflow that we're gonna talk about in a few minutes. The process in promote to review is to say, you know, I'm ready to go. I want my reviewers, looking at my data right away. And so that is the option that you have available to you there. The other thing that we've added in this promote to review jobs is when you have data that's been processed, but you're ready to promote it, which is just moving the data or, you know, making the data available in review, you have this promote to review button. When you click on it, you can see any completed processing job. And you simply just give it a name for this job. You would select one or more of the completed processing jobs and hit promote. And that would, initiate the pipeline to get the data into, the analytics pipeline for getting all the concept conceptual clustering, sentiment analysis, and so on, as well as indexing to make that data available for search and review. So the really important thing here is that you have the ability to really, separate your data out into various phases, to be able to get data through the process and whatever workflow makes the most sense for you and the people you're working with. A couple of points about this. One is when we look at the processing jobs and you're taking a look at data that's been uploaded, you're not seeing the entire s three bucket, which is where data gets uploaded in reveal, which is just your storage location for your account. You're only seeing a folder for your project. So if you were to imagine the, backend, you have your s three folder, you have a temporary folder. What's gonna happen when you're doing this is we create a new folder that's named after the project. And then underneath that project, each upload is placed into its own folder. So you could, upload the data that you've done previously or you could, upload individual files or folders from there. So that is a option that's available to you. And it really like I said, it allows you to have your customers upload the data and for you to come in afterwards and handle it. The, the other substantial upgrade that we made here is when you're doing an upload, just call this upload three. I'm gonna say this is an upload only job. You can now do both files and folders. Previously, we just allowed you to do folders. So you can actually select both of them and they'll both pull up in that list. So you can choose individual files, individual folders. If you choose individual files, you have the ability to associate the custodian location source on that individual file level without having to run multiple upload jobs. So that's another substantial, upgrade that we need to the system here. K. So if you have any questions about this, please feel free to add them to the chat. Otherwise, I am gonna go ahead and hand this over to my colleague David. So David, are you ready to show your portion? Yes. I am. Thank you, Ryan. I appreciate it, and I can take over from here. Alright. Thanks very much. Okay. Let me go ahead and share my screen here. Alright. Thanks. And so we are gonna be talking about ECA in in particular. Now I know this is you know, you go to, a trade show and someone says, what is blockchain? And that makes you very upset. So for those of you that understand ECA, you can tune out here. But for those of you that don't, ECA is early case assessment, and it's refers to the processes of quickly analyzing data to analyze potential risks, the scope of the case, do I have a case? It's a critical step in eDiscovery. It's going to help you make smart decisions but more importantly optimize your time and costs. And there's many reasons that people use ECA here are just some of the ones that are there listed. Now in terms of what we've built when we started building this, I've heard a lot that people say, oh, if you're gonna go to do processing in the web, processing in the web is a black box. I don't like it. So when we were building that, we took these concerns into account, and it became apparent to me that our differentiators were speed, consistency, transparency, and most importantly, what Ryan just touched on was is self serve. So in terms of speed, we re architected everything to run from a new elastic index, which mimics review. So this allows us to bring sub second searching to both processing and ECA. Also, the promotion from processing that Ryan just showed you to ECA is instantaneous. It's gonna leverage the same index and is simply a a hide unhide flag. So you're gonna get tremendous speed out of this. For consistency, we are gonna leverage the reveal query language or RQL across everything now. So this is gonna allow for the same search syntax, search process, and all aspects of the Reveal product. Now in terms of transparency, we are going to give you tools and you saw to identify and remediate exceptions, but we're also gonna have search history, save searches, new dashboards that will provide you knowledge at a glance. So this will eliminate the black box feel of older platforms. And finally and most importantly, you now truly have a self-service model for your customers or your end clients. So let your end client come in, use all of this functionality to move their case along, and they can you can focus on consulting the users rather than doing their work if you wish. Okay so before we dive in we wanted to set expectations and show some of the things that we are going to have in terms of functionality in the ECA components. So first we're going to be doing user feedback. We're going to be iterating very quickly and getting a lot of the user feedback. So the more that you can get back to us and let us know what you like, you don't like, things of that nature, we can come in and build that in. We are gonna be looking to have safe searches and work folders in. Safe searches are dynamic. Work folders are static. You can think of work folders almost like tags, but it's going to be a static save search of documents that you're moving data in chunks here really. And so that's the way to think about ECA. It's not really a doc by doc thing. It's more of a a bulk action thing. We're not gonna have any data analytics or AI here. Also, just like I said about work folders, there will be no individual tags, but, again, the work folder should suffice for that. There's gonna be text and metadata only in here. We won't have a native file, and we're gonna have a new permission where those who have access to ECA can do ECA, and they're gonna have the ability to promote and do those things over time. We may add other permissions to bifurcate that, but for right now, anyone who has access to ECA is going to be able to do it. So on that note, let me hop in. So just as we left Ryan, he had talked about in the processing grid or processing module, we would have the ability to remediate exceptions, isolate documents, and then we're gonna be able to click on promote. And when you are gonna promote you're gonna be have two options here. You're gonna have the ECA option which I'm gonna cover. He just talked about review, but review would just skip ECA and go right into review. And so when we go ahead and promote to ECA, it's gonna go down into this new module that's sitting underneath processing. And it's going to be instantaneous, so that's gonna be fantastic. Again, speed is one of those differentiators I talked about. I'm going to be able to click on a document here and have the text view slide in. I'm going to be able to look and read the documents and see what I have. I'm gonna have filters over here that I can filter the data easily. And of course the search, the RQL. I can run complex or easy searches in here. I can have search history or I can click on my saved searches and have them here. This is gonna create workflow repeatability. I can go ahead and say I have a very simple workflow here that's a complicated search of not promoted docs, certain file types I want to exclude or keep, however you want to see fit. These will be all things that you'll have in the system. So if I click on here and I run my search for not promoted docs, I'm now into a subset in here. And again, I could filter more of the documents, but very simply what I'm gonna do is click promote, and now it's gonna be back into that kind of wizard view that you saw Ryan present. It's gonna have the ability to go text and natives only or text only. So you could go from here and just push text into Revu if you want to hit it with AI and analytics before you promote the native. So again this is we call it ECA. It might be to some folks on the webinar today more of an EDA where I'm calling and filtering the data and really setting the ballpark for my AI and analytics to kick in. I can do my numbering. I can set all that. We're gonna remember that number for you, so you don't need to worry about it. If you set a new prefix, it's gonna start at one. And I'm gonna click promote, and that's gonna promote the data. Now here's something that I think is really, really, really cool and I love. When we're in the ECA component here or we're in processing, we are showing you all the data with duplicates included. When we go ahead here and click promote to review and the previous module and processing or from ECA if I promote to review, it's actually now deduping. So it's gonna if there's data already in your review, it's gonna come right in underneath that and dedupe it there. So I don't need to worry about this whole component of global dedupe versus do I need to process this or that? This is gonna create so many efficiencies in the process. As an example, let's say that you get a terabyte of data and in a lot of tools, you need to upload one custodian at a time and make sure they're in a specific order because it's first in first out processing and deduplication. You will not need to do that here. You're gonna gain so much speed and efficiency in this by just this little twist here of putting the deduplication at the stage. I can load all data in and get the last custodian who is the most important person, and now just push that custodians data, and that will now maintain the most master copies because it's deduping here. So, again, there are so many cool pieces of this in the differentiators that I think of of the speed, the consistency, the transparency, and, of course, the self serve nature of this is gonna be fantastic for those that, are wanting to get that work off their plate and get more to that consultative role. And that's all I really had. So I hope everybody found that fascinating and the great things that we're showing and doing here in the webinar. Turn it back over to you. Thanks very much. That was awesome. I hope everyone's today's session gave you guys a little bit of a clear picture of how web processing is gonna web based processing is, you know, is simplifying ediscovery workflows and eliminating some of those complex IT setups. I wanna take a few minutes just to go over some of the deeper questions that we got here. I'm lucky that we have, that here it looks like I got a couple of good questions. I tried to answer a few of them early on, and I see two questions on here as well that I commonly see often. I'm gonna invite David and Ryan to jump back on here and just answer those two quick questions. Any second now. Leave it to you guys. Thanks. Cool. Thanks. Yeah. So thanks, Jacqueline. So we, we're taking a look at some of the questions that we received in the chat. The first one that we received was, you you know, about how does this work in terms of billing? So the big thing to know about what we've done here is that we have taken the existing, discovery manager processing engine and just made it available in the front end. The real advantage of this is that the processing piece of Reveal is battle tested. It's been in use for well over a decade at this point. So we're not actually trying to create new processing from scratch. What we're doing is taking what already exists and making it more accessible to people and making it so that it is, easier to get data in and out of the system. So the same, methodology that happens in the discovery manager, is going to exist in this new, ECA module. The big difference is when we thought about how to do processing to the web, we did not just want to take what was already there and just redo it for the sake of redoing it. We really wanted to make sure we were doing it in a thoughtful way. And so what we came up with is what David kind of showed there, which was we have the ability to do these complex searches, to filter your data, to look at your data before you promote it. The the the additional piece of this that's really important is that, there isn't really a great way for your end customer to do complex searches of data prior to being moved to re hosting today. And the ECA module allows for that. Right? And so you can have your customers or your your clients or your business partners get in there, and they can run these searches and look at the data and decide, yep. This is what I really want. That should make it much more easier for you and your team to, you know, figure out billing and making sure the right data is making it to review, and that's a really big part of this. So the ECA does not create a new billing, construct at this point. It's really just another way to look at the data and to share data results prior to moving things to review. And then, so that's it on that one, Jacqueline. And then I I just posted a response for the other one. So will clients have the option to switch off deduplication from the ECA when they promote to review? Yes. So, one thing that I heard, especially from our construction partners is that they wanted the ability to dedupe emails, but not e files a lot of times specifically because they have a bunch of project data that they wanna make sure remains in the original folder structure. And so we talked about that a lot back and forth. And, the the methodology we came up with is to say, when you promote data to review, you can either add it to the existing dedupe logic that's in there, or you can say, don't dedupe this data. And so, when you run this search, you would do two different promotions in that case. You would do one with the dedupe turned on and one without. And how you organize your data is kinda be kind up to you. You could have those be two different processing jobs or single processing job, but that is that is the intention. So we're trying to get away from a lot of additional overhead for managing things like deduplication, but still giving people flexibility. So I think we found a good balance, with with how we're approaching that here. But keep in mind, this is a v one of what we're doing. This is not the last, you know, bit that we're gonna be doing for data processing. So as we get feedback from people that are in the system, if we, feel that there's a need for more flexibility or more workflows, we're certainly gonna be up for for doing that. The big thing just from a from a perspective of what we're trying to get to is processing is very commoditized at this point. So we wanna make sure that what we're doing allows data to just quickly get in quickly get out without a bunch of training, without a bunch of overhead, make it very, very simple. So anything that's going to take away from that, we have to very much consider whether it's worth it. So that is the back and forth that we're balancing there. Awesome. I don't see any more questions coming in on the chat for the time being. For anyone who did ask, I saw one person was asking if there's gonna be any PDF notes about this. A great question. I will be writing a blog about this webinar, summarizing what we kinda talked about today, as well as answering any additional questions that people wanna drop here in the chat. Or if you end up watching this webinar on demand, we'll ask answering questions in the chat. I'll try to grab those before, end up publishing that. And finally, the only other question I see on here is what is ECA? Hopefully, David was able to answer that question for you. But, and I thought since I see Luis was on here also, just jumping and adding a couple acronyms. So hopefully, that answered your questions. If there's anything else, don't be hesitate to drop it in the chat or q and a. But for the time being, I think that's all I see on here. So thank you guys so much. Thank you, David and Ryan, for jumping on to talk to us about our processing. This is exciting stuff. I know I get really excited about it. And so I appreciate everybody who was able to jump on today and ask some questions and learn a little bit more. We're excited to to launch this and to see how we're continuing to advance this and some of our other products coming out. So thank you so much. Thank you. Awesome. Have a great one. Hey, everyone.