• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!



Page history last edited by Alma Swan 15 years, 2 months ago

Map version


Access-based definitions

• Open Access: free-to-use (Budapest/Bethesda/Berlin definition)

• Closed Access (or Toll-Access): access limited to subscribers

• Protected Access (or Limited Access): Access with the correct permissions (Owner Access is a subset of this)



Workflow-based definitions


NISO/ALPSP Journal Article Versions (JAV): Recommendations of the NISO/ALPSP JAV Technical Working Group (April 2008)


The Working group identified the following important dimensions for an article version: time (from first draft to latest version), added value (from rough draft to polished publication, manifestation/rendition (different document formats and layouts, siblings (mappings between technical reports, conference papers, lectures, journal articles, review articles, etc), stakeholders (author, editor, referee, publisher, librarian, reader, funder).

Definitions of versions

Author's original: Any version of a journal article that is considered by the author to be of sufficient quality to be submitted for formal peer review by a second party. The author accepts full responsibility for the article. May have a version number or date stamp. Content and layout as set out by the author.

Submitted manuscript under review: Any version of a journal article that is under formal review managed by a socially recognized publishing entity. The entity recognizes its responsibility to provide objective expert review and feedback to the author, and, ultimately, to pass judgment on the fitness of the article for publication with an "accept" or "reject" decision. May have a version number or date stamp. Content and layout follow publisher's submission requirements.

Accepted manuscript: The version of a journal article that has been accepted for publication in a journal. A second party (the "publisher") takes permanent responsibility for the article. Content and layout follow publisher's submission requirements.

Proof: A version of a journal article that is created as part of the publication process. This includes the copy-edited manuscript, galley proofs (i.e., a typeset version that has not been made up into pages), page proofs, and revised proofs. Some of these versions may remain essentially internal process versions, but others are commonly released from the internal environment (e.g., proofs are sent to authors) and may thus become public, even though they are not authorized to be so. Content has been changed from Accepted Manuscript; layout is the publisher's.

Version of record: A fixed version of a journal article that has been made available by any organization that acts as a publisher by formally and exclusively declaring the article "published". This includes any "early release" article that is formally identified as being published even before the compilation of a volume issue and assignment of associated metadata, as long as it is citable via some permanent identifier(s). This does not include any "early release" article that has not yet been "fixed" by processes that are still to be applied, such as copy-editing, proof corrections, layout, and typesetting.

Corrected version of record: A version of the Version of Record of a journal article in which errors in the VoR have been corrected. The errors may be author errors, publisher errors, or other processing errors.

Enhanced version of record: A version of the Version of Record of a journal article that has been updated or enhanced by the provision of supplementary material.


'Open Access community' terms in use

eprint: electronic version of a journal article or conference paper (usually in the context of repositories)

preprint: version of an eprint before peer review

postprint: version of an eprint after changes recommended during peer review have been incorporated



Projects on versions/versioning


Version Identification Framework project


A JISC-funded project, led by the London School of Economics, with the following aims: To provide a framework for the identification of versions of digital objects in digital repositories (ii) To inform and support the work of other JISC projects and services in the area of digital repositories and preservation (iii) To disseminate the framework widely in order to achieve community acceptance.

The project identified 5 essential pieces of information: defined dates (ii) identifiers (iii) version numbering (iv) version labels or taxonomies (v) text description

It also identified essential information to embed in a digital object ID tags and properties fields (ii) cover sheet (iii) filename (iv) watermark

The project produced sets of guidelines for specific audiences (repository software, repository management and content creation): http://www.lse.ac.uk/library/vif/Framework/index.html




Project partners: London School of Economics (lead) and Nereus Consortium

A JISC-funded project, with a particular focus on economics, with the following aims: to clarify the position on different versions of academic papers in economics available for deposit in digital repositories, in order to help build trust among academic users of repository content (ii) to produce a toolkit of guidelines about versions for authors, researchers, librarians and others engaged in maintaining digital repositories (iii) to propose standards on versions to JISC to inform discussions and negotiations with stakeholders. The project produced a Toolkit as a project output. V1 is available at: http://www.lse.ac.uk/library/versions/VERSIONS_Toolkit_v1_final.pdf


RIVER (Repository Version Identification) Project

A JISC-funded project (partners London School of Economics, Rightscom Ltd). The project was a scoping study on versioning issues for repositories. It explores terminologies, describes use cases, reports on version control practices in a sample of repositories and makes recommendations to JISC (the funder) and repository managers. Final report: http://www.jisc.ac.uk/uploaded_documents/RIVER%20Final%20Report.pdf


VALREC Project (VALidating REpository Content)


JISC-funded project at the University of Southampton. Aims to report the differences between the repository version of an article and the published version and produce a digital certificate attesting to the differences. Due to produce final report and outcomes.


Comments (0)

You don't have permission to comment on this page.