[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Re: Versioning
Once again. Notifications go in opposite direction.
It is not your choice how to notify people who link to your
object. It's theirs.
sergey@total-knowledge.com wrote:
> So, in this case scenario we don't really have to worry about notifying
> authors after new version is created. We may give them a message once they
> visit their object that "New version was created. In order to view it,
> select it from dropdown below". If they like it and want it to be their
> default at this point, they may just hit "Save" button.
>
>
>> He is my view on how versioning may look on UI(done for course,
>> topic/explanation, explanation)
>>
>> http://gateway.total-knowledge.com/~sergey/UU/CourseEdit.html
>> http://gateway.total-knowledge.com/~sergey/UU/TopicEdit.html
>> http://gateway.total-knowledge.com/~sergey/UU/ExplanationEdit.html
>>
>>
>> Eligible author will be able to view/edit _all_ versions of current object
>> using dropdowns. By default he will see "_his_ + _latest_" version of
>> object if he clicks on the object link from "My UMOs" page or "_latest_"
>> if he comes there from Main Repository/Catalog. Once he updates/saves it
>> there, it becomes "_his_ + _latest_" and temporarily _latest_ for others.
>> Same scenario for all dependencies, dependent object may have different
>> version than parent.
>>
>>
>>
>
>
>
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com