nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best Practices, Heirarchy Examples

CalvinFold

This is not necessary just from Interwoven, I'd be interested in peer-level examples:

I'd like to see, aside from the recent General Mills examples, what other companies use for their folder heirarchy for assets, especially Consumer Goods companies with a focus on packaging graphics assets.

Seems a shame everyone is "winging it" on their own, and we find our selves changing the structure at least once a year because despite focus groups, testing, beta'ing, Survey Monkey, and just about everything short of reading the Tarot we never arrive at something even 50% of users are happy with.

(Last year, we did minor revisions to the structure no less than 4 times, and we're currently undergoing our latest major full-scale, ground-up re-org of the assets and metadata.)

So if Interwoven has a library of examples, that would be great. Or if fellow users want to volunteer what they do, that is equally helpful.

Find more posts tagged with

Comments

msrinivas

Kevin,

Having worked with Gen Mills and a few other CPG customers (including you Smiley Wink

) all I can say is it is very unique.

Interwoven should be able to help you out if you can get in touch with the AE for your account or Tracy or Mike.

PM me if you need help with that.

CalvinFold

Srinivas! Small world!

Well we ask through our official contacts but the "we're unique" answers only go so far. We're at a loss for even basic ideas and methodology. The General Mills demo gave us alot of ideas though...we were hoping for "more input."

Ideally we should contract a specialist in information systems, but not in this economy.

So they've got me signed into these forums to go on fishing exeditions in the peer community hoping for other sources of info. They know I'm a forum-fiend. Smiley Wink

msrinivas

The forums are typically frequented by the developer types rather than the business folks whom I think will be able to help you more. You will be able to get to the business folks mostly through account execs and PMs.

HTH

lyman

Fundamentally you need to decide how the data will be accessed. For some customers the primary interface is searching and in that case fewer containers make sense. For other customers,, the primary interface is browsing and then it would make sense to organize by how the data will be used.

The general criterion I would use is to see if you can set things up so that the individual users by clicking into a subfolder can quickly get to a preponderance of the files they are likely to be interested in and pare down those they are not interested in.

Not knowing your business process, it is impossible to tell if that top-level division is most logically by season, model, phase in workflow (i.e., pending approval, deployed,...) etc.

The other thing to remember about file structure is that MediaBin uses them to determine security. The way MediaBin functions it is far more efficient if the security on folders if more or less homogeneous.

Cheers,

Lyman Hurd