Page 3 of 6
Re: Reorganizing History Data
Posted: 29 Mar 2011 08:10
by admin
RalphM wrote:admin wrote:OK. So if it is not stored locally, then I should probably disallow and editing/repositioning of merged items simply because it would be lost on next start. Right?
Unless you enable the user at least to see that some items in his merged catalog are "dirty" and provide a way to reload the current server version?!
Yes, maybe in a 2nd step. I will keep it simple for now.
Re: Reorganizing History Data
Posted: 31 Mar 2011 14:41
by admin
RalphM wrote:Great, looking forward to see this evolve.
Well, any word on the new
Catalog Merging feature?
Re: Reorganizing History Data
Posted: 31 Mar 2011 16:44
by RalphM
admin wrote:Well, any word on the new Catalog Merging feature?
Didn't get to test it yet, but it sounds promising. Will check soon and keep you posted.
Re: Reorganizing History Data
Posted: 31 Mar 2011 18:16
by serendipity
admin wrote:RalphM wrote:Great, looking forward to see this evolve.
Well, any word on the new
Catalog Merging feature?
Awesome! Time-saver.
Re: Reorganizing History Data
Posted: 31 Mar 2011 19:37
by admin
serendipity wrote:admin wrote:RalphM wrote:Great, looking forward to see this evolve.
Well, any word on the new
Catalog Merging feature?
Awesome! Time-saver.
Yep, same here. Killer feature.
BTW, the same (merging) is possible for
tag.dat, of course. Which is pretty equivalent to MUT (multi user tagging) -- especially when I add auto-update (= auto-remerge). I will add that when I find the time...
Re: Reorganizing History Data
Posted: 31 Mar 2011 19:49
by admin
admin wrote:Yep, same here. Killer feature.

BTW, marketingwise I find "Catalog Merging" a bit pale. Any buzzy suggestions anybody...?
Re: Reorganizing History Data
Posted: 31 Mar 2011 21:23
by Stefan
admin wrote:admin wrote:Yep, same here. Killer feature.

BTW, marketingwise I find "Catalog Merging" a bit pale. Any buzzy suggestions anybody...?

QuickDic says
Commingle Catalogs
Coalescing Catalogs
Compounding Catalogs
Mashup Catalogs
Re: Reorganizing History Data
Posted: 31 Mar 2011 22:11
by RalphM
admin wrote:BTW, marketingwise I find "Catalog Merging" a bit pale. Any buzzy suggestions anybody...?
You didn't like the first name I gave it then? "Cascading Catalogs"
Re: Reorganizing History Data
Posted: 31 Mar 2011 22:56
by j_c_hallgren
RalphM wrote:admin wrote:BTW, marketingwise I find "Catalog Merging" a bit pale. Any buzzy suggestions anybody...?
You didn't like the first name I gave it then? "Cascading Catalogs"
I was thinking of Consolidated -or- Combined as suggested words.
Re: Reorganizing History Data
Posted: 01 Apr 2011 08:01
by admin
RalphM wrote:admin wrote:BTW, marketingwise I find "Catalog Merging" a bit pale. Any buzzy suggestions anybody...?
You didn't like the first name I gave it then? "Cascading Catalogs"
Certainly sounds good, and is better than "Catalog Merging".
Re: Reorganizing History Data
Posted: 01 Apr 2011 08:02
by admin
Stefan wrote:admin wrote:admin wrote:Yep, same here. Killer feature.

BTW, marketingwise I find "Catalog Merging" a bit pale. Any buzzy suggestions anybody...?

QuickDic says
Commingle Catalogs
Coalescing Catalogs
Compounding Catalogs
Mashup Catalogs
Similar but not as good as "Cascading Catalogs" IMO.
Re: Reorganizing History Data
Posted: 01 Apr 2011 11:13
by Stefan
Oh mannooo, i was about to write "Cascading Catalogs" too
But then i was thinking about "Cascading context menu items"
and think people get an wrong expression from it.
Code: Select all
Catalog One
| Items
|_Catalog Two
| Items
|_Catalog Three
| Items
instead of
Code: Select all
Catalog One
Items
Catalog Two
Items
Catalog Three
Items
For me sounds "Merging" (marketing aside) the right term.
But "to merge" is meant as merge "forever"? Like merge *.reg file?
What would be an term for merge only for an time?
No idea, just brainstorming:
side by side catalogs
Compounding Catalogs
composing
catalog stacking
supercharge
catalog collection
multi-level catalogs
Re: Reorganizing History Data
Posted: 01 Apr 2011 12:30
by admin
Right, cascading is not a correct term, but it sounds good. Which is more important in marketing.
Stefan wrote:What would be an term for merge only for an time?
No idea, just brainstorming:
side by side catalogs
Compounding Catalogs
composing
catalog stacking
supercharge
catalog collection
multi-level catalogs
Embed? Embedded Catalogs?
Re: Reorganizing History Data
Posted: 01 Apr 2011 17:10
by admin
While I now tend to think that "Embed" should replace "Merge" (which for me connotes something irreversible) in the interface, I have the following idea for marketing purposes: decentralized functionality.
Re: Reorganizing History Data
Posted: 01 Apr 2011 17:19
by j_c_hallgren
admin wrote:While I now tend to think that "Embed" should replace "Merge" (which for me connotes something irreversible) in the interface, I have the following idea for marketing purposes: decentralized functionality.
Sorry, but to me that term (decentralized functionality) means absolutely nothing in this context...I still think that combined or consolidated are better terms for this since they don't imply being irreversible in all cases.