Jump to content

jfishcasselsbrock.com

Members
  • Posts

    373
  • Joined

  • Days Won

    5

Everything posted by jfishcasselsbrock.com

  1. Yes, I agree. All Allegro reports and fields. Feature parity rules!
  2. Yes, I agree. All Allegro reports and fields. Feature parity rules!
  3. We had a similar issue with a user and the clear app cache option didn't work. We had to blow away the user's entire windows profile on the computer and n question.
  4. We had a similar issue with a user and the clear app cache option didn't work. We had to blow away the user's entire windows profile on the computer and n question.
  5. I've noticed when using this option that the search hits are being listed as zero in the highlights drop down menu in the viewer when using Boolean operators eg. ///TEXT contains (jack AND Jill). I assume this holds true for proximity searches as well.
  6. I've noticed when using this option that the search hits are being listed as zero in the highlights drop down menu in the viewer when using Boolean operators eg. ///TEXT contains (jack AND Jill). I assume this holds true for proximity searches as well.
  7. Also, proximity searches within persistent highlighting will not function as you would expect. Each word is highlighted in a document weather the proximity constraint is met or not. bob w/3 cat will result in all instances of each word being highlighted. The proximity operator is ignored and both terms are teated as separate persistent highlighting terms
  8. Also, proximity searches within persistent highlighting will not function as you would expect. Each word is highlighted in a document weather the proximity constraint is met or not. bob w/3 cat will result in all instances of each word being highlighted. The proximity operator is ignored and both terms are teated as separate persistent highlighting terms
  9. This also holds true for imagekeys that are not the first page of a document. Image keys are on a page level and they have to be unique across all images for all documents. For instance, if you have three docs with similar begdocs, abc0001 abc0001.001 abc0001.002 the third begdoc could have an image key in the first doc with this value. when numbering like this, you have to be aware of the image key values and make sure the page part of an image key is different in format than begdoc numbers. Use an _001 in such an instance. typically, if I'm doing an overlay of existing docs with existing images, I delete the existing images from the docs being overlayed in order to avoid the issue. if seen instances where both old and new image keys are kept in the document thereby causing a duplication of the images.
  10. This also holds true for imagekeys that are not the first page of a document. Image keys are on a page level and they have to be unique across all images for all documents. For instance, if you have three docs with similar begdocs, abc0001 abc0001.001 abc0001.002 the third begdoc could have an image key in the first doc with this value. when numbering like this, you have to be aware of the image key values and make sure the page part of an image key is different in format than begdoc numbers. Use an _001 in such an instance. typically, if I'm doing an overlay of existing docs with existing images, I delete the existing images from the docs being overlayed in order to avoid the issue. if seen instances where both old and new image keys are kept in the document thereby causing a duplication of the images.
  11. You can simply fill the endoc field with begdoc values. this applies weather you have images or not. The endoc field is not used to determine the values in the export set. Now with 2016.3.1, you can export a self referencing lfp image load file after filling in the endoc values and use iconvert+ to create a custom load file for begdoc, endoc,begattach, endattach values to overlay back into the case. this solves the issue if you don't want to use sql or have no access to sql. not all firm IT departments allow access to sql and the running of custom sql scripts.
  12. You can simply fill the endoc field with begdoc values. this applies weather you have images or not. The endoc field is not used to determine the values in the export set. Now with 2016.3.1, you can export a self referencing lfp image load file after filling in the endoc values and use iconvert+ to create a custom load file for begdoc, endoc,begattach, endattach values to overlay back into the case. this solves the issue if you don't want to use sql or have no access to sql. not all firm IT departments allow access to sql and the running of custom sql scripts.
  13. is this an issue with not having lotus notes installed correctly on the streaming workers thereby forcing Stellant to process the files? Or is there an option in the ecapture default settings for this case project to use stellant instead of lotus notes to perform extraction during data extract?
  14. is this an issue with not having lotus notes installed correctly on the streaming workers thereby forcing Stellant to process the files? Or is there an option in the ecapture default settings for this case project to use stellant instead of lotus notes to perform extraction during data extract?
  15. I've already submitted a feature request last year. I am a firm believer in feature parity.
  16. I've already submitted a feature request last year. I am a firm believer in feature parity.
  17. Hi there, any updated on the integration? What about web integration as well. I can't wait.
  18. Hi there, any updated on the integration? What about web integration as well. I can't wait.
  19. The other option is to go into the summation admin consile on the local copy and add the network case directory to the group the user is a member of. If there are no groups, use the unassigned user group as all users get mapped to this by default. this helps for networks cases on multiple server shares as well. We had 3 different instances of summation shared on 3 different servers as well as local cases that were mapped to network drives.
  20. The other option is to go into the summation admin consile on the local copy and add the network case directory to the group the user is a member of. If there are no groups, use the unassigned user group as all users get mapped to this by default. this helps for networks cases on multiple server shares as well. We had 3 different instances of summation shared on 3 different servers as well as local cases that were mapped to network drives.
  21. I use this option when I number a production on a doc level and I want to strip out the page number on the first page of every document. I use a text editor to modify the production load files to remove the page number from the first image key of each document and the first page number for begdocs in the Begdoc, endoc, begattach and endattach fields. This allows me to import the production history without the first page numbering in the production. there is a feature for this in Ecapture which I've put in a feature request for Eclipse SE, Eclipse Web and certain exports of ecapture. My feeling is, if it's already in another module of the ipro platform, let's reach feature parity in all modules.
  22. I use this option when I number a production on a doc level and I want to strip out the page number on the first page of every document. I use a text editor to modify the production load files to remove the page number from the first image key of each document and the first page number for begdocs in the Begdoc, endoc, begattach and endattach fields. This allows me to import the production history without the first page numbering in the production. there is a feature for this in Ecapture which I've put in a feature request for Eclipse SE, Eclipse Web and certain exports of ecapture. My feeling is, if it's already in another module of the ipro platform, let's reach feature parity in all modules.
  23. There is an option to import a production history. This comes in handy if you forget to check the update production history checkbox.
  24. There is an option to import a production history. This comes in handy if you forget to check the update production history checkbox.
  25. 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.
×
×
  • Create New...