> e) I notice that there are object version numbers as
attributes of
> many (all?) objects in OGO. I take it that this is one
of the Zope
> inspirations. I also see that there are comments in
the 'logs' tab
> of the web UI that show what changes have happened
between versions.
> However, in Zope objects can be rolled back to
previous versions but
> I can't see anyway in OGO to revert to a previous
version of an
> object. Moreover, when I've uploaded a file into a
project, I can't
> see that that file becomes versioned, which I thought
was one of the
> document management features of OGO.
> <<
> I found the versions tab for documents. Although I
can't see how to
> roll back to a previous version.
You can retrieve a previous version but I'm not aware of an
explicit
rollback command. For documents a "revert"
operation would be
interesting and probably trivial to implement; although it
might be
best to just pull a previous version into the current
version + 1
instead of doing a true revert (for reason below).
For other objects (Contacts, Tasks, etc...) I'd be opposed
to a rollback
command. The object version is extremely useful for
applications to
maintain a cache of objects for either performance or to
support offline
use. With the object version it is trivial to scan for
objects that
have changed and to detect conflicts when the client tries
to sync with
the server [Oops! both my copy and the copy of the server
have
changed!]. zOGI specifically supports a function for this
<http://code.google.com/p/zogi/wiki/getObjectVersion
sById>. zOGI will
also throw an exception if you attempt to update a Contact
or Enterprise
on the server whose version is less than the version on the
server.
Groupware information is something that very much lends
itself to
offline use + sync.
--
OpenGroupware.org Discussion discuss opengroupware.org
http://mail.opengroupware.org/mailman/listinfo/discuss
|