Jump to content

jfishcasselsbrock.com

Members
  • Posts

    373
  • Joined

  • Days Won

    5

Everything posted by jfishcasselsbrock.com

  1. I've noticed that the transcript import function will look for a date in the text of the first page of a transcript. if the text has a date like this, "the 27th day of October 2001", you can change the text to " October 27, 2001" and it will read it properly. You have to make sure the date does not break across multiple lines.
  2. Is there any possibility in using the backup/restore option instead of deleting the newly created case directory? if a user doesn't have the rights to delete the case directory on a network, would this be a possible workaround.
  3. Is there any possibility in using the backup/restore option instead of deleting the newly created case directory? if a user doesn't have the rights to delete the case directory on a network, would this be a possible workaround.
  4. unfortunately, batch printing natives is not an option in most litigation software products. This is due to the fact that there is no way to control page sizing and orientation (landscaping vs portrait) during a batch print operation not to mention the possibility of image cutoff for documents, like excel files which could be several football fields wide. Also, there is no ability to perform redactions, annotations and bates stamping on natives. you have to image the natives in order to perform batch printing as well as create redactions, annotations and bates stamping. If you have placeholders for these natives, the best option is to delete these placeholder images in Admin from a saved search and then perform batch tiff processing using the saved search. The other option is to send the natives to a service provider to batch tiff and qc. They will provide you with the images and a lfp load file to import into SE. You'll still need to delete the placeholder images in this scenario unless you give them the exact image key numbering of the placeholders (eg. Abc123.0001). If you do, you can perform an overlay import choosing the option to delete existing images. you can then batch print the resulting images for these natives.
  5. unfortunately, batch printing natives is not an option in most litigation software products. This is due to the fact that there is no way to control page sizing and orientation (landscaping vs portrait) during a batch print operation not to mention the possibility of image cutoff for documents, like excel files which could be several football fields wide. Also, there is no ability to perform redactions, annotations and bates stamping on natives. you have to image the natives in order to perform batch printing as well as create redactions, annotations and bates stamping. If you have placeholders for these natives, the best option is to delete these placeholder images in Admin from a saved search and then perform batch tiff processing using the saved search. The other option is to send the natives to a service provider to batch tiff and qc. They will provide you with the images and a lfp load file to import into SE. You'll still need to delete the placeholder images in this scenario unless you give them the exact image key numbering of the placeholders (eg. Abc123.0001). If you do, you can perform an overlay import choosing the option to delete existing images. you can then batch print the resulting images for these natives.
  6. Does SE have the same ability as Web to assign a field as a hyperlink? This would allow the linking of an external document from a document in the main database.
  7. Does SE have the same ability as Web to assign a field as a hyperlink? This would allow the linking of an external document from a document in the main database.
  8. Hey Roman, Good tip. of course, if you're on a company network/domain and don't have admin rights on the domain, group policy object may prevent this. The alternative is to use unc paths (\\server\share) by hitting the browse button and pasting the unc path in. i prefer this method when SE is installed on a network as it allows everyone else to see any ingested natives without the need to copy the natives to the case directory no matter what their personal mapped paths are. Not all user's will have the same mapped drives.
  9. Hey Roman, Good tip. of course, if you're on a company network/domain and don't have admin rights on the domain, group policy object may prevent this. The alternative is to use unc paths (\\server\share) by hitting the browse button and pasting the unc path in. i prefer this method when SE is installed on a network as it allows everyone else to see any ingested natives without the need to copy the natives to the case directory no matter what their personal mapped paths are. Not all user's will have the same mapped drives.
  10. You can export load files only in 2016.3.1 and up by choosing the self reference option for images and/or natives You can then pick the tag groups you want to export in a day file. I find, however, you have to do some cleanup on the tag structure in 2016.3.1 but not a big deal.
  11. You can export load files only in 2016.3.1 and up by choosing the self reference option for images and/or natives You can then pick the tag groups you want to export in a day file. I find, however, you have to do some cleanup on the tag structure in 2016.3.1 but not a big deal.
  12. I've seen this issue when there is not a comma in the path to the case data directory or in the case name. This seems to effect searches that imploy multiple Boolean operators or proximity operators. The other issue is when a search hits on an indexed metadata field. You have no way of telling where the hit is located. Can we ask for a feature request that keyword searches or keyword management lists will report on where the hit was found ( text or field like Allegro does. I find Eclipse over collects and identifies hits in metadata where proximity terms are found in different fields.
  13. I've seen this issue when there is not a comma in the path to the case data directory or in the case name. This seems to effect searches that imploy multiple Boolean operators or proximity operators. The other issue is when a search hits on an indexed metadata field. You have no way of telling where the hit is located. Can we ask for a feature request that keyword searches or keyword management lists will report on where the hit was found ( text or field like Allegro does. I find Eclipse over collects and identifies hits in metadata where proximity terms are found in different fields.
  14. hi, ehen will eclipse web be able to act on the rotation flag in an LFP file for proper image rotation?
  15. hi, ehen will eclipse web be able to act on the rotation flag in an LFP file for proper image rotation?
  16. I guess a possible workaround would be to export out an LLP file that references the existing db and then filter on the Annotation tokens. This would give the image key (begdoc) which could be crafted into a tag load file fairly easily using notepad and regular expressions.
  17. I guess a possible workaround would be to export out an LLP file that references the existing db and then filter on the Annotation tokens. This would give the image key (begdoc) which could be crafted into a tag load file fairly easily using notepad and regular expressions.
  18. you can't create child numbering in web (eg, Prod001, Prod001A, Prod002, Prod003, Prod003A, Prod003B, etc)
  19. you can't create child numbering in web (eg, Prod001, Prod001A, Prod002, Prod003, Prod003A, Prod003B, etc)
  20. Hi Mike, this must have recently changed. In 2015.1.X, this wasn't the case. i guess I better review the upgrade guides to find this one. thanks, jeff
  21. Hi Mike, this must have recently changed. In 2015.1.X, this wasn't the case. i guess I better review the upgrade guides to find this one. thanks, jeff
  22. Hi Mike, this must have recently changed. In 2015.1.X, this wasn't the case. i guess I better review the upgrade guides to find this one. thanks, jeff
  23. You may have to bring up the twain interface for the scanner in devices| scanner properties and change from ADF to Flatbed
  24. You may have to bring up the twain interface for the scanner in devices| scanner properties and change from ADF to Flatbed
  25. You may have to bring up the twain interface for the scanner in devices| scanner properties and change from ADF to Flatbed
×
×
  • Create New...