Andreas Hartmann wrote:
> Andreas Hartmann wrote:
> 
> [...]
> 
>> But, if you make changes to the site structure, you have to
>> publish anything to get them live. There are several possibilities:
>>
>> - If you move a document in the site structure, this could be
>>   handled as an "editing" operation on the document. This is not
>>   totally correct, though, since the document is not changed.
>>   But it would allow to republish the document, and the site
>>   structure change would be live as well.
>>

>From a user point of view this might be more intuitive. He changed
something sees that the document is in authoring state, hence republish it.

>> - We could treat the site structure as a separate entity and apply
>>   a workflow to it. This means that moving a document would be
>>   an editing operation on the site structure, and you could
>>   publish the site structure again. You could imagine the site
>>   structure as a document which contains references to other
>>   documents. Side note: Maybe it would be even appropriate to
>>   implement it like this (this SimpleSiteManager is already
>>   implemented this way).
> 
That seems to be the more logical solution because you really change the
structure. Therefore I am +1 for this approach. (But, you have to call
attention to this change to the user especially if they are used to work
in 1.2)


> Another issue to think about:
> 
> How would you like to see this in the history?
> 
> a) - go to a document's workflow history
>    - check if the document was moved
> 
> b) - go to the site structure history
>    - check if it was changed
> 
That depends on how this is implemented: b if the site structure has its
own workflow.

Jann


> 
> Side note:
> In both cases, I'd like to have (auto-generated) annotations for
> changes. But I guess the workflow history is not the right place for
> this, we should rather have a general change log.
> 
> -- Andreas
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to