{"id":74,"date":"2012-05-15T10:43:00","date_gmt":"2012-05-14T22:43:00","guid":{"rendered":"http:\/\/deborahfitchett.com\/blog\/?p=74"},"modified":"2012-05-15T10:43:00","modified_gmt":"2012-05-14T22:43:00","slug":"institutional-repositories-and-the-problem-of-versions","status":"publish","type":"post","link":"https:\/\/deborahfitchett.com\/blog\/2012\/05\/institutional-repositories-and-the-problem-of-versions\/","title":{"rendered":"Institutional repositories and the problem of versions"},"content":{"rendered":"<p>One of the (many) problems I see our institutional repository running into with busy academics is the utter confusion about what they&#8217;re allowed to upload into it.<\/p>\n<p>We promise them we&#8217;ll check all the copyright for them (at <a href=\"http:\/\/www.sherpa.ac.uk\/romeo\/\">Sherpa\/Romeo<\/a>) and won&#8217;t put anything live that shouldn&#8217;t be live.  Which solves half the problem.<\/p>\n<p>But the other half of the problem is that even when the journal does allow some version to go up, it&#8217;s always a different version.  Some say the preprint is okay but nothing else; some say only the postprint; some say the final publisher&#8217;s version.  So when the author is dutifully filling out the details in the repository submission form, unless they go and do their research (something which we&#8217;re telling them they don&#8217;t have to do) they don&#8217;t know what version to upload.  Even if they do know the difference between a preprint and a postprint or that something labelled &#8220;author&#8217;s copy&#8221; is nevertheless the publisher&#8217;s version.<\/p>\n<p>So, what we need is some magic DSpace (etc) plugin which, once the author&#8217;s filled out the journal field, goes to look that up on Sherpa\/Romeo and pops up a wee box that says &#8220;Cool, you can upload your preprint &#8211; by which we mean [insert clear and concise definition here].&#8221;<\/p>\n<p>Of course I use the word &#8220;magic&#8221; advisedly:  from what I hear of DSpace this&#8217;d be difficult to impossible, and I don&#8217;t imagine other repository management software is light years better.  Ideas are easy, implementation is hard.<\/p>\n<p>(The third half of the problem is that it seems some academics don&#8217;t actually save these previous versions.  A solution to this is probably even harder to centrally automate.)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the (many) problems I see our institutional repository running into with busy academics is the utter confusion about what they&#8217;re allowed to upload into it. We promise them we&#8217;ll check all the copyright for them (at Sherpa\/Romeo) and won&#8217;t put anything live that shouldn&#8217;t be live. Which solves half the problem. But the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[],"tags":[22],"_links":{"self":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts\/74"}],"collection":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/comments?post=74"}],"version-history":[{"count":0,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts\/74\/revisions"}],"wp:attachment":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/media?parent=74"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/categories?post=74"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/tags?post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}