Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/13/2017 in all areas

  1. Tom, Data extraction is different from Processing in that Processing performs imaging on documents where Data Extraction does not. There is less overhead to run Data Extraction which will result in quicker job completion times. Use Data Extraction when document imaging is not required.
    1 point
  2. Tom, Data extraction is different from Processing in that Processing performs imaging on documents where Data Extraction does not. There is less overhead to run Data Extraction which will result in quicker job completion times. Use Data Extraction when document imaging is not required.
    1 point
  3. Tom, Data extraction is different from Processing in that Processing performs imaging on documents where Data Extraction does not. There is less overhead to run Data Extraction which will result in quicker job completion times. Use Data Extraction when document imaging is not required.
    1 point
  4. Tom, Data extraction is different from Processing in that Processing performs imaging on documents where Data Extraction does not. There is less overhead to run Data Extraction which will result in quicker job completion times. Use Data Extraction when document imaging is not required.
    1 point
  5. Tom, Data extraction is different from Processing in that Processing performs imaging on documents where Data Extraction does not. There is less overhead to run Data Extraction which will result in quicker job completion times. Use Data Extraction when document imaging is not required.
    1 point
  6. Tom, Data extraction is different from Processing in that Processing performs imaging on documents where Data Extraction does not. There is less overhead to run Data Extraction which will result in quicker job completion times. Use Data Extraction when document imaging is not required.
    1 point
  7. Tom, Data extraction is different from Processing in that Processing performs imaging on documents where Data Extraction does not. There is less overhead to run Data Extraction which will result in quicker job completion times. Use Data Extraction when document imaging is not required.
    1 point
  8. Tom, I understand Clearwell is an eDiscovery platform similar to eCapture. If you point eCapture to the exported native directory from a Clearwell export it will discover and extract document families in the native folder as it would any other source directory. If you need to import the corpus into eCapture as processed data, then an .LFP (image load file *if document images exist) and .DAT (data load file) file will be required to import the corpus using the eCapture Import Wizard. Family relationships can be determined from the LFP file if images exist for the corpus, or can be read from the BEGATTACH field in the data load file if no images are being imported with the corpus. The BEGATTACH value will be the Item's parent BEGDOC number. All items in a family will have the same BEGATTACH value in the data load file. eCapture supports Concordance, Summation, IPRO, Ringtail, CSV, and Custom Delimited export formats upon output from eCapture. I understand that Clearwell may rebuild mail stores upon export and may not point to loose MSG / EML natives on disk after after export, but rather, point to the PST. If this can be avoided in the Clearwell export it will make the import into eCapture much easier. You can find a document outlining some commonly encountered metadatafields at the link below: https://myipro.iprotech.com/ResourceCenter/#/eCapture/Supplemental%20Documents
    1 point
  9. Tom, I understand Clearwell is an eDiscovery platform similar to eCapture. If you point eCapture to the exported native directory from a Clearwell export it will discover and extract document families in the native folder as it would any other source directory. If you need to import the corpus into eCapture as processed data, then an .LFP (image load file *if document images exist) and .DAT (data load file) file will be required to import the corpus using the eCapture Import Wizard. Family relationships can be determined from the LFP file if images exist for the corpus, or can be read from the BEGATTACH field in the data load file if no images are being imported with the corpus. The BEGATTACH value will be the Item's parent BEGDOC number. All items in a family will have the same BEGATTACH value in the data load file. eCapture supports Concordance, Summation, IPRO, Ringtail, CSV, and Custom Delimited export formats upon output from eCapture. I understand that Clearwell may rebuild mail stores upon export and may not point to loose MSG / EML natives on disk after after export, but rather, point to the PST. If this can be avoided in the Clearwell export it will make the import into eCapture much easier. You can find a document outlining some commonly encountered metadatafields at the link below: https://myipro.iprotech.com/ResourceCenter/#/eCapture/Supplemental%20Documents
    1 point
  10. Tom, I understand Clearwell is an eDiscovery platform similar to eCapture. If you point eCapture to the exported native directory from a Clearwell export it will discover and extract document families in the native folder as it would any other source directory. If you need to import the corpus into eCapture as processed data, then an .LFP (image load file *if document images exist) and .DAT (data load file) file will be required to import the corpus using the eCapture Import Wizard. Family relationships can be determined from the LFP file if images exist for the corpus, or can be read from the BEGATTACH field in the data load file if no images are being imported with the corpus. The BEGATTACH value will be the Item's parent BEGDOC number. All items in a family will have the same BEGATTACH value in the data load file. eCapture supports Concordance, Summation, IPRO, Ringtail, CSV, and Custom Delimited export formats upon output from eCapture. I understand that Clearwell may rebuild mail stores upon export and may not point to loose MSG / EML natives on disk after after export, but rather, point to the PST. If this can be avoided in the Clearwell export it will make the import into eCapture much easier. You can find a document outlining some commonly encountered metadatafields at the link below: https://myipro.iprotech.com/ResourceCenter/#/eCapture/Supplemental%20Documents
    1 point
  11. Tom, I understand Clearwell is an eDiscovery platform similar to eCapture. If you point eCapture to the exported native directory from a Clearwell export it will discover and extract document families in the native folder as it would any other source directory. If you need to import the corpus into eCapture as processed data, then an .LFP (image load file *if document images exist) and .DAT (data load file) file will be required to import the corpus using the eCapture Import Wizard. Family relationships can be determined from the LFP file if images exist for the corpus, or can be read from the BEGATTACH field in the data load file if no images are being imported with the corpus. The BEGATTACH value will be the Item's parent BEGDOC number. All items in a family will have the same BEGATTACH value in the data load file. eCapture supports Concordance, Summation, IPRO, Ringtail, CSV, and Custom Delimited export formats upon output from eCapture. I understand that Clearwell may rebuild mail stores upon export and may not point to loose MSG / EML natives on disk after after export, but rather, point to the PST. If this can be avoided in the Clearwell export it will make the import into eCapture much easier. You can find a document outlining some commonly encountered metadatafields at the link below: https://myipro.iprotech.com/ResourceCenter/#/eCapture/Supplemental%20Documents
    1 point
  12. Tom, I understand Clearwell is an eDiscovery platform similar to eCapture. If you point eCapture to the exported native directory from a Clearwell export it will discover and extract document families in the native folder as it would any other source directory. If you need to import the corpus into eCapture as processed data, then an .LFP (image load file *if document images exist) and .DAT (data load file) file will be required to import the corpus using the eCapture Import Wizard. Family relationships can be determined from the LFP file if images exist for the corpus, or can be read from the BEGATTACH field in the data load file if no images are being imported with the corpus. The BEGATTACH value will be the Item's parent BEGDOC number. All items in a family will have the same BEGATTACH value in the data load file. eCapture supports Concordance, Summation, IPRO, Ringtail, CSV, and Custom Delimited export formats upon output from eCapture. I understand that Clearwell may rebuild mail stores upon export and may not point to loose MSG / EML natives on disk after after export, but rather, point to the PST. If this can be avoided in the Clearwell export it will make the import into eCapture much easier. You can find a document outlining some commonly encountered metadatafields at the link below: https://myipro.iprotech.com/ResourceCenter/#/eCapture/Supplemental%20Documents
    1 point
  13. Tom, I understand Clearwell is an eDiscovery platform similar to eCapture. If you point eCapture to the exported native directory from a Clearwell export it will discover and extract document families in the native folder as it would any other source directory. If you need to import the corpus into eCapture as processed data, then an .LFP (image load file *if document images exist) and .DAT (data load file) file will be required to import the corpus using the eCapture Import Wizard. Family relationships can be determined from the LFP file if images exist for the corpus, or can be read from the BEGATTACH field in the data load file if no images are being imported with the corpus. The BEGATTACH value will be the Item's parent BEGDOC number. All items in a family will have the same BEGATTACH value in the data load file. eCapture supports Concordance, Summation, IPRO, Ringtail, CSV, and Custom Delimited export formats upon output from eCapture. I understand that Clearwell may rebuild mail stores upon export and may not point to loose MSG / EML natives on disk after after export, but rather, point to the PST. If this can be avoided in the Clearwell export it will make the import into eCapture much easier. You can find a document outlining some commonly encountered metadatafields at the link below: https://myipro.iprotech.com/ResourceCenter/#/eCapture/Supplemental%20Documents
    1 point
  14. Tom, I understand Clearwell is an eDiscovery platform similar to eCapture. If you point eCapture to the exported native directory from a Clearwell export it will discover and extract document families in the native folder as it would any other source directory. If you need to import the corpus into eCapture as processed data, then an .LFP (image load file *if document images exist) and .DAT (data load file) file will be required to import the corpus using the eCapture Import Wizard. Family relationships can be determined from the LFP file if images exist for the corpus, or can be read from the BEGATTACH field in the data load file if no images are being imported with the corpus. The BEGATTACH value will be the Item's parent BEGDOC number. All items in a family will have the same BEGATTACH value in the data load file. eCapture supports Concordance, Summation, IPRO, Ringtail, CSV, and Custom Delimited export formats upon output from eCapture. I understand that Clearwell may rebuild mail stores upon export and may not point to loose MSG / EML natives on disk after after export, but rather, point to the PST. If this can be avoided in the Clearwell export it will make the import into eCapture much easier. You can find a document outlining some commonly encountered metadatafields at the link below: https://myipro.iprotech.com/ResourceCenter/#/eCapture/Supplemental%20Documents
    1 point
×
×
  • Create New...