RE: caching, publishing, and cloning

1 > 2

Yes, we try to be intelligently accommodating to our users
needs 

I'm sensing from people that there are pros and cons of each
and users
would eventually want auto-shelving anyway.

Maybe the notion of multiple shelves is really what I'm
thinking of, but
I'm not prepared to go there right now.


-----Original Message-----
From: slanninglocalhost.localdomain
[mailto:slanninglocalhost.localdomain] On Behalf Of Scott
Lanning
Sent: Wednesday, October 03, 2007 5:46 AM
To: userslists.bricolage.cc
Subject: RE: caching, publishing, and cloning

On Tue, 2 Oct 2007, Beaudet, David P. wrote:
> Has anyone ever suggested that stories NOT leave
workflow when they're
> published and instead just stay at the publish desk
until they're
> manually moved to shelf?
>
> Does this seem like a crazy idea?

You presumably have some underlying reason for wanting
this?
For example:
1) users who don't preview find mistakes after publishing
and need to re-checkout and are complaining, and you care;
2) there's a story published by a human every 20 minutes,
and that human is annoyed at having to re-checkout the
story,
and you care.

The problem here is not the system,
it's that you care that users are complaining.
No, wait a minute....

But I think if you don't shelve stories after publish,
users will be annoyed at having to manually shelve the
stories.