Re: Versioning

["Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>]

And perhaps add a warning, something along the lines of
"You are about to create new version now. Do you want to proceed?"

So, full use case will be something like:

1. User opens an object for edit.
2. User tries to change an UMO link
3. UU prompts user to confirm new version creation
4. User confirms
5. UU creates new (and unpublished) version of an object
    and with requested UMO linking change done.
6. All further changes are accepted without creating new version
7. User publishes UMO.

This scenario presumes following things:
1. We only allow versioned edits of "head" version - that is the
    latest version of an UMO
2. User is trying to edit HEAD version (changes to the scenario
    for other cases are left as an exercise to the reader)
3. UMO cannot be "unpublished" once it is published.

These requirements weren't clearly defined previously
(nor, in fact, were they discussed before). Now is the time to
voice your concerns, and propose solutions. Otherwise I'll
put this into the spec.

Ilya A. Volynets-Evenbakh wrote:
> I'd say it should be other way around - changing object linking
> disables "minor edit" checkbox.
>
> sergey@total-knowledge.com wrote:
>   
>>> You seem to have missed "until UMO is published" part.
>>>
>>>     
>>>       
>> I guess so. Imho, from the UI point of view, an ability to link objects
>> should be hidden from users while they are in the "minor edit" mode.
>> This way they will know for sure when their changes are minor and when
>> they are versioned.
>>
>>   
>>     
>>> sergey@total-knowledge.com wrote:
>>>     
>>>       
>>>>> New versions aren't created even if object links
>>>>> are changed, until object is published. I know we didn't think through
>>>>> this
>>>>> part of editing scenario 100% yet.
>>>>>
>>>>>         
>>>>>           
>>>> Let's look at this more thoroughly.
>>>> If
>>>>
>>>>       
>>>>         
>>>>> New versions aren't created even if object links are changed
>>>>>
>>>>>         
>>>>>           
>>>> then it means that Students that currently studying a Course which
>>>> contains this UMO will see the Course that structured differently than
>>>> the
>>>> one they signed-up originally.
>>>> Are we OK with that?
>>>> Also it means that if Author adds completely new UMO from Repository to
>>>> his Course and doesn't check this action as "versioned", Students will
>>>> see
>>>> this new UMO during studying process. Probably for this scenario we have
>>>> to completely remove "minor change" option from the UI which leads to
>>>> some
>>>> additional functionality which will allow us to check whether it's new
>>>> UMO
>>>> for the Course or Author just manipulating with existing one and it's OK
>>>> for Students to see that.
>>>>
>>>>
>>>>
>>>>       
>>>>         
>>> --
>>> Ilya A. Volynets-Evenbakh
>>> Total Knowledge. CTO
>>> http://www.total-knowledge.com
>>>
>>>
>>>     
>>>       
>>   
>>     
>
>   

-- 
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com