search

sepinf-inc / IPED

IPED Digital Forensic Tool. It is an open source software that can be used to process and analyze digital evidence, often seized at crime scenes by law enforcement or in a corporate investigation by private examiners.
Other
924 stars 217 forks source link

Open multicase overwrites bookmark info if bookmark names coincide #1946

Open patrickdalla opened 10 months ago

patrickdalla commented 10 months ago

If two or more cases with bookmarks with same name, but some different properties like comment, color and shortcut are opened inside a multicase IPED opening, one of this bookmark is chosen from one the cases and the properties of the remaining bookmarks of the others cases are overwritten with the properties of this bookmark.

patrickdalla commented 10 months ago

Could we create a separate bookmark.iped file specific for the multicase? Any modification would apply to this separate bookmark.iped for the multicase, keeping the original single case bookmark.iped. Also, when opening a multicase, if bookmark conflicts are identified a merge warning could be shown.

On the other hand, maybe the user wants to replicate the bookmark changes to the single cases.

lfcnassif commented 10 months ago

Could we create a separate bookmark.iped file specific for the multicase? Any modification would apply to this separate bookmark.iped for the multicase, keeping the original single case bookmark.iped. Also, when opening a multicase, if bookmark conflicts are identified a merge warning could be shown.

On the other hand, maybe the user wants to replicate the bookmark changes to the single cases.

Hi @patrickdalla, I think popping up a warning if conflicts are identified is a good idea! In my opinion we could use a separate bookmarks.iped for the multicase just in this conflict situation (and also warn the user about that), and keep current behavior of replicating bookmark changes to single cases if there is no conflict.

patrickdalla commented 7 months ago

Hi @patrickdalla, I think popping up a warning if conflicts are identified is a good idea! In my opinion we could use a separate bookmarks.iped for the multicase just in this conflict situation (and also warn the user about that), and keep current behavior of replicating bookmark changes to single cases if there is no conflict.

How might be a subsequent opening of this multicase with these bookmarks saved on a distinct file?