[Building Sakai] Resources versioning

[Matthew Jones]

>From what I remember this was all just design discussion. Back at one time
there was a serious effort made to switch Content Hosting over to
JCR/Jackrabbit as Steve mentioned. That probably would have supplied basic
versioning but agree that seemed like a gigantic project, and maybe not any
easier today. That effort was so long ago that it ended up being used in
the *original* OAE project which also doesn't exist anymore. So my sense is
there's a lot of history with nothing usable in Sakai.

I think you'd essentially need to support some type of binary diffs of
files otherwise you'd eat up too much space, and you probably couldn't
include versions of larger files anyway (like videos) as computing the
deltas would take too long unless it was done in some background job.

Would be a pretty cool addition and one I've thought about. I think the
concept is simple but would take some time to implement and fully test it
all out.


On Sat, Apr 5, 2014 at 6:44 AM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> Hi,
>
> I’ve actually done some work in this area - it is more investigative than
> actual working code we could drop in, but there isn’t a great deal of work
> involved in this if its just a database implementation. There was previous
> work in this area in regards to a JackRabbit content repository, which
> would bring versioning if surfaced in the UI, but that has actually been
> removed from the core source so I’d forget that route.
>
> IMHO the best bet for versioning is to just implement it in the database
> and provide some UI controls to allow it to be managed. Pretty simple stuff.
>
> Happy to discuss further and implement it if you like.
>
> cheers,
> Steve
>
>
> On 5 Apr 2014, at 1:56 am, Qu, Yuanhua <yq12 at txstate.edu> wrote:
>
>  Good morning,
>
>  I found this Jira https://jira.sakaiproject.org/browse/SAK-8159 talking
> about content versioning and also a confluence page
> http://bugs.sakaiproject.org/confluence/display/RES/Versioning+of+resources,
>  but I didn't see any progress for this request.
>
>  We have local request of content versioning,  and our user hope at least
> sakai could support some basic versioning like when you upload or save  a
> same named file, the old one could be saved with a version number and the
> new one becomes active;  user can rollback to the version they want.
>
>  Now 8 years later,  wondering if someone has already get this working
> and would like to share;  if no one yet, would like to draw more attention
> to this feature request to enhance sakai to keep up with nowadays content
> hosting capability.
>
>  Thanks
>
>  -Qu
>  _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140405/b70d515b/attachment.html