Re: Database schema

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

sergey@total-knowledge.com wrote:
> 3. It should be a time interval allowed for Authors to finish their
> editings, after this time UMO should be unlocked automaticaly. It will
> help with situations when Authors leave their work without publishing, if
> they got disconnected before publishing, etc.
>   
First of all, let's not mix up "publishing" and "saving".
Second, time interval is fine, but on the other hand, what does one
do if it just takes too much time to do the edit, and yet he doesn't
want to save it (think: large textual change, that is still considered
minor edit on a published object)


>> There are some complications with this approach.
>> 1. We can't just lock an object whenever an Author of this object or
>> Referer view it in their browsers.
Correct.
>>  We need to know for sure that they are
>> going to edit it, so they will have to take some action to get into
>> "editing mode" first(like clicking on the "Edit Mode' button on the page),
>> then we can lock the object for other authors(not students).
Works for me.
>>  During the
>> editing process other than current Authors will see a message "Object is
>> currently locked, come back later".
Works for me.
>>  Once cuurent Author publishes it, it's
>> unlocked and available for other co-Authors.
Works for me.
>>  The one of them who gets into
>> "editing mode" first has the priority to edit an UMO.
>>     
What is that supposed to mean?
>> 2. Students will have to see changes to the UMO on the fly if an Author
>> makes minor chnges to this version of the object at that moment.
>>     
Correct. That's entire intention behind minor edits.

BTW, one thing that isn't specified anywhere right now, but which we should
probably add, is that changing object relationships cannot be a minor edit.

>>> I guess, the very least we can do is to add published field (DATETIME, I
>>> guess) to every UMO. If this field is NULL, then the object exists but
>>> can
>>> be seen by the UMO author only. In this case, any changes made in
>>> already
>>> published object are seen instantly (that is a disadvantage).
>>>
>>> 2007/1/18, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>>>       
>>>> I've checked the discussion threads including topic "Versioning", but I
>>>> can't seem to find it anywhere except " Translation vs. Versioning"
>>>> topic
>>>> in specs.
>>>>
>>>> http://www.total-knowledge.com/wiki/index.php/UU#Translation_vs._Versioning
>>>>
>>>>         
>>>>> There is another comment somewhere, which describes
>>>>> "published/unpublished"
>>>>> bit for a version, which suits better our current model.
>>>>>
>>>>> sergey@total-knowledge.com wrote:
>>>>>           
>>>>>> I see. But I still need to know if we are going to save those copies
>>>>>>             
>>>> in
>>>>         
>>>>>> DB
>>>>>> or not. What if several users edit a same object at the same time?
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> We have versioning support. If user creates a new version and then
>>>>>>> edits
>>>>>>> it
>>>>>>> many times - it is supported. Temporary copy of the object is not
>>>>>>> implemented.
>>>>>>>
>>>>>>> 2007/1/18, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>>>>>>>
>>>>>>>               
>>>>>>>> Qustion regarding copy of UMO. Here is what we have in specs:
>>>>>>>>
>>>>>>>> ----
>>>>>>>> Object editing follows this pattern:
>>>>>>>>
>>>>>>>> 1. Edit Object action is requested. It creates a temporary copy of
>>>>>>>>                 
>>>> an
>>>>         
>>>>>>>> object
>>>>>>>> 2. User edits and saves the copy (it can be saved as many times as
>>>>>>>> needed)
>>>>>>>> ----
>>>>>>>>
>>>>>>>> I can't find in which tables(fields) in DB schema those copys will
>>>>>>>>                 
>>>> be
>>>>         
>>>>>>>> saved. Do we have it there and I'm just missing it?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> --
>>>>>>> Alexey Parshin,
>>>>>>> http://www.sptk.net
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>>
>>>>>>             
>>>>> --
>>>>> Ilya A. Volynets-Evenbakh
>>>>> Total Knowledge. CTO
>>>>> http://www.total-knowledge.com
>>>>>
>>>>>
>>>>>           
>>>>
>>>>         
>>> --
>>> Alexey Parshin,
>>> http://www.sptk.net
>>>
>>>       
>>
>>     
>
>
>   

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