Submitted by Armando on 2010/02/23 14:22
Hi Pierre,
 
I'll clarify my question by explaining what I want (or what I'm hesitating...) to do.
 
As I'm bringing more precision to my organizational system in IQ (actually trying to bring to IQ more of what I developed a my "file naming scheme" in the past few years), some questions arise.
 
A- As we know, there are some advantages in separating all info/data into many different fields (e.g. : usually easier to filter and find items, make changes in many items at once, etc.), but this can also become messy and hard to manage (e.g. : a- too many columns in a grid to display only little info, b- user has too many fields to fill in the properties pane and  the input flow gets fragmented, etc. )
 
B- There are some advantages in integrating all data in less fields (e.g. : the WikiTag field, where you can have several tags in one field, allowing one to avoid the "1 field = 1 tag" mess...), as it can allow more clarity, allow the display of more info in less columns, etc.
 
 
However, if I'm going to choose B.... Will performance be affected when filtering (whether through grid sources, or just the filter text box) ?
 
i.e. : if I choose   WikiTag like "*xle-*"   as the source for one of my grids, will it be less performant than having only an xLE- field I'd use as the source ?
 
 
=========
 
 
Choosing B also means that 2 very important features need to be implemented sooner then later :
 
- "Search and replace" in grids :  otherwise, it becomes very hard to suppress a "tag" (or any piece of info from a field) without erasing the other pieces of info. (This is part of my high priority list : Armando's list. )
 
-  "Multiple-selection combo boxes" (part of Tom's high priority feature list : Tom's request - improve wikitag selection) : When are we going to get these in the grids so that it's easier to implement the "multiple tags in one field" principle ? I know Tom, Jan and others too are waiting for that so that they can enter tags/WikiTags, etc. more easily in grids or in other text-boxes. it's already been implemented in a few places (like in the add item window : the "WikiTags" and "Other field" text boxes).
 
 
I'd appreciate feedback on this one too as I'm kind of waiting to implement different data management strategies based on your plans... Thanks.

Comments

[quote=Armando]
However, if I'm going to choose B.... Will performance be affected when filtering (whether through grid sources, or just the filter text box) ?
 
i.e. : if I choose   WikiTag like "*xle-*"   as the source for one of my grids, will it be less performant than having only an xLE- field I'd use as the source ?
[/quote]
JET is extremely efficient at searching for text. Just see how responsive live-search is. it does complex *xyz* searches combined with and/or.
 
As for the 2 improvements needed, point well taken. Will do.
 

Armando

2010/03/09 14:13

In reply to by Pierre_Admin

[quote=Pierre_Admin]
[quote=Armando]
However, if I'm going to choose B.... Will performance be affected when filtering (whether through grid sources, or just the filter text box) ?
 
i.e. : if I choose   WikiTag like "*xle-*"   as the source for one of my grids, will it be less performant than having only an xLE- field I'd use as the source ?
[/quote]
JET is extremely efficient at searching for text. Just see how responsive live-search is. it does complex *xyz* searches combined with and/or.
 
As for the 2 improvements needed, point well taken. Will do.
 
[/quote]
 
Thanks for the answer.