[Sigia-l] The A>B, B>A problem

[Dwayne King]

I'm still going to fall back on asking the user how they want to view 
the data. Having it in a database is all the better, as long as the 
data is normalized it won't matter how you request it. If it's not, 
tell your DB admin that you want your money back, w/o being able to 
request the data by different metadata really defeats the purpose of 
having a database.

I know the original question was just to come up with a name for this, 
but I'm really having a hard time understanding why this is an issue. 
In the example Billie is pointing out, it is specifically stated that 
the user has different needs each time they visit, why force them into 
a model that doesn't fit their needs?

It's easy to do and make for a better user experience, so why not?

On Nov 5, 2004, at 2:04 PM, Billie Mandel wrote:

> **
> Unfortunately, the same user does not always need to slice it the same
> way, depending on the project s/he is working on, so ...

> ...I do have a dependency on a single tree structure - the structure 
> of how the content is currently
> organized on the system (and in the database). Until/unless I change 
> the
> back-end drastically, internal navigation and browsing is anchored to
> the way things are currently set up, which is (loosely speaking) by
> topic. I'm going to have to overlay any new navigation on top of this
> structure without adding unnecessary complexity. Any brilliant
> recommendations?