Thank you for the reminder about the item level versioning, Andrea. In this case I am interested not "versioning" so much as making all versions available, properly dated, but offering a caution to readers in the record (or not) to say that the copy in hand may not be the most recent one published. This is what I would like to discuss. Have others discussed this at their institutions? Are there examples of "disclaimer" text?
An example of documents like this would be a backlog of departmental statistics docs, Annual reports or employee handbooks. These are items important to archive, even if current versions exist and are in current use. Do you mark older versions in metadata with any disclaimer text? thanks again everyone ICB From: <[email protected]<mailto:[email protected]>> on behalf of Bollini Andrea Date: Tuesday, January 10, 2017 at 12:14 AM To: "[email protected]<mailto:[email protected]>" Subject: Re: [dspace-community] archiving "older versions": do caution readers about versions? Examples sought Hi Irene, you can use the item level versioning https://wiki.duraspace.org/display/DSDOC5x/Item+Level+Versioning#ItemLevelVersioning-Viewthehistoryandolderversionsofanitem to give to the users that come from your repository UI the information about the revision of the item. For whom that land directly on the pdf from google scholar out of box you can only suggest to check for new revision on the cover page. Please note that the use of the cover page itself, if the paper is not a working paper "published originally" in your repository is not liked by google scholar. With some customization you can intercept direct request to download pdf file and, if related to outdated version, you can prompt the user with a message asking for confirmation. To do that you should alter the item page presentation to include some extra parameters in the bitstream download to recognize the one that come from the item page, or you can rely on the http referrer header. A servlet filter to intercept the bitstream download can be used to process this extra parameters. Andrea Il 10/01/2017 01:52, Berry, Irene (CIV) ha scritto: Hello all, I have been asked to archive versions of a significant document at our campus that is constantly under revision. I will also be archiving the most current version. There is an concern among some that presenting "outdated" (but archived, available) versions of this document in our public access archive might cause confusion with readers, who may not realize they are holding a version that is not current. I'm interested in how you handle this situation, when Google makes IR content so easy to access from beyond the actual IR. Do you expect that users will take care to look for the most current version? Do you metadata to remind readers to use the most currently available version? Assuming that historical versions of documents in an IR are important to capture, what ideas, experience, suggestions can you share that might offer some comparison for best practices? thank you, Irene Berry Digital Services Librarian Dudley Knox Library Naval Postgraduate School NPS Archive : Calhoun https://calhoun.nps.edu -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout. -- Andrea Bollini Chief Technology and Innovation Officer 4Science, www.4science.it<http://www.4science.it> office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy mobile: +39 333 934 1808 skype: a.bollini linkedin: andreabollini orcid: 0000-0002-9029-1854 an Itway Group Company Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
