CINXE.COM

WebCite Frequently Asked Questions

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("https://web.archive.org/web"); __wm.wombat("https://www.webcitation.org/faq","20210421193254","https://web.archive.org/","web","/_static/", "1619033574"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" /> <!-- End Wayback Rewrite JS Include --> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/><script type="text/javascript">(window.NREUM||(NREUM={})).loader_config={licenseKey:"NRJS-09e243d8a531035d2ee",applicationID:"813503022"};window.NREUM||(NREUM={}),__nr_require=function(e,t,n){function r(n){if(!t[n]){var i=t[n]={exports:{}};e[n][0].call(i.exports,function(t){var i=e[n][1][t];return r(i||t)},i,i.exports)}return t[n].exports}if("function"==typeof __nr_require)return __nr_require;for(var i=0;i<n.length;i++)r(n[i]);return r}({1:[function(e,t,n){function r(){}function i(e,t,n){return function(){return o(e,[u.now()].concat(c(arguments)),t?null:this,n),t?void 0:this}}var o=e("handle"),a=e(7),c=e(8),f=e("ee").get("tracer"),u=e("loader"),s=NREUM;"undefined"==typeof window.newrelic&&(newrelic=s);var d=["setPageViewName","setCustomAttribute","setErrorHandler","finished","addToTrace","inlineHit","addRelease"],p="api-",l=p+"ixn-";a(d,function(e,t){s[t]=i(p+t,!0,"api")}),s.addPageAction=i(p+"addPageAction",!0),s.setCurrentRouteName=i(p+"routeName",!0),t.exports=newrelic,s.interaction=function(){return(new r).get()};var m=r.prototype={createTracer:function(e,t){var n={},r=this,i="function"==typeof t;return o(l+"tracer",[u.now(),e,n],r),function(){if(f.emit((i?"":"no-")+"fn-start",[u.now(),r,i],n),i)try{return t.apply(this,arguments)}catch(e){throw f.emit("fn-err",[arguments,this,e],n),e}finally{f.emit("fn-end",[u.now()],n)}}}};a("actionText,setName,setAttribute,save,ignore,onEnd,getContext,end,get".split(","),function(e,t){m[t]=i(l+t)}),newrelic.noticeError=function(e,t){"string"==typeof e&&(e=new Error(e)),o("err",[e,u.now(),!1,t])}},{}],2:[function(e,t,n){function r(){return c.exists&&performance.now?Math.round(performance.now()):(o=Math.max((new Date).getTime(),o))-a}function i(){return o}var o=(new Date).getTime(),a=o,c=e(9);t.exports=r,t.exports.offset=a,t.exports.getLastTimestamp=i},{}],3:[function(e,t,n){function r(e){return!(!e||!e.protocol||"file:"===e.protocol)}t.exports=r},{}],4:[function(e,t,n){function r(e,t){var n=e.getEntries();n.forEach(function(e){"first-paint"===e.name?d("timing",["fp",Math.floor(e.startTime)]):"first-contentful-paint"===e.name&&d("timing",["fcp",Math.floor(e.startTime)])})}function i(e,t){var n=e.getEntries();n.length>0&&d("lcp",[n[n.length-1]])}function o(e){e.getEntries().forEach(function(e){e.hadRecentInput||d("cls",[e])})}function a(e){if(e instanceof m&&!g){var t=Math.round(e.timeStamp),n={type:e.type};t<=p.now()?n.fid=p.now()-t:t>p.offset&&t<=Date.now()?(t-=p.offset,n.fid=p.now()-t):t=p.now(),g=!0,d("timing",["fi",t,n])}}function c(e){d("pageHide",[p.now(),e])}if(!("init"in NREUM&&"page_view_timing"in NREUM.init&&"enabled"in NREUM.init.page_view_timing&&NREUM.init.page_view_timing.enabled===!1)){var f,u,s,d=e("handle"),p=e("loader"),l=e(6),m=NREUM.o.EV;if("PerformanceObserver"in window&&"function"==typeof window.PerformanceObserver){f=new PerformanceObserver(r);try{f.observe({entryTypes:["paint"]})}catch(v){}u=new PerformanceObserver(i);try{u.observe({entryTypes:["largest-contentful-paint"]})}catch(v){}s=new PerformanceObserver(o);try{s.observe({type:"layout-shift",buffered:!0})}catch(v){}}if("addEventListener"in document){var g=!1,w=["click","keydown","mousedown","pointerdown","touchstart"];w.forEach(function(e){document.addEventListener(e,a,!1)})}l(c)}},{}],5:[function(e,t,n){function r(e,t){if(!i)return!1;if(e!==i)return!1;if(!t)return!0;if(!o)return!1;for(var n=o.split("."),r=t.split("."),a=0;a<r.length;a++)if(r[a]!==n[a])return!1;return!0}var i=null,o=null,a=/Version\/(\S+)\s+Safari/;if(navigator.userAgent){var c=navigator.userAgent,f=c.match(a);f&&c.indexOf("Chrome")===-1&&c.indexOf("Chromium")===-1&&(i="Safari",o=f[1])}t.exports={agent:i,version:o,match:r}},{}],6:[function(e,t,n){function r(e){function t(){e(a&&document[a]?document[a]:document[i]?"hidden":"visible")}"addEventListener"in document&&o&&document.addEventListener(o,t,!1)}t.exports=r;var i,o,a;"undefined"!=typeof document.hidden?(i="hidden",o="visibilitychange",a="visibilityState"):"undefined"!=typeof document.msHidden?(i="msHidden",o="msvisibilitychange"):"undefined"!=typeof document.webkitHidden&&(i="webkitHidden",o="webkitvisibilitychange",a="webkitVisibilityState")},{}],7:[function(e,t,n){function r(e,t){var n=[],r="",o=0;for(r in e)i.call(e,r)&&(n[o]=t(r,e[r]),o+=1);return n}var i=Object.prototype.hasOwnProperty;t.exports=r},{}],8:[function(e,t,n){function r(e,t,n){t||(t=0),"undefined"==typeof n&&(n=e?e.length:0);for(var r=-1,i=n-t||0,o=Array(i<0?0:i);++r<i;)o[r]=e[t+r];return o}t.exports=r},{}],9:[function(e,t,n){t.exports={exists:"undefined"!=typeof window.performance&&window.performance.timing&&"undefined"!=typeof window.performance.timing.navigationStart}},{}],ee:[function(e,t,n){function r(){}function i(e){function t(e){return e&&e instanceof r?e:e?u(e,f,a):a()}function n(n,r,i,o,a){if(a!==!1&&(a=!0),!l.aborted||o){e&&a&&e(n,r,i);for(var c=t(i),f=v(n),u=f.length,s=0;s<u;s++)f[s].apply(c,r);var p=d[h[n]];return p&&p.push([b,n,r,c]),c}}function o(e,t){y[e]=v(e).concat(t)}function m(e,t){var n=y[e];if(n)for(var r=0;r<n.length;r++)n[r]===t&&n.splice(r,1)}function v(e){return y[e]||[]}function g(e){return p[e]=p[e]||i(n)}function w(e,t){s(e,function(e,n){t=t||"feature",h[n]=t,t in d||(d[t]=[])})}var y={},h={},b={on:o,addEventListener:o,removeEventListener:m,emit:n,get:g,listeners:v,context:t,buffer:w,abort:c,aborted:!1};return b}function o(e){return u(e,f,a)}function a(){return new r}function c(){(d.api||d.feature)&&(l.aborted=!0,d=l.backlog={})}var f="nr@context",u=e("gos"),s=e(7),d={},p={},l=t.exports=i();t.exports.getOrSetContext=o,l.backlog=d},{}],gos:[function(e,t,n){function r(e,t,n){if(i.call(e,t))return e[t];var r=n();if(Object.defineProperty&&Object.keys)try{return Object.defineProperty(e,t,{value:r,writable:!0,enumerable:!1}),r}catch(o){}return e[t]=r,r}var i=Object.prototype.hasOwnProperty;t.exports=r},{}],handle:[function(e,t,n){function r(e,t,n,r){i.buffer([e],r),i.emit(e,t,n)}var i=e("ee").get("handle");t.exports=r,r.ee=i},{}],id:[function(e,t,n){function r(e){var t=typeof e;return!e||"object"!==t&&"function"!==t?-1:e===window?0:a(e,o,function(){return i++})}var i=1,o="nr@id",a=e("gos");t.exports=r},{}],loader:[function(e,t,n){function r(){if(!E++){var e=x.info=NREUM.info,t=l.getElementsByTagName("script")[0];if(setTimeout(u.abort,3e4),!(e&&e.licenseKey&&e.applicationID&&t))return u.abort();f(h,function(t,n){e[t]||(e[t]=n)});var n=a();c("mark",["onload",n+x.offset],null,"api"),c("timing",["load",n]);var r=l.createElement("script");r.src="https://"+e.agent,t.parentNode.insertBefore(r,t)}}function i(){"complete"===l.readyState&&o()}function o(){c("mark",["domContent",a()+x.offset],null,"api")}var a=e(2),c=e("handle"),f=e(7),u=e("ee"),s=e(5),d=e(3),p=window,l=p.document,m="addEventListener",v="attachEvent",g=p.XMLHttpRequest,w=g&&g.prototype;if(d(p.location)){NREUM.o={ST:setTimeout,SI:p.setImmediate,CT:clearTimeout,XHR:g,REQ:p.Request,EV:p.Event,PR:p.Promise,MO:p.MutationObserver};var y=""+location,h={beacon:"bam.nr-data.net",errorBeacon:"bam.nr-data.net",agent:"js-agent.newrelic.com/nr-1208.min.js"},b=g&&w&&w[m]&&!/CriOS/.test(navigator.userAgent),x=t.exports={offset:a.getLastTimestamp(),now:a,origin:y,features:{},xhrWrappable:b,userAgent:s};e(1),e(4),l[m]?(l[m]("DOMContentLoaded",o,!1),p[m]("load",r,!1)):(l[v]("onreadystatechange",i),p[v]("onload",r)),c("mark",["firstbyte",a.getLastTimestamp()],null,"api");var E=0}},{}],"wrap-function":[function(e,t,n){function r(e,t){function n(t,n,r,f,u){function nrWrapper(){var o,a,s,p;try{a=this,o=d(arguments),s="function"==typeof r?r(o,a):r||{}}catch(l){i([l,"",[o,a,f],s],e)}c(n+"start",[o,a,f],s,u);try{return p=t.apply(a,o)}catch(m){throw c(n+"err",[o,a,m],s,u),m}finally{c(n+"end",[o,a,p],s,u)}}return a(t)?t:(n||(n=""),nrWrapper[p]=t,o(t,nrWrapper,e),nrWrapper)}function r(e,t,r,i,o){r||(r="");var c,f,u,s="-"===r.charAt(0);for(u=0;u<t.length;u++)f=t[u],c=e[f],a(c)||(e[f]=n(c,s?f+r:r,i,f,o))}function c(n,r,o,a){if(!m||t){var c=m;m=!0;try{e.emit(n,r,o,t,a)}catch(f){i([f,n,r,o],e)}m=c}}return e||(e=s),n.inPlace=r,n.flag=p,n}function i(e,t){t||(t=s);try{t.emit("internal-error",e)}catch(n){}}function o(e,t,n){if(Object.defineProperty&&Object.keys)try{var r=Object.keys(e);return r.forEach(function(n){Object.defineProperty(t,n,{get:function(){return e[n]},set:function(t){return e[n]=t,t}})}),t}catch(o){i([o],n)}for(var a in e)l.call(e,a)&&(t[a]=e[a]);return t}function a(e){return!(e&&e instanceof Function&&e.apply&&!e[p])}function c(e,t){var n=t(e);return n[p]=e,o(e,n,s),n}function f(e,t,n){var r=e[t];e[t]=c(r,n)}function u(){for(var e=arguments.length,t=new Array(e),n=0;n<e;++n)t[n]=arguments[n];return t}var s=e("ee"),d=e(8),p="nr@original",l=Object.prototype.hasOwnProperty,m=!1;t.exports=r,t.exports.wrapFunction=c,t.exports.wrapInPlace=f,t.exports.argsToArray=u},{}]},{},["loader"]);</script> <title>WebCite Frequently Asked Questions</title> <link rel="stylesheet" type="text/css" href="/web/20210421193254cs_/https://www.webcitation.org/basic.css"/> <link rel="stylesheet" type="text/css" href="/web/20210421193254cs_/https://www.webcitation.org/nicetitle.css"/> <script src="https://web.archive.org/web/20210421193254js_/https://www.google.com/recaptcha/api.js" async defer></script> </head> <body> <!-- Google analytics code added 16/01/08 --> <script src="https://web.archive.org/web/20210421193254js_/http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> <script type="text/javascript"> _uacct = "UA-186918-2"; urchinTracker(); </script> <style> .alert-box { text-align: center; padding: 0.125rem; margin-bottom: 20px; border: 1px solid transparent; border-radius: 4px; color: #8a6d3b; background-color: #fcf8e3; border-color: #faebcc; } </style> <div style="width: 75%; margin: auto"> <section class="alert-box"> <p><i class="fas fa-exclamation-circle"></i> <strong>We are currently not accepting archiving requests.</strong> The archival state/snapshots of websites that have been archived with WebCite in the past can still be accessed and cited.</p> </section> </div> <table class="topmaster" cellspacing="0" cellpadding="0"> <tr> <td colspan="2" class="titlebanner"><a href="index">WebCite</a></td> </tr> <tr> <td colspan="2" class="linkbanner"> [ <a href="/web/20210421193254/https://www.webcitation.org/index" title="Home" class="linkbannerlinks">HOME</a> | <a href="/web/20210421193254/https://www.webcitation.org/faq" title="Answers about WebCite" class="linkbannerlinks">FAQ</a> | <a href="/web/20210421193254/https://www.webcitation.org/news" title="Press Reports and News" class="linkbannerlinks">NEWS</a> | <a href="/web/20210421193254/https://www.webcitation.org/members" title="List of WebCite Consortium members" class="linkbannerlinks">MEMBERS</a> | <a href="/web/20210421193254/https://www.webcitation.org/query" title="Search for Stored WebCites" class="linkbannerlinks">SEARCH</a> ] </td> </tr> <tr> <td class="mainbody"> <table> <tr> <td colspan="2"> <h1>WebCite<sup>&reg;</sup> Consortium FAQ</h1> </td> </tr> <tr> <td class="twocolumn"> <h2>As an individual (scholar/student/researcher), do I have to become member of the consortium in order to use WebCite<sup>&reg;</sup>?</h2> <p>No formal membership or even registration is required. For individual scholars who want to cite and archive (=”to webcite<sup>&reg;</sup>”) a web document, this is a free and open service, and you can use WebCite<sup>&reg;</sup> right away, for example by going to the <a href="/web/20210421193254/https://www.webcitation.org/archive">archive</a> form, without being a member.</p> <h2>Why should editors, publishers, and libraries join the WebCite<sup>&reg;</sup> consortium?</h2> <p>Webpages or websites which are cited in scholarly articles are presumably important documents worth preserving for readers, yet due to the volatility of the World Wide Web they are at risk to disappear as a reference for future scholars. Adding WebCite<sup>&reg;</sup> links to cited URLs increases the likelihood that the cited work remains accessible and ensures that readers have access to exactly the version as seen by the citing author.</p> <h2>How does this work?</h2> <p>The archiving process is simple: WebCite takes a snapshot of a cited webpage and stores a copy of the html including images (or any other files, for example pdf) on the webcitation server.</p> <p>The caching (archiving) process can be initiated prospectively (before publication) by the author or the editor, copyeditor or publisher at the time he/she authors, edits, or publishes the citing document. WebCite<sup>&reg;</sup> also has a crawler capability, allowing retrospective (after publication) archiving. Here, the publisher would submit XML files of already published articles (or point us to a website where WebCite<sup>&reg;</sup> can access the full text articles). The WebCite<sup>&reg;</sup> crawler will then go through the references and attempt to retrospectively archive cited webpages, although there is no guarantee that these will still be available and that what is being archived is what the author saw when he/she cited the webdocument. We therefore urge authors, editors, and publishers to prospectively archive webcitations when the write or edit articles.</p> <h2>What is the goal of the WebCite<sup>&reg;</sup> consortium?</h2> <p>WebCite<sup>&reg;</sup> members are editors, publishers, libraries, and other interested entities pursuing a common goal: Digital archiving of webpages or websites which are referenced in scholarly journal articles, therefore preserving the scholarly record and our cultural heritage for future generations (for the broader societal implications see below). Beyond these broader objectives, WebCite<sup>&reg;</sup> solves some practical problems, creating some utility and value for readers, providing a solution to "404 File Not Found" errors when clicking on cited webreferences. It also avoids the problems associated with the dynamic nature of Web content, making sure that the reader sees the webdocument exactly the way the author saw it when he cited it. For example, a citing author may critique a report published online. Responding to the critique, the cited author of the online report may subsequently make changes and republish the report at the same URL, without the reader of the critique being able to retrieve the version the citing author has critiqued - the scholarly record is lost. </p> <p>In addition, WebCite<sup>&reg;</sup> will provide "impact statistics" of webpages and websites (number of citations of a given website or webpage in the scholarly literature, combined with access data), helping for example tenure and promotion committees to establish the "impact" and importance of webservices and digital objects, complementing metrics like the Journal Impact Factor developed by ISI (the latter measures the impact of a scientific journal based on how often articles from a specific journal are cited).</p> <h2>What are the broader societal implications and objectives?</h2> <p>The people behind WebCite<sup>&reg;</sup> are social entrepreneurs, driven by the desire to instigate social change. WebCite<sup>&reg;</sup> is a simple yet disruptive application, which has wider societal implications and a potentially significant impact on scholarship and scholarly communication. </p> <p>Simply put, WebCite<sup>&reg;</sup> aims to make Internet material (any sort of digital objects) more "citable", long-term accessible, and hence more acceptable for scholarly purposes. Without WebCite<sup>&reg;</sup>, Internet citations are deemed ephemeral and therefore are often frowned upon by authors and editors. However, it does not make much sense to ignore opinions, ideas, draft papers, or data published on the Internet (including wikis and blogs), not acknowledging them only because they are not "formally" published, and because they are difficult to cite. The reality is that in the age of the Internet, "publication" is a continuum, and it makes little sense to not cite (therefore acknowledge) for example the idea of a scholarly blogger, the collective wisdom of a wiki, ideas from an online discussion paper, or data from an online accessible dataset only because online material is not deemed "citable". By making Internet material more "citable" (and also by creating incentives such as mechanisms and metrics for measuring the "impact" of online material by calculating and publishing WebCite<sup>&reg;</sup> impact factor), we hope that this will encourage scholars to publish ideas and data online in a wide range of formats, which in turn should accelerate and facilitate the exchange of scientific ideas. While we do see the value of scholarly peer-reviewed journals for publishing research results (many of us are editors and publishers of peer-reviewed journals ourselves!), we also acknowledge that much of the scientific discourse takes place before it is "formally" published, and that peer-review can also take on other forms (e.g. post-publication peer-review, which is something WebCite<sup>&reg;</sup> plans to implement). </p> <p>Another broader societal aspect of the WebCite<sup>&reg;</sup> initiative is advocacy and research in the area of copyright. We aim to develop a system which balances the legitimate rights of the copyright-holders (e.g. cited authors and publishers) against the "fair use" rights of society to archive and access important material. We also advocate and lobby for a non-restrictive interpretation of copyright which does not impede digital preservation of our cultural heritage, or free and open flow of ideas. This should not be seen as a threat by copyright-holders - we aim to keep material which is currently openly accessible online accessible for future generations without creating economic harm to the copyright holder. This is a challenging, but feasible goal, and future iterations of this service may include some sort of revenue sharing mechanism for copyright holders.</p> <p>Yet another angle is that WebCite<sup>&reg;</sup> enables "one-click self-archiving", making it very easy for scholarly authors to create a permanent, openly accessible record of their own work and their ideas. While the primary pathway in the WebCite<sup>&reg;</sup> system is third-party initiated archiving (triggered by a citing author), WebCite<sup>&reg;</sup> also provides a very simple mechanism for authors to self-archive their own work.</p> <h2>Who is behind the WebCite<sup>&reg;</sup> Consortium?</h2> <p>WebCite<sup>&reg;</sup> is run by editors for editors, and by publishers for publishers. The system was invented by Dr. Gunther Eysenbach, Editor and Publisher of the <i>Journal of Medical Internet Research</i>, Senior Scientist at the Centre for Global eHealth Innovation, and Associate Professor at the Department of Health Policy, Management and Evaluation at the University of Toronto.</p> <h2>What is the history of this service?</h2> <p>The WebCite<sup>&reg;</sup> idea was first conceived in 1997 and mentioned in a 1998 article (BMJ 1998;317:1496-1502) on quality control on the Internet, alluding to the fact that such a service dubbed webcite.net would also be useful to measure the citation impact of webpages. In the same year, a pilot service was set up. However, shortly after, Google and the Internet Archive entered the market, both apparently making a service like WebCite<sup>&reg;</sup> redundant, providing a basic mechanism to retrieve older versions of a given URL. The WebCite<sup>&reg;</sup> idea was revived in 2003, when a study published in the journal <i>Science</i> concluded that there is still no appropriate and agreed on solution in the publishing world available, and that cited webreferences were to a large degree no longer accessible. In addition to the accessibility problem it is always unclear whether the reader sees exactly the version the author saw when he/she cited a webreference. Traditional Internet archives and Google do not allow for "on-demand" archiving by authors, and = more importantly - do not have dedicated services and interfaces to scholarly journals and publishers to automate the archiving of cited links. In 2005, the first journal announced using WebCite<sup>&reg;</sup> routinely, and hundreds of other journals followed. In fact, what is visible to the public (this website) </p> <h2>Who owns and runs WebCite<sup>&reg;</sup> at the moment?</h2> <p>WebCite<sup>&reg;</sup> has been incubated and is still hosted at the University of Toronto / University Health Network's <a href="https://web.archive.org/web/20210421193254/http://www.ehealthinnovation.org/">Centre for Global eHealth Innovation</a>. Partners include the Faculty of Information Studies at the University of Toronto, University of Toronto Library, and Internet archives. An increasing number of journal editors and publishers are currently joining the growing WebCite<sup>&reg;</sup> Consortium. We are currently in the process of incorporating WebCite<sup>&reg;</sup> as a distinct entity. Many of the tools we use and develop are open source.</p> </td> <td class="twocolumn"> <h2>How can I be assured that archived material remains accessible and that webcitation.org doesn't disappear in the future?</h2> <p>WebCite<sup>&reg;</sup> used to be a member a member of the International Internet Preservation Consortium (IIPC). Members of the IIPC (e.g. libraries) are concerned with the collection, preservation and long-term access of a rich body of Internet content from around the world, and develop and use common tools, techniques and standards for the creation of international archives, which may also include the exchange of data. WebCite<sup>&reg;</sup> feeds its content to digital preservation partners such as libraries and the Internet Archive (archive.org). WebCite<sup>&reg;</sup> is operated and supported by publishers, who are already using it for their journals and citations and therefore have a vital interest in keeping the service alive. </p> <p>Finally, the DOI handle system enables a mechanism to cite and retrieve an archived copy of a webpage without having to rely on the functionality of WebCite<sup>&reg;</sup> and the webcitation.org URL itself. WebCite<sup>&reg;</sup> can, under certain circumstances, assign DOIs to archived copies, which are identified by their hash (a digital fingerprint). Archived copies can then be retrieved through http://dx.doi.org (either from WebCite<sup>&reg;</sup>, or from other digital preservation organizations), providing a mechanism for cross-archive retrieval of archived material.</p> <h2>Doesn't something like this already exist? What about CrossRef, Google or the Wayback Machine?</h2> <p>No. While systems such as Digital Object Identifier (DOI) and CrossRef ensure to a certain degree the stability of cross-links to other journal articles and other materials carrying a Digital Object Identifier (DOI), cited non-journal webpages (for example links to questionnaires on the web, research reports, quotes from homepages etc.) do not usually have a DOI. To assign a DOI, a document has to be stable, and it must be formally "published". WebCite<sup>&reg;</sup> can do both - "freezing" the status of a webdocument by taking a snapshot, and then - if desired by the author of the cited material - assign a DOI (this functionality is planned to be implemented in 2008).</p> <p>Services such as the Internet Archive (Wayback Machine) or Google archive Internet documents in a shotgun-approach by a crawler, not focussing on academic references. The caching process cannot be initiated by authors, editors, or publishers wanting to archive a specific web reference as they saw it on a specific date when they quoted it. In contrast, WebCite<sup>&reg;</sup> is a tool specifically designed to be used by authors, readers, editors and publishers of scholarly material, allowing them to permanently archive cited Internet references. It is now used by an increasing number of authors and journals, ensuring future availability of cited webreferences for scholars reading the citing article in 1, 3, 5 or 10 years from now. WebCite<sup>&reg;</sup> has built a XML-based webservice architecture which enables for example publishers, webmasters, editors, institutions, and vendors of bibliographic software packages to exchange data (e.g. metadata) and to trigger an archiving request. As such, WebCite<sup>&reg;</sup> can be seen as providing the "glue" between the scholarly community (authors/editors/publishers) and the digital preservation community.</p> <!--- <h2>Tell me more about DOIs. Can they be assigned to webmaterial archived in WebCite<sup>&reg;</sup>?</h2> <p>DOIs are a widely adopted persistent identifier for scholarly works. However, they are only assigned by "traditional" publishers, through CrossRef. Here is how this currently works:</p> <blockquote> <p>Publishers of electronic scholarly content join CrossRef as members and are assigned a DOI prefix. For each content item a publisher wants to register in the system, it creates a unique DOI name (incorporating the assigned prefix) and associates it with the item’s metadata and the URL where the item resides. The publisher submits the record to the CrossRef metadata database (MDDB) in a strict XML format. (The publisher can also submit citations contained in a deposited article to CrossRef to add outbound links to other content already registered in the CrossRef system. (...) </p><p> CrossRef then registers each DOI name and URL in a central DOI directory. When a user selects a DOI name link, the DOI name redirects to the current URL for the item in the central directory, thereby establishing permanent inbound links to the content that other publishers, libraries, affiliates, and researchers can retrieve from CrossRef. If a publisher changes the location of the content at a later date, it needs to update the URL in only one place: with CrossRef. (Source: <a href="http://www.webcitation.org/5Uhi0HKTA">CrossRef</a>)</p> </blockquote> <p>"Unpublished" or self-published material usually does not have a DOI. In fact, it is against CrossRef policy to assign multiple DOIs to multiple versions of the same document, which precludes for example assigning a DOI automatically to every piece of material in WebCite<sup>&reg;</sup>, because we do not have "control" over that material. We do not know whether a DOI has already been assigned or will be assigned to that material, and we do not know if the online work is simply a different manifestation of another manifestation (print, html, and pdf versions of the same work all should have the same DOI). </p> <p>But here is our plan for expanding the functionality for paying premium members: WebCite<sup>&reg;</sup> is in fact a CrossRef member, has a DOI prefix, and can under certain circumstances assign DOIs to archived webmaterial. If the author / copyright holder of material archived in WebCite<sup>&reg;</sup> requests it, we can very easily assign a DOI to the material. In this case, WebCite<sup>&reg;</sup> acts like a publisher, and will register the DOI with CrossRef. The DOI has the format "10.2196/webcite.xxx" (where xxx is the hash key of the material in WebCite<sup>&reg;</sup>). Entering the DOI at dx.doi.org would then resolve to a WebCite<sup>&reg;</sup> page (or an intermediary page pointing to the same work in other archives, in other manifestations such as print or pdf, or - in the case of online preprints - to "final" publications). The author would have to take certain responsibility to maintain the DOI record, for example entering other DOIs of another publisher into our database, should the work be published elsewhere (e.g. in a scholarly journal).Different versions of the same work can be pointed to from the response page on WebCite<sup>&reg;</sup> to which the DOI resolves. As CrossRef charges us per DOI, and because curation of the metadata on our part is required, authors and organizations requesting DOIs for WebCite<sup>&reg;</sup> archived material have to be premium members (available in 2008).</p> <p>WebCite<sup>&reg;</sup> uses DOIs also in another context: To identify citing documents. A query to the WebCite<sup>&reg;</sup> archive handing over a DOI of a citing document and a cited URL will retrieve the cited URL as it looked like when the citing document was published. </p> --> <h2>What about copyright issues?</h2> <p>Caching and archiving webpages is widely done (e.g. by Google, Internet Archive etc.), and is not considered a copyright infringement, as long as the copyright owner has the ability to remove the archived material and to opt out. WebCite<sup>&reg;</sup> honors robot exclusion standards, as well as no-cache and no-archive tags. Please contact us if you are the copyright owner of an archived webpage which you want to have removed.</p> <p>A U.S. court has recently (Jan 19th, 2006) ruled that caching does not constitute a copyright violation, because of <em>fair use</em> and an <em>implied license</em> (<a href="https://web.archive.org/web/20210421193254/http://www.webcitation.org/query?id=1138565968295754">Field vs Google</a>, US District Court, District of Nevada, CV-S-04-0413-RCJ-LRL, see also <a href="https://web.archive.org/web/20210421193254/http://www.webcitation.org/query?id=1138565951713503">news article on Government Technology</a>). <em>Implied license</em> refers to the industry standards mentioned above: If the copyright holder does not use any no-archive tags and robot exclusion standards to prevent caching, WebCite<sup>&reg;</sup> can (as Google does) assume that a license to archive has been granted. Fair use is even more obvious in the case of WebCite<sup>&reg;</sup> than for Google, as Google uses a “shotgun” approach, whereas WebCite<sup>&reg;</sup> archives selectively only material that is relevant for scholarly work. Fair use is therefore justifiable based on the fair-use principles of <em>purpose</em> (caching constitutes transformative and socially valuable use for the purposes of archiving, in the case of WebCite<sup>&reg;</sup> also specifically for academic research), the <em>nature</em> of the cached material (previously made available for free on the Internet, in the case of WebCite<sup>&reg;</sup> also mainly scholarly material), <em>amount</em> and substantiality (in the case of WebCite<sup>&reg;</sup> only cited webpages, rarely entire websites), and <em>effect</em> of the use on the potential market for or value of the copyrighted work (in the case of Google it was ruled that there is no economic effect, the same is true for WebCite<sup>&reg;</sup>).</p> <p> Please also see <a href="policy.php">Webcite Takedown Requests Policy</a> </p> <h2>Who is going to pay for this?</h2> <p>There are various revenue streams to cover the ongoing costs of operations. One revenue stream is from publishers who pay a membership fee (similar to PILA/CrossRef membership fees) to have their publications analyzed and cited webreferences archived. There is no fee for citing authors. In 2008, we plan to offering premium membership accounts for institutions and individual users, creating revenue streams for copyright owners ("cited authors") such as content-specific ads, enabling DOI<sup>&reg;</sup> (Digital Object Identifier) assignment for cited non-journal material, and offering access to advanced access/webcitation statistics including a WebCite<sup>&reg;</sup> impact factor.</p> <h2>I am working on a grant-funded project / on a proposal for a grant-funded project. Can we do something together?</h2> <p>Most definitively - please contact us. We are already involved in a number of collaborative projects, for example involving wiki-like scholarly projects, where we have to develop mechanisms to make the work "citable", or projects which involve the preservation of more complex citable units such as datasets and interactive programs. Speak to us.</p> <h2>I am working as a project officer at a foundation - can we sponsor/fund you?</h2> <p>Most definitively talk to us...</p> <h2>How can I become involved?</h2> <p>To become a member of the WebCite<sup>&reg;</sup> Consortium as a publisher, editor, or digital preservation partner, fill in the <a href="mailform.php">membership form</a>, or contact us at:</p> <p>WebCite<sup>&reg;</sup> Consortium<br/> <a href="https://web.archive.org/web/20210421193254/http://www.webcitation.org/">http://www.webcitation.org</a><br/> c/o Centre for Global eHealth Innovation<br/> Toronto General Hospital<br/> R Fraser Elliott Building, 4th Floor,&nbsp; Room 4S435<br/> 190 Elizabeth Street<br/> Toronto ON, M5G 2C4<br/> Telephone (+1) 416-340-4800 Ext. 6427<br/> Fax (+1) 416-340-3595<br/> <a href="https://web.archive.org/web/20210421193254/mailto:geysenba@jmir.org">geysenba@gmail.org</a></p> </td> </tr> <tr> <td colspan="2"> <h1>WebCite<sup>&reg;</sup> Technical FAQ</h1> </td> </tr> <tr> <td class="twocolumn"> <h2>What if I want to archive multiple pages, or an entire site?</h2> <p>We're working on a number of enhancements to the WebCite<sup>&reg;</sup> service along these exact lines. Until such time as they are ready, the <a href="/web/20210421193254/https://www.webcitation.org/archive">archive</a> and <a href="/web/20210421193254/https://www.webcitation.org/comb">comb</a> pages are the only publicly available ways of initiating archiving operations. There are some simple workarounds, however. If you're trying to archive an article that is broken up into multiple pages (as many news sites do with longer stories), look for a 'Printable version' of the article -- many sites provide a single page version of content for printing purposes, also ideally suited for WebCite<sup>&reg;</sup> archiving. Note that unless the copyright holder uses a liberal license such as Creative Commons, you must obey to the fair use principle. Archiving multiple pages or an entire website may not be allowable.</p> <h2>Why do some archived pages appear to 'pop out' of the WebCite<sup>&reg;</sup> interface immediately after they load?</h2> <p>Page authors frequently use a bit of JavaScript trickery to ensure that their pages aren't viewed within a frame. This is done to discourage the 'wrapping' of their content without the permission, and is commonly used by many web sites (particularly news and reference sites). Because the WebCite<sup>&reg;</sup> interface uses frames, the archived pages detect this as a wrapping attempt, and use JavaScript to 'pop out' of the WebCite<sup>&reg;</sup> interface.</p> </td> <td class="twocolumn"> <h2>Why are some pages not archived successfully?</h2> <p>A page may not be archived for a number of reasons. The page owner may specifically prohibit archiving of their content through no-cache / no-archive tags, or via a <a href="https://web.archive.org/web/20210421193254/http://www.robotstxt.org/wc/norobots.html">robot exclusion policy</a> on their site. The content may be inaccessible from the WebCite<sup>&reg;</sup> network (this is particularly likely if you are attempting to access subscription based content which your institution subscribes to on its users' behalf). Also, the content may be unreadable by the WebCite<sup>&reg;</sup> archiver (complex JavaScript based pages, or ones involving browser checks sometimes cause our archive engine to fail).</p> <h2>What if I need more detailed information about how to use WebCite<sup>&reg;</sup> or about how WebCite<sup>&reg;</sup> works?</h2> <p>The WebCite<sup>&reg;</sup> has created a <a href="doc/WebCiteBestPracticesGuide.pdf">WebCite Technical Background and Best Practices Guide</a> just for this purpose. </p> </td> </tr> </table> </td> </tr> </table> <div class="footer"> [ <a href="/web/20210421193254/https://www.webcitation.org/privacy" title="WebCite's Privacy Policy">Privacy</a> | <a href="/web/20210421193254/https://www.webcitation.org/contact" title="Contact WebCite">Contact Us</a> | <a href="/web/20210421193254/https://www.webcitation.org/license" title="Legal and Copyright Information">Legal Information</a> | <a href="/web/20210421193254/https://www.webcitation.org/policy.php" title="Webcite Takedown Requests Policy">Takedown Policy</a> ] <br/> <a rel="license" href="https://web.archive.org/web/20210421193254/http://creativecommons.org/licenses/by-nc-sa/2.5/"><img alt="Creative Commons License" src="https://web.archive.org/web/20210421193254im_/http://creativecommons.org/images/public/somerights20.png"/></a><br/> Except for archived content, this site is licensed under a <br/><a rel="license" href="https://web.archive.org/web/20210421193254/http://creativecommons.org/licenses/by-nc-sa/2.5/">Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License</a>. </div> <script type="text/javascript">window.NREUM||(NREUM={});NREUM.info={"beacon":"bam.nr-data.net","licenseKey":"NRJS-09e243d8a531035d2ee","applicationID":"813503022","transactionName":"ZlMEbUAEVhJYAE1YDV8ZM0tbSl4ASE1JWRI=","queueTime":0,"applicationTime":0,"atts":"ShQHGwgeRRw=","errorBeacon":"bam.nr-data.net","agent":""}</script></body> </html> <!-- FILE ARCHIVED ON 19:32:54 Apr 21, 2021 AND RETRIEVED FROM THE INTERNET ARCHIVE ON 02:54:01 Dec 03, 2024. JAVASCRIPT APPENDED BY WAYBACK MACHINE, COPYRIGHT INTERNET ARCHIVE. ALL OTHER CONTENT MAY ALSO BE PROTECTED BY COPYRIGHT (17 U.S.C. SECTION 108(a)(3)). --> <!-- playback timings (ms): captures_list: 0.535 exclusion.robots: 0.025 exclusion.robots.policy: 0.016 esindex: 0.011 cdx.remote: 6.282 LoadShardBlock: 129.882 (3) PetaboxLoader3.datanode: 87.778 (4) PetaboxLoader3.resolve: 137.852 (2) load_resource: 145.605 -->

Pages: 1 2 3 4 5 6 7 8 9 10