Hello all,
The VIF framework (www.lse.ac.uk/library/vif) does indeed have a page of
recommendations within software development section of the main body of
the framework, although it doesn't go as far as recommending how a system
should handle versioning. There are also other sections within the same
software development section which describes how the main 3 systems
currently handle versioning.
However, we intend to develop the recommendation section further,
particularly given that EPrints and DSpace are improving their versioning
systems, albeit in different ways.
If anyone is very interested, perhaps you wouldn't mind taking a look at
what is there already (go to Framework and then Software Development
Community) and give us your thoughts on whether you agree with what's
currently there and also what else needs to be addressed, either to this
group or directly to the VIF team (email [log in to unmask] or
[log in to unmask]).
Meanwhile, the project team will do a bit of thinking and come back to
this group with a few questions to see if it isn't possible to start
shaping some kind of opinion on the subject. At the very least we might be
able to provide some clarity as to pros and cons of the different methods.
You may be interested that in our survey conducted last autumn, Fedora had
the most popular versioning system which was to keep all versions,
highlighting the latest added. Although, please note that this was
conducted before the improvements to the other 2 were announced.
One final note - the VIF workshop on the 22nd April in London will have a
section where we have invited 3 exerts from EPrints, DSpace and Fedora to
dscribe how each handles versioning, followed by a panel question and
answer session. The workshop is free so email Dave Puplett if you'd like
to book a place.
Regards,
Jenny Brace
VIF Project Manager
|