Jump to content

ŁukaszBachman

Administrators
  • Content Count

    320
  • Joined

  • Last visited

  • Days Won

    15

ŁukaszBachman last won the day on April 19 2019

ŁukaszBachman had the most liked content!

Community Reputation

16 Good

About ŁukaszBachman

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. Hi Neil! I noticed that the exact same thing was reported in. We already have an internal ticket about extending this functionality, it just needs a bit of time to get into a development queue. Thanks for pointing that out!
  2. @Jared, I think that this will get created if you create an Export Set while running your production. Intella will add a new column then which you can see in Items Table or use in further exports.
  3. Hi again, What you can try to do is to extend the default timeout of 3 minutes to a larger value by means of trial and error (4, 5, 6 mins...). To do this one has to modify "C:\Users\ACCOUNT_RUNNING_CONNECT\AppData\Roaming\Intella Connect\prefs\user.prefs" file by adding the following line: ReverseProxyTimeout=XXX where XXX is the new value in milliseconds (defaults to 180000). Intella Connect restart would be required. In general it should be ok to do this, but keep in mind that such timeouts are added for a reason and setting this value too large can result in performance degradation if not used wisely.
  4. Hello Stephan, This all sounds like good ideas to me, I'll include them in our roadmap for the future. We have some long-term plans for improvements in overall experience of using tasks in Connect, where I would like to address these as well. Leveraging Nodes for background tasks is also something that we are planning to do, but that one will be the hardest to do. Thank you for sharing your thoughts and feedback. P.S. Current version allows for stopping (removing) tasks which are running, but this depends on the type of the task (not all of them support this feature).
  5. Hi Margaret! The "Combine queries" option is enforced when there is more than 7 keywords in the list. We made this decision so that you don't evaluate all 98 keywords at once, which will likely not be of much use. That being said, please note that Intella Connect 2.3.1 will allow you to explore your keyword list and search for individual queries contained in it. Here is a relevant snippet from the Release Notes:
  6. I renamed the button to "Finish source management", to avoid confusion. This change will be present in upcoming 2.3.1 release.
  7. Hi Tom, Indeed we have plans for changing the flow, so that the case will be closed automatically. This requires larger architectural changes to the software, so it will likely take a couple of releases though. However, I do agree with your point about unfortunate naming of this button. We will consider this change in a shorter time span.
  8. Hi Chris, When seeing issues like this it's indeed best to submit a support ticket. Out engineers are working around the clock so often you get a response very vast. Now, what Adam has suggested (reindexing) is actually the best way to ensure that the case indices (databases) have been properly rebuilt. However, it's worth to check indexing logs, Exceptions Report and "Errors" branch in Features Facet beforehand. It will give you a better overview of the state of your case.
  9. Hi Adam! You should note that Primary Dates are calculated based on values stored in Intella columns. Different file formats are populating it differently: sometimes from RAW DATA, sometimes from item properties directly, etc. Therefore I wouldn't go this road because it would be hard to achieve 1:1 consistency. However, I think that the solution to your problem is rather simple. I would create a CSV export (or a load file) containing two columns: Item ID Primary Date Primary date will be populated using full date format (date + time + time zone). Then I'd use some text processing tool (Excel, advanced text editors, etc.) to remove date + time from the 2nd column. Now you'll need to create a new Custom Column of type "TEXT". The final step would be to add a new source as a Load File Overlay with following settings: As you can see the column which you modified (PRIMARY DATE) will be mapped to new custom column you created (TZ ONLY). Item ID is used to match items. After the overlay is imported, you will see: Is that what you need? I hope it helps a bit.
  10. Hello Adam, When using auto-tag feature you can provide the tag name in the following format: parent_tag/new_tag. That way a parent tag will be created first and you should be able to maintain your structure. Is that what you were seeking? As for the other part of your question - what changes/features in the UI you would like to see to influence the scope of this search/tagging operation? Filtering by type or something else?
  11. Vound is pleased to announce the official release of Intella and Intella Connect 2.3. Intella and Intella Connect 2.3 are available from the Downloads section in the Vound Support Portal, after logging in with your email address and password. Users with a 2.2.x license need to use the Dongle Manager to update their dongle to the 2.3 license. Please read the Release Notes before installing or upgrading, to ensure you do not affect any active cases. Highlights Introducing a new product: W4, for the rapid analysis of user activity. Added support for load file overlays. Items can now be exported to an item report. Added support for MS Exchange EDB 2013/2016 files. Added support for Outlook for Mac olk15* files. Added a user interface for managing memory and crawling settings. Note: W4 installers will be published in next couple of days.
  12. Intella Connect 2.3 version has just been officially released.
  13. Hi Sam, Selective indexing of pages inside documents is not something we are currently supporting. I would suggest to open that document using native application and print desired pages to individual PDFs. Then you could use Intella to index those loose files and perform your investigation on individual pages.
  14. Hi QasimProtiviti, In general this shouldn't be the case. What I can suggest to you is do the following: Clear searches Add a regular search query that will produce 1500 items (like before) Add a regular search query for 100 items tagged as "Irrelevant" Now look at the clustermap - if it contains only two clusters, then that is fine. If it contains three, then it means some of items which you tagged as "Irrelevant" are not in the scope of your initial search for 1500 items. Example: I searched for term "look" and marked 10 of those items as "Irrelevant". When I do those three steps listed above I see: Now, I marked 2 more items as Irrelevant, but I made sure that they don't contain term "look". This is what I see after I repeat my exercise: This pictures clearly says that I have 12 irrelevant items, but only 10 of them are also responsive to "look". So if I now search for "look" and exclude items tagged as "Irrelevant", I see: This might look misleading at first, because for an untrained eye "260 - 12" should equal 248, but it's should now be clear that those two extra items were never a part of the "look" cluster, therefore they shouldn't be accounted for. Hope that I was on the right track here and it helps you down the road.
×
×
  • Create New...