{"id":233,"date":"2009-06-26T10:18:07","date_gmt":"2009-06-26T09:18:07","guid":{"rendered":"http:\/\/blog.soton.ac.uk\/keepit\/?p=233"},"modified":"2009-06-26T17:19:09","modified_gmt":"2009-06-26T16:19:09","slug":"eating-our-own-dogfood","status":"publish","type":"post","link":"https:\/\/blog.soton.ac.uk\/keepit\/2009\/06\/26\/eating-our-own-dogfood\/","title":{"rendered":"Eating our own dogfood?"},"content":{"rendered":"<p><a href=\"http:\/\/www.flickr.com\/photos\/roadsidepictures\/1299788381\/\"><img loading=\"lazy\" decoding=\"async\" class=\"alignright size-medium wp-image-235\" title=\"Safeway Dog Food Display, 1960's, by Roadsidepictures\" src=\"http:\/\/blog.soton.ac.uk\/keepit\/files\/2009\/06\/dogfood-189x300.jpg\" alt=\"\" width=\"189\" height=\"300\" \/><\/a>KeepIt is a preservation project, about preserving digital repositories. But not preserving anything else, it seems. So we stand accused by <a title=\"Preserving URLs, Diary, June 18, 2009\" href=\"http:\/\/blog.soton.ac.uk\/keepit\/2009\/06\/18\/preserving-urls\/\" target=\"_self\">Chris Gutteridge<\/a> of not eating our own dogfood. The evidence is here, in this blog. What are we doing to preserve the content of this blog, the embedded content (Slideshare, YouTube) and the twitters?<\/p>\n<p>Chris says: &#8220;these sites, while amazingly cool and useful, have no contract or  duty of preservation. The universities involved could always keep their  own information, but the &#8220;primary&#8221; URL for each item is likely to be the  one on the above site. That means if the plug is pulled on youtube (is  it making money? can it?) then all those URLs could just go away.&#8221;<\/p>\n<p>The obvious answer is we are distinguishing the project and communications about the project from the object of the project, the repositories. Should we be preserving the project and its outputs as well? Yes. And that&#8217;s a point that goes to the heart of the project&#8217;s approach. You cannot preserve content effectively unless you know what it is you want to preserve, i.e. you need a plan. When it comes to the day-to-day activity of the project as reflected here &#8211; rather than the boiled-down reports and papers that are presented, added to repositories, published, and thus more actively &#8216;preserved&#8217; (or managed) &#8211; we don&#8217;t know what is worth preserving or what should be. We don&#8217;t yet have a plan. What follows instead are some thoughts on the preserving the formal vs the informal, and trying to identify where these might meet in the new online continuum.<\/p>\n<p><strong>WordPress blog<\/strong>. Most heavily used service so far in the project. We are using a blog service hosted in our university school (ecs.soton) rather than a public service, so there is a chance to do  something about preserving that, linking to the repository perhaps. Maybe there  could be a closer association between repositories and blogs. Having  said that, while there are some students using the ECS blog service, I&#8217;m  not sure many academics are, and there could be a message there.<\/p>\n<p>(Note. We will be setting up a project <strong>wiki<\/strong> soon, and will again use the  in-house hosted wiki.)<\/p>\n<p><strong>YouTube\/Slideshare<\/strong>. We are using these principally for the embed  function, to display in the blog. Of the four items embedded in the blog  to date (3 slides <a title=\"First project meeting presentations, Diary, 19 June 2009\" href=\"http:\/\/blog.soton.ac.uk\/keepit\/2009\/06\/19\/first-project-meeting-presentations\/\" target=\"_self\">e.g.<\/a>, 1 <a title=\"Preserving URLs, Diary, June 18, 2009\" href=\"http:\/\/blog.soton.ac.uk\/keepit\/2009\/06\/18\/preserving-urls\/\" target=\"_self\">video<\/a>), one is also in a repository, and the others  we must assume were not considered formal enough by the authors for  repository deposit. Those are the two angles on these types of material  and repositories: display functionality vs scope for deposit.<\/p>\n<p><strong>Twitter<\/strong>. I&#8217;ve only been using it for a few days, so I can&#8217;t comment yet on  its instant ephemerality vs long-term value. I wouldn&#8217;t rule out the  latter in terms of realising some academic value, but my immediate  impression is it&#8217;s not there yet and would have to be heavily filtered.  The practice is not there yet, nor the filter mechanism.<\/p>\n<p>So the project is focussed on preservation of repository content. To  what extent are we seeking to preserve what is in repositories, to shape  content creation practices for better preservation, or to shape  repository policy to accept and therefore preserve a wider range of  content types such as considered here? This is an open question, and one  that we need to try and answer in the remaining year and months of the  project.<\/p>\n<p>The general fact is that practice in digital preservation is always  trying to keep up with content creation practices. McLuhan said the  content of a new medium is an old medium. Hence pdf. Blogs, Twitter (to  come, Google Wave), etc., are the leading-edge content forms for the new  online medium. If it seems obvious and inevitable to state that digital  preservation is always reacting, never leading, Chris is saying this  doesn&#8217;t have to be the case. Content creation, repository support tools,  repository management and preservation are all part of the same  continuum. We all face the same problems. It&#8217;s good to be reminded of that.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>KeepIt is a preservation project, about preserving digital repositories. But not preserving anything else, it seems. So we stand accused by Chris Gutteridge of not eating our own dogfood. The evidence is here, in this blog. What are we doing to preserve the content of this blog, the embedded content (Slideshare, YouTube) and the twitters? [&hellip;]<\/p>\n","protected":false},"author":25,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[41,42],"class_list":["post-233","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-dogfood","tag-non-repository-content"],"_links":{"self":[{"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/posts\/233","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/comments?post=233"}],"version-history":[{"count":13,"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/posts\/233\/revisions"}],"predecessor-version":[{"id":259,"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/posts\/233\/revisions\/259"}],"wp:attachment":[{"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/media?parent=233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/categories?post=233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/keepit\/wp-json\/wp\/v2\/tags?post=233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}