Video: Fall Feature Updates 2024 | Duration: 1832s | Summary: Fall Feature Updates 2024

Transcript for "Fall Feature Updates 2024": Joining us. My name is Jacqueline Murphy. I'm a marketing campaigns manager here at Review, and a big part of my job is putting webinars and, campaigns and information and content out to you guys that will be helpful. Today, I'm joined by Billy and Ryan as we go into the newest features that were released this fall. Really exciting. We had a lot of really cool tools out there before we jump into it. And as we wait for a couple more people to join, I do wanna let you all know that that is gonna be a live q and a at the very end of this webinar. So throughout the webinar, feel free to ask your questions in the chat or the q and a function, and our team will make sure to see them and answer them till we save them for the end. We also might be answering some of them ahead of time via chat or messenger, so you'll see those answers below it, but definitely send in messages and we'll make sure to address this at the very end. Additionally, this webinar is gonna be available on demand after the fact. So if you decide that you have to jump out early for a meeting or whatever the case is, feel free to jump back into it later, and you will be able to watch what we've, what happened on today. And then last two things, at the very end of this webinar, I'm gonna send out a survey. This is just a quick 3 question message, and this is gonna be a great way for me as a marketing campaigns manager to make sure I'm getting you the resources you need and to make sure that our product team has great ideas and more things for the future as we create, more updates and features for you to you all. Finally, if you see here on the screen, you also will be able to download any resources under the docs tab on the right side of your screen. We have a couple of resources there that should be very helpful for you including our release notes for this past month. We don't have the new release for this upcoming month yet, but you should be able to see that soon as well as weekly webinar trainings we have going on. Our very own Griff, and his team on our marketing, products team creates webinars that happen live. They're very interactive, and they are amazing. So if you don't already, make sure you check those out. With further without further ado, I'm gonna pass this off to Ryan so he's gonna get us started on today's, future updates. Thanks so much. Alright. Well, excellent. Thanks so much for that introduction, Jacqueline. I'm gonna start sharing my screen here. So as Jacqueline said, I am the, vice president of product here at Reveal. I'm joined by my colleague Billy Belchove, who is also vice president of product here at Reveal. So a lot of my role has to do with integrating the large, number of really exciting products that we have to offer into one kind of singular package. So for the last year, we've really been working on this very large and, important initiative, which is to combine a lot of these executables and applications that previously required a load machine into our web interface. And so I've got just a slide to kinda talk about what we were hoping to accomplish, with that work and then, give you a little bit of an overview of the current status and then actually show you what we're doing. So when we decided this initiative, there's really 5 things that we really wanted to do. One is what we heard from customers is that the need to have, s three browser or some sort of other third party software to upload data to the system was cumbersome. Right? It also made it very difficult for our customers' customers to upload data, and do kind of their own, initializing of data processing. So this new workflow that we have, which we'll show today, allows that to happen, which is a a great, really handy improvement. We're not taking away the ability to upload data directly to s 3. We're just enhancing it by having some alternative options here. As I said just a moment ago, we're looking to get rid of the need to get into a load machine altogether to do any sort of administrative or data processing tasks. We're gonna have everything right there just in the same web interface. We're also making it so that everything can be controlled on a project and company level, rather than kind of the complete admin functionality that exists when you log in to load machine today. There's also this new concept of an instance manager, which goes a little bit beyond the scope, or sorry, an instance admin that goes a little bit beyond the scope of what we're talking about today. But that's another concept that's kind of in control of the entire environment that we introduced as part of this. We introduced in our last release the 2024.9, the ability to create a project for both processing review at the same time to really simplify that process. And then finally, and this is to be probably the most important part, we didn't just take what existed in the previous systems and say, let's just do it exactly as it was previously. You know, these systems are very powerful. We're actually using the same logic, especially when it comes to data processing. Data processing is very difficult to do right, and what we've done is taken the power of our existing discovery manager reveal processing application and just made it so you don't have to go through, an interface that is not the most user friendly and harder to teach. This thing that's a lot more streamlined. So with that, what we're gonna do first is just very briefly, I'm gonna talk about where we're at in our efforts with the review manager specifically. So the review manager is where you could do a couple of things primarily around the ability to, administrate a project, user access, but there was other things too, notably being able to do your templating, what we call our project settings, and then everything that has to do with loading data from a DAT file, whether that is a opposing party production or a third party DAT file, anything like that. That was something that required that admin access. So we're really thrilled today to actually show you where we're at on that. There's still work to be done, and what we've done is kind of divided this up into what have we already either delivered, or were, you know, given to some some select customers at this point, what is currently in testing, so kind of, more on the imminent side as long as testing goes as expected, and then what's an active development. Right? What are things that we are working on day to day here, and we'll be pushing to QA and testing as soon as we can? So as you can see, we're very close on the copy settings, the templates, the field mapping creation. What's happening next, which you'll actually see we're we're pretty far along in the development of, at least the initial phase, is the loading of a DAT file, right, directly from the browser. So what I'm gonna do is I'm now gonna actually log into Reveal, and, where I'm at is a whole new page that doesn't exist yet. This is in a development environment, so you'll see some other things that are a little bit different than maybe what you're seeing in your own. But what you'll find is that under project admin, we have a new section for field mappings. Field mappings are what we use to determine what items are going to be mapped in your load file to the revealed database. That was kind of a cumbersome process for a lot of reasons in the review manager. So myself and and Billy Bilichev and the really great engineering team we have here at Reveal really spend a lot of time thinking about how to improve that. So what I'm gonna show first is how you do that creation and mapping, and then I'll actually show you what it looks like to load data in the system at least for this early phase. So right now, we had some default ones, and I created this additional one called an opposing party map. The way this works is that I come in here and say that I'd like to create a new mapping. I'm gonna give this a name. In this case, I'll just call this mapping 2. One of the improvements that we put in here is the ability to auto detect a delimiter. And so if you're using standard concordance, you're using pipe caret, you're using CSV, it will auto detect. It can actually auto detect a little bit beyond that, but those are the 3 that are kind of officially supported, and you can see that in this drop down here. What I'm gonna do next is that I'm going to select a file. So I've got here this DAT file that's a production export. It's gonna let me know that it's got that available for me. And when I go to the next page, you're gonna see a lot that's quite a bit different, from maybe what you've seen before. So the first thing that we've done that I think is really important is that we've broken up the most core field mappings, into individual categories. So what we, heard from customers with the review manager is that it was hard to determine what I needed to map, what I needed to do to get native files into the system, what I needed to do to make sure the data analytics worked, and so on. So, there this is still a work in progress. There's some things that, you know, you'll you'll have to take a closer look at, when we're a little further along. But, for example, your big doc identifier, what do you need to do for that? So what you'll see here is that we have a page that's just for the identifier. There'll be one for the, parent, ID as well, and you can see that it did an auto match for me. I didn't have to do anything. It attempted to do an auto match, and I can reset that at any time. There's some really interesting things that we did here, and I think the most notable is that instead of just doing kind of a simple match, we also have kind of a thesaurus. And so what it will do is it actually looks for things like begin number or big doc or bigbaits or other common nomenclature that's used in this industry. And if it matches any of those, even if it's not a near match to the actual project field, it will still do that mapping for you. That's something that was introduced in our logical application recently. It was a great idea, so we we continued and brought that over to the Reveal application as well. The other thing that you'll notice as we're going through here is that we actually give you an example of this data once you do that mapping, over here on the right. So this is the first entry in your load file. So I can see that this load file starts at, document ID number 59 here. If I chose a different field, you would see that change to reflect that field. So if I chose volume, for example, which would not be correct, I can see that, and I can see that's wrong. At any point, I can reset and kinda go back to that mapping state to where it needed to be. Right? Just like that. So you'll see all of that behavior that you just saw here on this main page. So this is all your fields in load phone. It's letting me know that it's 32 fields that should match my expectations. I just showed the identifiers a moment ago. There is the analytics fields, and you can see this actually lets you know what fields are needed to run our communications analysis, our email threading, our near duplicate detection. It gives you a link to our documentation. And, really, what this is meant to do is just make sure that people know what they need to ask for, when they're doing these mappings and also to, just make sure that, you know, when you're doing the mappings on your end, you're not missing anything. Right? You're mapping it to the correct field. So, again, I can see kind of the preview here. If I were to choose a field, the ones that are already selected are kinda grayed out here, and I can do things like, apply filters and such. So if I wanted to look for something like bcc, you can see that I can type and I can pull that up in the filter. One of the other things that's really kind of a huge improvement here is you'll notice on the left hand side, this is actually the, reveal database name, and then this is your load file field. But if I go to some of these, other pieces, you can see this is actually the load file field with the project field on the right. One of the things that we heard from customers is that before we had many, many fields in each project, and you had to go through this very large list to get it to what you were looking for. So now we greatly simplify that. And what this does is instead of having to look through a list of every SQL field, you're just looking at the fields in your load file and making sure that those are mapped. Okay? Once you have everything in a spot that you'd like, you can do a preview here. And when you do that, it actually is gonna give you a readout of your first 100 rows. So in this case, I can see what are in all of these, load files. Right? And as I go to the right, you'll see that if there's an error, it will let me know that. Now in this case, this is a file size error. It's letting me know that there's a comma in here. So a comma is not compatible with a with a numeric value, so it's letting me know that that's not, compatible for me. K. So there's kind of this really quick validation. You can see it happens entirely in browser. It's very quick in terms of being able to load that. Once you've actually, you know, gone through this and you have a mapping that you're comfortable with, you can go ahead and hit save and go from there. K? So now that you've made that mapping, and you actually don't have to predo it. You can do it during the upload phase as well. I'm gonna go ahead and move to my uploads, and what I'm gonna do is click a new upload. So this is gonna show 2 different sections, native files and load files. I'm gonna come back and do native files in just a few minutes here. But in this case, I'm gonna go ahead and call this DAT 2. I can give this a description if I'd like. Like, this is the 2nd production. The options you see underneath this are going to change depending on whether it's a dat file, or native files. Right? In this case, I have load. You're gonna be able to add or overlay documents. Today, I'm just gonna be showing the adding. We are also gonna show metadata, and that's going to include your native file link and your text links. We're still working on the images section, but the intent is to be able to do that simultaneously, and we have work ongoing with that. And so now what I'm gonna do is I am going to move to this, file, and I'm gonna select that DAT file here. So if I choose that DAT, it'll go ahead and lets me know. K. That's the DAT you're using. We also are solving the problem with the root and relative path, and there's some interesting things we're doing here. So when you, do this, you're gonna select the folder that contains all of your renderings, so your images, your natives, your text, and so on. So I'll go ahead and do that. You can see it's got my top level folder there. For the delimiter profile, it's just like I showed previously. It's got a language in there that has to do with your date formatting and such, so you're gonna wanna make sure that you're choosing the appropriate language. Then you have the option to index data. So when I move to this next page, it will automatically do that mapping for me, but I can also come in here and choose a map that I made previously. Now what I had done is I made a mapping that's just like what we saw previously, but I removed that file, size field just so that, I wouldn't get that error. Right? So if I choose that, you can see it's now mapping 21 instead of 22 fields as it had previously. But everything else here is the same. Now the other thing that I wanna show has to do with this rendering. You can see that it's rendering actually has the z drive in there. And one of the things that we heard from customers is that in the review manager previously, you had to spend an awful lot of time formatting how to get this right. There's a couple different ways we're exploring here, but the way that it it works at the moment is it actually will detect that and just clear it out. Right? So I don't need to actually remove that c drive. It just knows that that is a placeholder that's in there. That could be a c drive. It could be a dot, whatever the case may be. So when I hit submit, what's gonna happen is it's actually going to begin the upload for me. And so I'm not going to, you know, actually do a full upload here because that'll take some time, but But you can see that it's already started that progress. It's done 97 files, and it's gonna keep going here. So what I am going to do is actually, kinda move on to the native file load and talk about that next. But you can see that we've made a lot of really great progress here, and the team's done an excellent job bringing the experience in a much improved way to the, the web interface here, and we're really excited about that. Just real quick as a note, you will see that it keeps uploading for me. So if I were to move from here to project admin, I can see that it's still uploading. If I come back, it didn't pause for me. It's going to continue, and I can see that it's still working and uploading right now. I can hit that refresh and see it go. So that's actually a very important point is that you're not stuck just watching it. You can go and do other work in that project while that upload is ongoing. Alright. So going back to my slide deck, everything that we just showed was specifically around the review manager and loading DAT files. What I'm gonna do now is show you native file loading, which is our discovery manager. What we have delivered, actually just this last week here, is uploading using our new uploader, which you just saw. Right now, the version that's available for our customers is just for native files, so it doesn't show the, DAT file loading that I should showed just a moment ago. The current version supports one workflow in that it says I'm gonna take documents from upload to processing to review all the way through. Right? So there's no way to break up that step. What's currently in kind of our QA and testing department right now is being able to upload without processing. So essentially, I could ask my customer to upload the data and then after they've done that, I can now go and do the processing for them. Okay? And so that's gonna require the browsing of uploaded data to be able to look in your s three bucket and to be able to see it and be able to select what it is in all of your mappings. So that's what that other piece is. The part that's in active development right now is around air handling and data filtering. That part, I am gonna show you a mock up of what we're looking to do because it's not quite in a state yet that I can show you all, although we're making some great progress there. But what our intentions are is to bring a process that's just like this. So you can see that I have this processing, tab over here on the left hand side. And now what I've got is a review grid just like I have in review, and I have a search bar just like I have in review. The intention here is that, instead of having to use selective sets, instead of having to use import QC and these other, concepts that were a little bit more challenging for, users that are new to the industry, what we did was basically say, let's talk about having a unified experience. So rather than having to go do a completely different area of the tool, what we're working or sorry, learn something that's completely different from the review side of the tool, what we've done is said, what can we do to make that review experience almost the exact same thing in processing? So what you're looking at here concept wise is this idea of the document grid just like you have in review. You also have the concept of the search bar just like you have in review. And what our intentions are is you can do things like work folders and save searches to look through this data, before you move it to review. Right? So it's it's kind of like, an ECA type situation, but it's also for error handling. So all of the searching that you can do in review today, so things like date range searches and keyword searches, but also other kinds of metadata searches like maybe a file type or a file size you'll be able to do. And then once you've done your error handling, which you can see you could reprocess a file, if you need to change you know, reprocess with new settings, you need to be able to replace a file. Maybe you got a bad PST email container. You need to replace that to reprocess it. All of that's in there. And then eventually, there's this this idea of promotion. Right? That's what we call an export in the discovery manager today. And what this is is moving the data from processing to review. Okay? So this is in the in the concept stage. It's a very important part of the workflow, which is why we wanted to show it here, but what I'm gonna do now is actually show you what that looks like in review, or in the web rather. So, I can see that that upload is still going. It's about 55% of the way through, which is great, but I am actually gonna pause and cancel it just so it doesn't interfere with some of the other things that I'm doing here. But you can see, you know, that was all very seamless, not something I had to babysit or anything like that. Okay. So, you can see that I have that canceled status there. So now what I'm gonna do is go ahead and do a brand new upload. And when I do this, I'm gonna go ahead and call this import 2. I'm gonna call this, second, processing set, and I'm gonna indicate that these are native files this time. Okay? You can see, as I mentioned a moment ago, we have a little notice up here saying that uploading processing promotion is a single action. Our future updates will allow for more flexible workflows. So, again, we're, you know, working on that kind of in the QA testing phase right now, but not quite ready to show you today. What's gonna happen here is that I'm gonna browse just like I did for the DAT file, my local system. And what I'm gonna do is I've got this Globex folder here, and, I'm gonna go ahead and open that up. Now the first time you do this, it's going to, ask you, you know, do you give the browser access to use your system here? And the answer will be yes, obviously, if you wanna do this. But what it's gonna do is it recreates the folder structure for your users, in this interface here. And so I can browse through it just like I could, in the discovery manager previously or just like it was on my local drive or local network. This can be a network drive. It can be a local drive. As long as the current user can hit it with their current login, you'll be able to to browse it on here. So there's a couple of things that we did. One is that you have a whole section in processing to be able to see, your custodian list, to be able to append it. Right now, it's adding a custodian at a time, although we are working at a bulk upload. So I can either choose a custodian just like that or I can come in here and I can actually add a custodian on the fly. So I see that I don't have anything for Bridget Andrews. So I could come in here and say Bridget Andrews, and it will make that custodian for me just like that. For locations, it's the same thing. I can either choose an existing one or I can add 1 on the fly, and I can do the same thing for source. Now what's really interesting here is that we've made it so you can bulk do these actions here. So I can bulk say, let's just make all of these Chicago, and you can see it will do that for me. And I can do the same for sourced. So I can say, for example, this is the home PC of those users and process it just like that. So you do have the kind of custodian assignments on here. What we are working on is an auto detect, to basically match kind of like we've done with the field mappings to take things you've got and do that mapping automatically, but also to kind of put in a manifest type where you can say, here's the folder structure and here's how the mappings need to work. So both those things are, part of our intentions for this rollout. They're just not here for me to show you quite yet today. When you hit this next button, you will have the ability to email people and let them know that data has been uploaded, and has begun processing. We're intending to put this kind of throughout the app, in in many different areas. The other thing that's not showing here at the moment is it does not show you your processing settings. That is something that we're still working on, but the idea is that you'll be able to see before you hit submit exactly what your extraction settings are, your OCR settings, things of that nature. And when you do that, you'll be able to to basically confirm that that's the case. From a pre permissioning standpoint, it's very straightforward. There's gonna be 3 permissions. There's can I upload? Yes or no. Can I process data? Yes or no. And can I change project settings? Yes or no. And the reason that project setting, editing is its own permission is that there are some very large organizations we work with where they're working with a global team, and they may be very junior. And so we want the ability to say, if there's a problem, we maybe don't want people to make any changes that may not be correct, but have the ability to raise their hand and say, I don't think this is right. Okay? So the submission you can see is very similar. I'm actually not gonna do that just in the interest of time here, but we have this whole new section of the grid for processing, which includes that permission that I mentioned a moment ago. So we've got this main page here that's showing you your very similar to the the snapshot view that we have in the discovery manager in terms of frequent extensions, in terms of data processing that's happening. I can get to my jobs as well, and you can see that this is a job that I'd done previously. It did have an error, but it took, you you know, 2 minutes here to go ahead and do that processing. I've got some counts of the number of files, including the number of containers and such. And when I click in this, I can get the detail just for that processing job. The other thing that you'll notice here is that there is the ability to download an error report, so that's going to get you your errors into an Excel format. We're gonna continue to add, the data processing, reporting into the interface, but this was the most important one in terms of the transition from the the application to the web, and so that's what we kinda chose to do with 1st. But you can also see there's things that we're doing around the the the, logging of custodians, the logging of sources and such, and being able to track, how this data is moving in. So as I said, kind of the next steps are gonna be the settings and getting the, the ability to to process and upload to separate steps. But, you know, we're we're hard at work at that and be excited to get that in front of you soon. So that is what I had for the presentation today, so I think what we're gonna do now is move to a q and a section. So thank you very much for your time and attention, and looking forward to answering the questions you've asked either during the chat or right now. Okay. Alright. Wonderful. Thank you, Ryan, for this wonderful overview. Exciting functionality. I'm going to look in the, chat here and, answer some questions. I'm gonna start in the order that they came in, and I'm sure more will be coming in. Mark asked if we can have auto ignore in the load file fields that contain 0 data for any document. We will present a warning if the first 100 rows of the data in that load file, I have no data for the same field. It's not really an auto ignore, but it is alerting you to that effect. Then you can choose to ignore the warning or you can choose to unmap the field and any field that you don't map obviously will be ignored. We'll consider a future enhancement to ignore automatically without consent. But at the moment, we alert you to that fact and ask you to make a decision. That helps Mark. We will go next to Alan's question. Alan asked if there's any front end exception detection on the load files and what examples of areas we look for. Yes. I just mentioned and Ryan showed us there's a preview of the first 100 rows of the load file. At the same time we load the preview, we also perform common validation for some typical errors. Examples include mismatched data types. If you've mapped into a date field, but the source data is text and cannot be parsed into a date, we will present a warning. Or if you map the field that's a number field in the project, but you're trying to put text data in it in the first 100 rows, we will alert you. As I just mentioned, all blank entries will produce an alert, missing a required field like back doc will produce an alert. A couple of other scenarios too. More extensive error checking will happen, during the actual ingestion process, such as the, a big dog 2 big dogs, that are the same exist. That will happen during the ingestion process, Not right now. We're considering future enhancements for a test mode. But at the moment, when we encounter such an error, we will record it in a separate DAT file, an errors DAT file that you will be able to download and it will proceed to the next row. We will not stop your job. Moving down the next question here. Let's take a look here. I think Kelly mentioned a question around adding new custodians in the front end. Kelly, that's very much a feature. There are some little nips and tucks we're still putting on some projects, but that is very much a feature that we have and we expect to correct it. In fact, it might have already been corrected. We pushed a quick update on some functionality in the last day or 2. So very much a feature and we'll be, making some quick fixes there. Vanessa asked if we will, be able to apply a template to a new project. Vanessa, wondering if that means a mapping template or maybe a settings template. I'll ask her in the context of a mapping template. So, the ability to save field mapping templates is absolutely present, and there is the ability to copy these templates from one project to another. That's also a feature we expect in the next release, in the November release. I'm not sure if, Ryan, you wanted to add something around other template. If not, that's again and we can follow-up on some of these questions by email as, Jacqueline has mentioned. Yeah. I think she just came back because we're we're at the end of the time here, Jacqueline. Right? Right. Yeah. Well, I Not really, but we do gotta get we gotta end this time sometime. But any questions that were not addressed or that we want to address more in-depth, we'll make sure to send out an email on this within the next week just with all the follow ups and the answers to some of these questions. Thank you so much, everyone. I'm gonna send out a quick survey to anybody who's able to answer. We appreciate the time that you've given us today to, announce some of these releases, and we're excited to so for the more ideas and more things that we're coming out with. And I give so much props to these products, guys. They're so awesome in what they do, and they work so hard on this. And it's all because of the feedback and the the answers that you guys give us. So thank you so much, and we're excited that we're able to do this with you all. Awesome. Thank you so much. Bye, everyone.