Well, as I said: it is not for an author to decide what happens to his updated UMO. The UU is to notify all this UMO users it has been updated, period. The users are to decide whether to use the updated UMO, or to keep their current version thereof.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.
-- Anatoly Volynets, Co-Founder total-knowledge.com culturedialogue.org
Authoright © Total Knowledge: 2001-2008