Hi Claire,
There's a JISC project called Versions [1] looking at this issue at the
moment. It's in the context of eprints, or scholarly works, and digital
repositories, but I imagine that findings will have a much wider
interest. They have conducted a couple of detailed user studies to look
at how academics version their own documents.
The Versions project also cites a couple of other initiatives. The
NISO/ALPSP Working Group on Journal Article Versioning [2] and the RIVER
Scoping Study on Repository Version Identification [3].
In addition, the Eprints Application Profile for describing scholarly
works [4], developed by UKOLN and the Eduserv Foundation has creating a
metadata format that support grouping together different versions and
has used IFLA's Functional Requirements for Bibliographic Records (FRBR)
[5] as a basis for its application model.
Hope this helps,
Julie
[1] http://www.lse.ac.uk/library/versions/
[2] http://www.niso.org/committees/Journal_versioning/JournalVer_comm.html
[3] http://www.jisc.ac.uk/uploaded_documents/RIVER%20Final%20Report.pdf
[4]
http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Application_Profile
[5] http://www.ifla.org/VII/s13/frbr/frbr.pdf
Claire Park wrote:
> Does anyone know if there is an accepted 'standard' for applying version
> control to documents?
>
> We have recently discovered that there is a huge difference in the was
> version controls are added to documents across the authority. Admittedly
> in the absence of any corporate guidance users/creators have applied their
> own logic. There is a difficulty understanding what is meant by the
> terms 'draft' and 'version 1/2/3', etc.
>
> If there is a standard, defintion or useful guide I would be grateful if
> someone could point me in the right direction.
>
> Thanks
>
> Claire Park
--
Julie Allinson [log in to unmask]
Repositories Research Officer
UKOLN, University of Bath, Bath BA2 7AY, United Kingdom
Tel: ++44 (0) 114 2486457, ++44 (0) 1225 386580
http://www.ukoln.ac.uk/repositories/
http://www.ukoln.ac.uk/ukoln/staff/j.allinson/
--
|