San Diego User Group
San Diego User Group Relativity Production Workflows
© kCura LLC. All rights reserved.
Introductions Thanks to our host. kCura Team • Michael Harris –Sales Support • Kelly Wehbi – Product Manager • Greg Houston – Solutions Team
© kCura LLC. All rights reserved.
What is the Relativity User Panel? The user panel is a group of customers that participate in kCura’s user experience research (user testing, user interviews, surveys, etc…). The panel acts as a launch point for design- and productrelated discussions between users, the kCura UX / product team, and each other.
© kCura LLC. All rights reserved.
Our Goals •
We want to build a strong relationship with our users
•
It’s important for us to get feedback throughout the lifecycle of a project (from conception to post-release), so that we fully understand how our users are impacted
•
We want to show our users that their experience using Relativity is important and valuable
© kCura LLC. All rights reserved.
Benefits of Being a User Panel Member • • • •
Receive RCE credits Sneak peek of what we are working on for the current release Direct input on how we impact workflows and tasks Your voice will be heard
© kCura LLC. All rights reserved.
What’s your Production horror story?
© kCura LLC. All rights reserved.
Steps to Production 1. Searches a. Items to produce based on production format I. Native II. Images III. Images and Natives b. Items not to produce for conflict search
© kCura LLC. All rights reserved.
Steps to Production 2.
Production Template Format a. Items to produce based on production format I. Native II. Images III. Images and Natives b. Items not to produce for conflict search
© kCura LLC. All rights reserved.
Production Set Quality Control Before Production • What are the production set parameters? – Are there multiple responsiveness or privilege fields? – Are there multiple markup sets? •
Include relevant fields in the production set search results
•
Consider setting up a consistent production set QC system – Use production set tag – Update production set QC searches for new tag or use temporary tag
•
How are inconsistencies treated?
•
Is there a specific production order?
© kCura LLC. All rights reserved.
Production Set QC Searches In Production Set and: • Not responsive • Privileged • Redacted, not tagged redact (make sure to search on proper markup set) • Tagged redact, not redacted (make sure to search on proper markup set) • Previously produced • Privilege screen terms, not marked privileged • Imaged and to be produced natively • To be imaged, not imaged • Corrupt/unprocessable in production set • Inconsistent families (related to production, not in production) • Duplicate/email thread/near duplicate of privilege document • Not reviewed/question/not sure for responsiveness or privilege • Outside of relevant date range
© kCura LLC. All rights reserved.
Final Production Volume Quality Control After Production • Review load files – Correct number of rows in DAT file – Correct fields in DAT file – Native and text paths are correct – Correct number of documents in image files (count ,Y, or ,D) – Number of images in image load files – Number of natively produced documents
© kCura LLC. All rights reserved.
•
Review images – Proper first bates number – Proper confidentiality endorsement – Redactions burned – Any other special endorsements – Correct number of images from image load files – Image type (B&W, color) are proper
Final Production Volume Quality Control •
Review text – Text of first document matches image of first document – OCR text for redacted documents – Empty text files only for documents with no text in database
© kCura LLC. All rights reserved.
•
Review native files – Correct number of native files – Proper extensions/document types produced natively
Common Errors in Productions What to watch out for? • Production format – Format conforms with production specifications/ESI order – Proper image type (PDF/B&W/color) produced •
Text – OCR text produced – A text file is produced for every document – ILB (intentionally left blank) text documents should be blank
© kCura LLC. All rights reserved.
•
Changes to production set after release – Additions to production set – Changes to tagging – Slip-sheeting and ILB slip-sheets
•
Treatment of exception files – Produced natively with a slip-sheet – Slip-sheeted only – Exception log
•
Production order
© kCura LLC. All rights reserved.
Questions?
© kCura LLC. All rights reserved.
© kCura LLC. All rights reserved.
Introductions Thanks to our host. kCura Team • Michael Harris –Sales Support • Kelly Wehbi – Product Manager • Greg Houston – Solutions Team
© kCura LLC. All rights reserved.
What is the Relativity User Panel? The user panel is a group of customers that participate in kCura’s user experience research (user testing, user interviews, surveys, etc…). The panel acts as a launch point for design- and productrelated discussions between users, the kCura UX / product team, and each other.
© kCura LLC. All rights reserved.
Our Goals •
We want to build a strong relationship with our users
•
It’s important for us to get feedback throughout the lifecycle of a project (from conception to post-release), so that we fully understand how our users are impacted
•
We want to show our users that their experience using Relativity is important and valuable
© kCura LLC. All rights reserved.
Benefits of Being a User Panel Member • • • •
Receive RCE credits Sneak peek of what we are working on for the current release Direct input on how we impact workflows and tasks Your voice will be heard
© kCura LLC. All rights reserved.
What’s your Production horror story?
© kCura LLC. All rights reserved.
Steps to Production 1. Searches a. Items to produce based on production format I. Native II. Images III. Images and Natives b. Items not to produce for conflict search
© kCura LLC. All rights reserved.
Steps to Production 2.
Production Template Format a. Items to produce based on production format I. Native II. Images III. Images and Natives b. Items not to produce for conflict search
© kCura LLC. All rights reserved.
Production Set Quality Control Before Production • What are the production set parameters? – Are there multiple responsiveness or privilege fields? – Are there multiple markup sets? •
Include relevant fields in the production set search results
•
Consider setting up a consistent production set QC system – Use production set tag – Update production set QC searches for new tag or use temporary tag
•
How are inconsistencies treated?
•
Is there a specific production order?
© kCura LLC. All rights reserved.
Production Set QC Searches In Production Set and: • Not responsive • Privileged • Redacted, not tagged redact (make sure to search on proper markup set) • Tagged redact, not redacted (make sure to search on proper markup set) • Previously produced • Privilege screen terms, not marked privileged • Imaged and to be produced natively • To be imaged, not imaged • Corrupt/unprocessable in production set • Inconsistent families (related to production, not in production) • Duplicate/email thread/near duplicate of privilege document • Not reviewed/question/not sure for responsiveness or privilege • Outside of relevant date range
© kCura LLC. All rights reserved.
Final Production Volume Quality Control After Production • Review load files – Correct number of rows in DAT file – Correct fields in DAT file – Native and text paths are correct – Correct number of documents in image files (count ,Y, or ,D) – Number of images in image load files – Number of natively produced documents
© kCura LLC. All rights reserved.
•
Review images – Proper first bates number – Proper confidentiality endorsement – Redactions burned – Any other special endorsements – Correct number of images from image load files – Image type (B&W, color) are proper
Final Production Volume Quality Control •
Review text – Text of first document matches image of first document – OCR text for redacted documents – Empty text files only for documents with no text in database
© kCura LLC. All rights reserved.
•
Review native files – Correct number of native files – Proper extensions/document types produced natively
Common Errors in Productions What to watch out for? • Production format – Format conforms with production specifications/ESI order – Proper image type (PDF/B&W/color) produced •
Text – OCR text produced – A text file is produced for every document – ILB (intentionally left blank) text documents should be blank
© kCura LLC. All rights reserved.
•
Changes to production set after release – Additions to production set – Changes to tagging – Slip-sheeting and ILB slip-sheets
•
Treatment of exception files – Produced natively with a slip-sheet – Slip-sheeted only – Exception log
•
Production order
© kCura LLC. All rights reserved.
Questions?
© kCura LLC. All rights reserved.
