<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-4503292949532760618.post6206724220745404840..comments</id><updated>2010-09-03T09:05:25.963-07:00</updated><category term='CNI2009spring'/><category term='e-journals'/><category term='ipres2008'/><category term='jcdl2010'/><category term='pda2011'/><category term='format migration'/><category term='blog-science'/><category term='storage costs'/><category term='peer review'/><category term='fast11'/><category term='storage failures'/><category term='ipres2010'/><category term='government information'/><category term='format obsolescence'/><category term='open access'/><category term='memento'/><category term='benchmarks'/><category term='normalization'/><category term='scholarly communication'/><category term='publishing business'/><category term='idcc2008'/><category term='fast2009'/><category term='green preservation'/><category term='digital preservation'/><title type='text'>Comments on DSHR's Blog: Why Preserve E-Journals? Post-Cancellation Access</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.dshr.org/feeds/6206724220745404840/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default'/><link rel='alternate' type='text/html' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html'/><author><name>David.</name><uri>http://www.blogger.com/profile/14498131502038331594</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-4503292949532760618.post-1655535153803349351</id><published>2007-07-17T21:05:00.000-07:00</published><updated>2007-07-17T21:05:00.000-07:00</updated><title type='text'>I updated this topic &lt;a href="http://blog.dshr.org...</title><content type='html'>I updated this topic &lt;A HREF="http://blog.dshr.org/2007/07/update-on-post-cancellation-access.html" REL="nofollow"&gt;here&lt;/A&gt;.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/1655535153803349351'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/1655535153803349351'/><link rel='alternate' type='text/html' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html?showComment=1184731500000#c1655535153803349351' title=''/><author><name>David.</name><uri>http://www.blogger.com/profile/14498131502038331594</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html' ref='tag:blogger.com,1999:blog-4503292949532760618.post-6206724220745404840' source='http://www.blogger.com/feeds/4503292949532760618/posts/default/6206724220745404840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1605961295'/></entry><entry><id>tag:blogger.com,1999:blog-4503292949532760618.post-2365604476708789340</id><published>2007-06-20T18:17:00.000-07:00</published><updated>2007-06-20T18:17:00.000-07:00</updated><title type='text'>David – &lt;br&gt;&lt;br&gt;You are mistaken if you find withi...</title><content type='html'>David – &lt;BR/&gt;&lt;BR/&gt;You are mistaken if you find within Portico's response any "marketing spin" or an attempt to create a false impression.  Nor has Portico "been forced to confirm" anything.  Frankly, I find these conclusions puzzling, and I do not understand why you want to attribute to Portico these negative motivations.  I have only attempted to provide an accurate description of the long-term preservation and access role that Portico is able to play.  &lt;BR/&gt;&lt;BR/&gt;Certainly Portico does not address – nor have we ever claimed to address - the full spectrum of the community's wide-ranging preservation and access needs for all digital materials.  Nor is any single entity ever likely to do so.  Publishers and libraries are finding multiple ways to address long-term preservation and access, including Portico.  Approximately 85% of the 6,100+ journals in the Portico archive are covered by the post-cancellation rider.  In many cases Portico is only one means of addressing this concern.  Some libraries and publishers have directly identified and documented mutually satisfactory arrangements; in other cases, publishers and libraries are designating multiple mechanisms to ensure ongoing access.  In these early days of managing and preserving access to digital resources clearly the community wisely believes that a "belt and suspenders" approach is in order.&lt;BR/&gt;&lt;BR/&gt;The critical task is to ensure the long-term preservation of and access to important digital scholarly literature.  Portico is one – but certainly not the only – mechanism to address this need.  The community needs the security that comes from multiple players taking different approaches. Portico's approach, for instance, differs usefully from LOCKSS'.  Publishers deliver their original files to Portico, a step which by itself introduces a certain discipline that helps to ensure the integrity of the content and also creates opportunities to directly engage publishers to resolve any data questions. Portico then takes responsibility for actively managing the archived content and ensuring that it will be migrated forward as data formats and technologies evolve.  This active preservation ensures that the content will be accessible when trigger events occur.  We do not have 100% coverage of journals, nor do we have 100% ability to provide post-cancellation access, but we are constantly increasing our coverage, and we will continue to work cooperatively with libraries and publishers to see to it that Portico successfully delivers on its mission.   We have made progress, and we are encouraged by it, but we recognize that preservation is a marathon, and not a sprint.  &lt;BR/&gt;&lt;BR/&gt;Eileen Fenton&lt;BR/&gt;Executive Director, Portico&lt;BR/&gt;eileen.fenton@portico.org</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/2365604476708789340'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/2365604476708789340'/><link rel='alternate' type='text/html' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html?showComment=1182388620000#c2365604476708789340' title=''/><author><name>Eileen</name><uri>http://www.blogger.com/profile/15544364296689247507</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html' ref='tag:blogger.com,1999:blog-4503292949532760618.post-6206724220745404840' source='http://www.blogger.com/feeds/4503292949532760618/posts/default/6206724220745404840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-72072788'/></entry><entry><id>tag:blogger.com,1999:blog-4503292949532760618.post-8396457239474480405</id><published>2007-06-17T06:51:00.000-07:00</published><updated>2007-06-17T06:51:00.000-07:00</updated><title type='text'>The astute reader will observe two things in the &lt;...</title><content type='html'>The astute reader will observe two things in the &lt;A HREF="http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html#comment-5016135111646223386" REL="nofollow"&gt;comment above&lt;/A&gt;.&lt;BR/&gt;&lt;BR/&gt;First, although the marketing spin contrives to make it look like Portico are disagreeing with me, they have been forced to confirm the factual basis of my statements about their post-cancellation access product. Despite the appearance the comment tries to create, Portico confirms that the  post-cancellation access they offer to institutions is subject to three conditions:&lt;BR/&gt;&lt;BR/&gt;1) The publisher must have signed the rider allowing it. A significant proportion of Portico's publishers have not done so.&lt;BR/&gt;&lt;BR/&gt;2) The institution's Portico subscription must be current. There can be no guarantee that it will be, especially if the institution is so strapped for cash that it has to cancel subscriptions.&lt;BR/&gt;&lt;BR/&gt;3) After each cancellation, the publisher must permit Portico to provide access to the content that institution canceled. While Portico may be right that in most cases this would be a formality, there can be no guarantee that it will be.&lt;BR/&gt;&lt;BR/&gt;In other words, &lt;I&gt;if&lt;/I&gt; everything goes right, it will work for &lt;I&gt;some&lt;/I&gt; publishers, but your mileage may vary. Given this level of uncertainty, it should be hard for Portico to argue that their product is a comprehensive or robust solution to the problem of post-cancellation access.&lt;BR/&gt;&lt;BR/&gt;Second, the trigger events discussed in the latter part of the comment do not apply to post-cancellation access. The discussion would have been more appropriate in a comment on the &lt;A HREF="http://blog.dshr.org/2007/06/why-preserve-e-journals-to-preserve.html" REL="nofollow"&gt;relevant post&lt;/A&gt;, which is where I will address them.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/8396457239474480405'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/8396457239474480405'/><link rel='alternate' type='text/html' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html?showComment=1182088260000#c8396457239474480405' title=''/><author><name>David.</name><uri>http://www.blogger.com/profile/14498131502038331594</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html' ref='tag:blogger.com,1999:blog-4503292949532760618.post-6206724220745404840' source='http://www.blogger.com/feeds/4503292949532760618/posts/default/6206724220745404840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1605961295'/></entry><entry><id>tag:blogger.com,1999:blog-4503292949532760618.post-5016135111646223386</id><published>2007-06-11T22:35:00.000-07:00</published><updated>2007-06-11T22:35:00.000-07:00</updated><title type='text'>I would like to offer a few words of correction an...</title><content type='html'>I would like to offer a few words of correction and clarification regarding post-cancellation access and the Portico archive (&lt;A&gt;www.portico.org&lt;/A&gt;).  David correctly observes that publishers who archive materials with Portico are not required to name Portico as a mechanism for achieving post-cancellation access; it is an option.  Many publishers have a variety of means to meet this need; some do not.  That it is an option to name Portico as a mechanism to meet this need is communicated clearly on the Portico website and in the rider to Portico's participating publisher agreement (&lt;A&gt;www.portico.org/publishers/publisher_license.html&lt;/A&gt;).  It is also reflected in the Portico's agreements with participating libraries (&lt;A&gt;www.portico.org/libraries/library_license.html&lt;/A&gt;).  (More on this below).   David correctly observes that to date approximately two thirds of Portico's participating publishers have chosen to execute the rider.&lt;BR/&gt;&lt;BR/&gt;The rider to the Portico publisher agreement which David quotes simply outlines the process whereby a library subscriber status can be confirmed with the publisher prior to providing post-cancellation access via the Portico website.  This is a logistical arrangement designed to alert the publisher that access is about to be provided to a library and to give an opportunity for any questions about the library's subscriber status to be resolved.  The overall intent of the rider – to enable Portico to act in response to post-cancellation access needs – is clear.  Those publishers who prefer to address this need in another way generally decline the rider while pressing ahead with third-party archival arrangements with Portico.  .&lt;BR/&gt; &lt;BR/&gt;David's posting may have inadvertently created some misimpressions about how access to the Portico archive is structured.  The conditions under which participating libraries may access archived content are detailed in section 2 of the library-Portico agreement and are summarized on the Portico website (&lt;A&gt;www.portico.org/libraries/&lt;/A&gt;).  For convenience, these conditions are summarized here.&lt;BR/&gt;&lt;BR/&gt;Portico provides all libraries supporting the archive with campus-wide access to archived content when specific trigger events occur, and when titles are no longer available from the publisher or other source. Trigger events include:&lt;BR/&gt; A publisher stops operations; or &lt;BR/&gt; A publisher ceases to publish a title; or &lt;BR/&gt; A publisher no longer offers back issues; or &lt;BR/&gt; Upon catastrophic and sustained failure of a publisher's delivery platform. &lt;BR/&gt;In addition, select librarians at participating libraries are granted password-controlled access for verification and audit purposes only.  This password-controlled access is designed to allow participating libraries sufficient pre-trigger event access to the archive to determine that content is well preserved and that the archive is functioning reliably.&lt;BR/&gt;&lt;BR/&gt;Readers with questions about the Portico archive or how access to it is structured are encouraged to contact Portico directly at support@portico.org.  I also welcome any questions or comments sent to me directly at eileen.fenton@portico.org.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/5016135111646223386'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4503292949532760618/6206724220745404840/comments/default/5016135111646223386'/><link rel='alternate' type='text/html' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html?showComment=1181626500000#c5016135111646223386' title=''/><author><name>Eileen</name><uri>http://www.blogger.com/profile/15544364296689247507</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.dshr.org/2007/06/why-preserve-e-journals-post.html' ref='tag:blogger.com,1999:blog-4503292949532760618.post-6206724220745404840' source='http://www.blogger.com/feeds/4503292949532760618/posts/default/6206724220745404840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-72072788'/></entry></feed>
