Data publication consensus and controversies

Data publication consensus and controversies | F1000Research "use strict";function _typeof(t){return(_typeof="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(t){return typeof t}:function(t){return t&&"function"==typeof Symbol&&t.constructor===Symbol&&t!==Symbol.prototype?"symbol":typeof t})(t)}!function(){var t=function(){var t,e,o=[],n=window,r=n;for(;r;){try{if(r.frames.__tcfapiLocator){t=r;break}}catch(t){}if(r===n.top)break;r=r.parent}t||(!function t(){var e=n.document,o=!!n.frames.__tcfapiLocator;if(!o)if(e.body){var r=e.createElement("iframe");r.style.cssText="display:none",r.name="__tcfapiLocator",e.body.appendChild(r)}else setTimeout(t,5);return!o}(),n.__tcfapi=function(){for(var t=arguments.length,n=new Array(t),r=0;r 3&&2===parseInt(n[1],10)&&"boolean"==typeof n[3]&&(e=n[3],"function"==typeof n[2]&&n[2]("set",!0)):"ping"===n[0]?"function"==typeof n[2]&&n[2]({gdprApplies:e,cmpLoaded:!1,cmpStatus:"stub"}):o.push(n)},n.addEventListener("message",(function(t){var e="string"==typeof t.data,o={};if(e)try{o=JSON.parse(t.data)}catch(t){}else o=t.data;var n="object"===_typeof(o)&&null!==o?o.__tcfapiCall:null;n&&window.__tcfapi(n.command,n.version,(function(o,r){var a={__tcfapiReturn:{returnValue:o,success:r,callId:n.callId}};t&&t.source&&t.source.postMessage&&t.source.postMessage(e?JSON.stringify(a):a,"*")}),n.parameter)}),!1))};"undefined"!=typeof module?module.exports=t:t()}(); dataLayer = dataLayer || []; // Standard GTM initialization - Google Consent Mode handles consent automatically (function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl+ '>m_auth=hzk0Vc3qFsQYhCrIoHz68A>m_preview=env-1>m_cookies_win=x';f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-MWFK8L5J'); ;window.NREUM||(NREUM={});NREUM.init={distributed_tracing:{enabled:true},privacy:{cookies_enabled:true},ajax:{deny_list:["bam.nr-data.net"]}}; ;NREUM.loader_config={accountID:"438030",trustKey:"438030",agentID:"772317073",licenseKey:"97f8f67f26",applicationID:"772317073"} ;NREUM.info={beacon:"bam.nr-data.net",errorBeacon:"bam.nr-data.net",licenseKey:"97f8f67f26",applicationID:"772317073",sa:1} ;/*! For license information please see nr-loader-spa-1.236.0.min.js.LICENSE.txt */ (()=>{"use strict";var e,t,r={5763:(e,t,r)=>{r.d(t,{P_:()=>l,Mt:()=>g,C5:()=>s,DL:()=>v,OP:()=>T,lF:()=>D,Yu:()=>y,Dg:()=>h,CX:()=>c,GE:()=>b,sU:()=>_});var n=r(8632),i=r(9567);const o={beacon:n.ce.beacon,errorBeacon:n.ce.errorBeacon,licenseKey:void 0,applicationID:void 0,sa:void 0,queueTime:void 0,applicationTime:void 0,ttGuid:void 0,user:void 0,account:void 0,product:void 0,extra:void 0,jsAttributes:{},userAttributes:void 0,atts:void 0,transactionName:void 0,tNamePlain:void 0},a={};function s(e){if(!e)throw new Error("All info objects require an agent identifier!");if(!a[e])throw new Error("Info for ".concat(e," was never set"));return a[e]}function c(e,t){if(!e)throw new Error("All info objects require an agent identifier!");a[e]=(0,i.D)(t,o),(0,n.Qy)(e,a[e],"info")}var u=r(7056);const d=()=>{const e={blockSelector:"[data-nr-block]",maskInputOptions:{password:!0}};return{allow_bfcache:!0,privacy:{cookies_enabled:!0},ajax:{deny_list:void 0,enabled:!0,harvestTimeSeconds:10},distributed_tracing:{enabled:void 0,exclude_newrelic_header:void 0,cors_use_newrelic_header:void 0,cors_use_tracecontext_headers:void 0,allowed_origins:void 0},session:{domain:void 0,expiresMs:u.oD,inactiveMs:u.Hb},ssl:void 0,obfuscate:void 0,jserrors:{enabled:!0,harvestTimeSeconds:10},metrics:{enabled:!0},page_action:{enabled:!0,harvestTimeSeconds:30},page_view_event:{enabled:!0},page_view_timing:{enabled:!0,harvestTimeSeconds:30,long_task:!1},session_trace:{enabled:!0,harvestTimeSeconds:10},harvest:{tooManyRequestsDelay:60},session_replay:{enabled:!1,harvestTimeSeconds:60,sampleRate:.1,errorSampleRate:.1,maskTextSelector:"*",maskAllInputs:!0,get blockClass(){return"nr-block"},get ignoreClass(){return"nr-ignore"},get maskTextClass(){return"nr-mask"},get blockSelector(){return e.blockSelector},set blockSelector(t){e.blockSelector+=",".concat(t)},get maskInputOptions(){return e.maskInputOptions},set maskInputOptions(t){e.maskInputOptions={...t,password:!0}}},spa:{enabled:!0,harvestTimeSeconds:10}}},f={};function l(e){if(!e)throw new Error("All configuration objects require an agent identifier!");if(!f[e])throw new Error("Configuration for ".concat(e," was never set"));return f[e]}function h(e,t){if(!e)throw new Error("All configuration objects require an agent identifier!");f[e]=(0,i.D)(t,d()),(0,n.Qy)(e,f[e],"config")}function g(e,t){if(!e)throw new Error("All configuration objects require an agent identifier!");var r=l(e);if(r){for(var n=t.split("."),i=0;i {r.d(t,{D:()=>i});var n=r(50);function i(e,t){try{if(!e||"object"!=typeof e)return(0,n.Z)("Setting a Configurable requires an object as input");if(!t||"object"!=typeof t)return(0,n.Z)("Setting a Configurable requires a model to set its initial properties");const r=Object.create(Object.getPrototypeOf(t),Object.getOwnPropertyDescriptors(t)),o=0===Object.keys(r).length?e:r;for(let a in o)if(void 0!==e[a])try{"object"==typeof e[a]&&"object"==typeof t[a]?r[a]=i(e[a],t[a]):r[a]=e[a]}catch(e){(0,n.Z)("An error occurred while setting a property of a Configurable",e)}return r}catch(e){(0,n.Z)("An error occured while setting a Configurable",e)}}},6818:(e,t,r)=>{r.d(t,{Re:()=>i,gF:()=>o,q4:()=>n});const n="1.236.0",i="PROD",o="CDN"},385:(e,t,r)=>{r.d(t,{FN:()=>a,IF:()=>u,Nk:()=>f,Tt:()=>s,_A:()=>o,il:()=>n,pL:()=>c,v6:()=>i,w1:()=>d});const n="undefined"!=typeof window&&!!window.document,i="undefined"!=typeof WorkerGlobalScope&&("undefined"!=typeof self&&self instanceof WorkerGlobalScope&&self.navigator instanceof WorkerNavigator||"undefined"!=typeof globalThis&&globalThis instanceof WorkerGlobalScope&&globalThis.navigator instanceof WorkerNavigator),o=n?window:"undefined"!=typeof WorkerGlobalScope&&("undefined"!=typeof self&&self instanceof WorkerGlobalScope&&self||"undefined"!=typeof globalThis&&globalThis instanceof WorkerGlobalScope&&globalThis),a=""+o?.location,s=/iPad|iPhone|iPod/.test(navigator.userAgent),c=s&&"undefined"==typeof SharedWorker,u=(()=>{const e=navigator.userAgent.match(/Firefox[/\s](\d+\.\d+)/);return Array.isArray(e)&&e.length>=2?+e[1]:0})(),d=Boolean(n&&window.document.documentMode),f=!!navigator.sendBeacon},1117:(e,t,r)=>{r.d(t,{w:()=>o});var n=r(50);const i={agentIdentifier:"",ee:void 0};class o{constructor(e){try{if("object"!=typeof e)return(0,n.Z)("shared context requires an object as input");this.sharedContext={},Object.assign(this.sharedContext,i),Object.entries(e).forEach((e=>{let[t,r]=e;Object.keys(i).includes(t)&&(this.sharedContext[t]=r)}))}catch(e){(0,n.Z)("An error occured while setting SharedContext",e)}}}},8e3:(e,t,r)=>{r.d(t,{L:()=>d,R:()=>c});var n=r(2177),i=r(1284),o=r(4322),a=r(3325);const s={};function c(e,t){const r={staged:!1,priority:a.p[t]||0};u(e),s[e].get(t)||s[e].set(t,r)}function u(e){e&&(s[e]||(s[e]=new Map))}function d(){let e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:"",t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:"feature";if(u(e),!e||!s[e].get(t))return a(t);s[e].get(t).staged=!0;const r=[...s[e]];function a(t){const r=e?n.ee.get(e):n.ee,a=o.X.handlers;if(r.backlog&&a){var s=r.backlog[t],c=a[t];if(c){for(var u=0;s&&u {let[t,r]=e;return r.staged}))&&(r.sort(((e,t)=>e[1].priority-t[1].priority)),r.forEach((e=>{let[t]=e;a(t)})))}function f(e,t){var r=e[1];(0,i.D)(t[r],(function(t,r){var n=e[0];if(r[0]===n){var i=r[1],o=e[3],a=e[2];i.apply(o,a)}}))}},2177:(e,t,r)=>{r.d(t,{c:()=>f,ee:()=>u});var n=r(8632),i=r(2210),o=r(1284),a=r(5763),s="nr@context";let c=(0,n.fP)();var u;function d(){}function f(e){return(0,i.X)(e,s,l)}function l(){return new d}function h(){u.aborted=!0,u.backlog={}}c.ee?u=c.ee:(u=function e(t,r){var n={},c={},f={},g=!1;try{g=16===r.length&&(0,a.OP)(r).isolatedBacklog}catch(e){}var p={on:b,addEventListener:b,removeEventListener:y,emit:v,get:x,listeners:w,context:m,buffer:A,abort:h,aborted:!1,isBuffering:E,debugId:r,backlog:g?{}:t&&"object"==typeof t.backlog?t.backlog:{}};return p;function m(e){return e&&e instanceof d?e:e?(0,i.X)(e,s,l):l()}function v(e,r,n,i,o){if(!1!==o&&(o=!0),!u.aborted||i){t&&o&&t.emit(e,r,n);for(var a=m(n),s=w(e),d=s.length,f=0;fn,p:()=>i});var n=r(2177).ee.get("handle");function i(e,t,r,i,o){o?(o.buffer([e],i),o.emit(e,t,r)):(n.buffer([e],i),n.emit(e,t,r))}},4322:(e,t,r)=>{r.d(t,{X:()=>o});var n=r(5546);o.on=a;var i=o.handlers={};function o(e,t,r,o){a(o||n.E,i,e,t,r)}function a(e,t,r,i,o){o||(o="feature"),e||(e=n.E);var a=t[o]=t[o]||{};(a[r]=a[r]||[]).push([e,i])}},3239:(e,t,r)=>{r.d(t,{bP:()=>s,iz:()=>c,m$:()=>a});var n=r(385);let i=!1,o=!1;try{const e={get passive(){return i=!0,!1},get signal(){return o=!0,!1}};n._A.addEventListener("test",null,e),n._A.removeEventListener("test",null,e)}catch(e){}function a(e,t){return i||o?{capture:!!e,passive:i,signal:t}:!!e}function s(e,t){let r=arguments.length>2&&void 0!==arguments[2]&&arguments[2],n=arguments.length>3?arguments[3]:void 0;window.addEventListener(e,t,a(r,n))}function c(e,t){let r=arguments.length>2&&void 0!==arguments[2]&&arguments[2],n=arguments.length>3?arguments[3]:void 0;document.addEventListener(e,t,a(r,n))}},4402:(e,t,r)=>{r.d(t,{Ht:()=>u,M:()=>c,Rl:()=>a,ky:()=>s});var n=r(385);const i="xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx";function o(e,t){return e?15&e[t]:16*Math.random()|0}function a(){const e=n._A?.crypto||n._A?.msCrypto;let t,r=0;return e&&e.getRandomValues&&(t=e.getRandomValues(new Uint8Array(31))),i.split("").map((e=>"x"===e?o(t,++r).toString(16):"y"===e?(3&o()|8).toString(16):e)).join("")}function s(e){const t=n._A?.crypto||n._A?.msCrypto;let r,i=0;t&&t.getRandomValues&&(r=t.getRandomValues(new Uint8Array(31)));const a=[];for(var s=0;s {r.d(t,{Bq:()=>n,Hb:()=>o,oD:()=>i});const n="NRBA",i=144e5,o=18e5},7894:(e,t,r)=>{function n(){return Math.round(performance.now())}r.d(t,{z:()=>n})},7243:(e,t,r)=>{r.d(t,{e:()=>o});var n=r(385),i={};function o(e){if(e in i)return i[e];if(0===(e||"").indexOf("data:"))return{protocol:"data"};let t;var r=n._A?.location,o={};if(n.il)t=document.createElement("a"),t.href=e;else try{t=new URL(e,r.href)}catch(e){return o}o.port=t.port;var a=t.href.split("://");!o.port&&a[1]&&(o.port=a[1].split("/")[0].split("@").pop().split(":")[1]),o.port&&"0"!==o.port||(o.port="https"===a[0]?"443":"80"),o.hostname=t.hostname||r.hostname,o.pathname=t.pathname,o.protocol=a[0],"/"!==o.pathname.charAt(0)&&(o.pathname="/"+o.pathname);var s=!t.protocol||":"===t.protocol||t.protocol===r.protocol,c=t.hostname===r.hostname&&t.port===r.port;return o.sameOrigin=s&&(!t.hostname||c),"/"===o.pathname&&(i[e]=o),o}},50:(e,t,r)=>{function n(e,t){"function"==typeof console.warn&&(console.warn("New Relic: ".concat(e)),t&&console.warn(t))}r.d(t,{Z:()=>n})},2587:(e,t,r)=>{r.d(t,{N:()=>c,T:()=>u});var n=r(2177),i=r(5546),o=r(8e3),a=r(3325);const s={stn:[a.D.sessionTrace],err:[a.D.jserrors,a.D.metrics],ins:[a.D.pageAction],spa:[a.D.spa],sr:[a.D.sessionReplay,a.D.sessionTrace]};function c(e,t){const r=n.ee.get(t);e&&"object"==typeof e&&(Object.entries(e).forEach((e=>{let[t,n]=e;void 0===u[t]&&(s[t]?s[t].forEach((e=>{n?(0,i.p)("feat-"+t,[],void 0,e,r):(0,i.p)("block-"+t,[],void 0,e,r),(0,i.p)("rumresp-"+t,[Boolean(n)],void 0,e,r)})):n&&(0,i.p)("feat-"+t,[],void 0,void 0,r),u[t]=Boolean(n))})),Object.keys(s).forEach((e=>{void 0===u[e]&&(s[e]?.forEach((t=>(0,i.p)("rumresp-"+e,[!1],void 0,t,r))),u[e]=!1)})),(0,o.L)(t,a.D.pageViewEvent))}const u={}},2210:(e,t,r)=>{r.d(t,{X:()=>i});var n=Object.prototype.hasOwnProperty;function i(e,t,r){if(n.call(e,t))return e[t];var i=r();if(Object.defineProperty&&Object.keys)try{return Object.defineProperty(e,t,{value:i,writable:!0,enumerable:!1}),i}catch(e){}return e[t]=i,i}},1284:(e,t,r)=>{r.d(t,{D:()=>n});const n=(e,t)=>Object.entries(e||{}).map((e=>{let[r,n]=e;return t(r,n)}))},4351:(e,t,r)=>{r.d(t,{P:()=>o});var n=r(2177);const i=()=>{const e=new WeakSet;return(t,r)=>{if("object"==typeof r&&null!==r){if(e.has(r))return;e.add(r)}return r}};function o(e){try{return JSON.stringify(e,i())}catch(e){try{n.ee.emit("internal-error",[e])}catch(e){}}}},3960:(e,t,r)=>{r.d(t,{K:()=>a,b:()=>o});var n=r(3239);function i(){return"undefined"==typeof document||"complete"===document.readyState}function o(e,t){if(i())return e();(0,n.bP)("load",e,t)}function a(e){if(i())return e();(0,n.iz)("DOMContentLoaded",e)}},8632:(e,t,r)=>{r.d(t,{EZ:()=>u,Qy:()=>c,ce:()=>o,fP:()=>a,gG:()=>d,mF:()=>s});var n=r(7894),i=r(385);const o={beacon:"bam.nr-data.net",errorBeacon:"bam.nr-data.net"};function a(){return i._A.NREUM||(i._A.NREUM={}),void 0===i._A.newrelic&&(i._A.newrelic=i._A.NREUM),i._A.NREUM}function s(){let e=a();return e.o||(e.o={ST:i._A.setTimeout,SI:i._A.setImmediate,CT:i._A.clearTimeout,XHR:i._A.XMLHttpRequest,REQ:i._A.Request,EV:i._A.Event,PR:i._A.Promise,MO:i._A.MutationObserver,FETCH:i._A.fetch}),e}function c(e,t,r){let i=a();const o=i.initializedAgents||{},s=o[e]||{};return Object.keys(s).length||(s.initializedAt={ms:(0,n.z)(),date:new Date}),i.initializedAgents={...o,[e]:{...s,[r]:t}},i}function u(e,t){a()[e]=t}function d(){return function(){let e=a();const t=e.info||{};e.info={beacon:o.beacon,errorBeacon:o.errorBeacon,...t}}(),function(){let e=a();const t=e.init||{};e.init={...t}}(),s(),function(){let e=a();const t=e.loader_config||{};e.loader_config={...t}}(),a()}},7956:(e,t,r)=>{r.d(t,{N:()=>i});var n=r(3239);function i(e){let t=arguments.length>1&&void 0!==arguments[1]&&arguments[1],r=arguments.length>2?arguments[2]:void 0,i=arguments.length>3?arguments[3]:void 0;return void(0,n.iz)("visibilitychange",(function(){if(t)return void("hidden"==document.visibilityState&&e());e(document.visibilityState)}),r,i)}},1214:(e,t,r)=>{r.d(t,{em:()=>v,u5:()=>N,QU:()=>S,_L:()=>I,Gm:()=>L,Lg:()=>M,gy:()=>U,BV:()=>Q,Kf:()=>ee});var n=r(2177);const i="nr@original";var o=Object.prototype.hasOwnProperty,a=!1;function s(e,t){return e||(e=n.ee),r.inPlace=function(e,t,n,i,o){n||(n="");var a,s,c,u="-"===n.charAt(0);for(c=0;c 2?n-2:0),o=2;o {r(A[T],e,w),r(E[T],e,w)})),r(l._A,"fetch",y),t.on(y+"end",(function(e,r){var n=this;if(r){var i=r.headers.get("content-length");null!==i&&(n.rxSize=i),t.emit(y+"done",[null,r],n)}else t.emit(y+"done",[e],n)})),t}const O={},j=["pushState","replaceState"];function S(e){const t=function(e){return(e||n.ee).get("history")}(e);return!l.il||O[t.debugId]++||(O[t.debugId]=1,s(t).inPlace(window.history,j,"-")),t}var P=r(3239);const C={},R=["appendChild","insertBefore","replaceChild"];function I(e){const t=function(e){return(e||n.ee).get("jsonp")}(e);if(!l.il||C[t.debugId])return t;C[t.debugId]=!0;var r=s(t),i=/[?&](?:callback|cb)=([^&#]+)/,o=/(.*)\.([^.]+)/,a=/^(\w+)(\.|$)(.*)$/;function c(e,t){var r=e.match(a),n=r[1],i=r[3];return i?c(i,t[n]):t[n]}return r.inPlace(Node.prototype,R,"dom-"),t.on("dom-start",(function(e){!function(e){if(!e||"string"!=typeof e.nodeName||"script"!==e.nodeName.toLowerCase())return;if("function"!=typeof e.addEventListener)return;var n=(a=e.src,s=a.match(i),s?s[1]:null);var a,s;if(!n)return;var u=function(e){var t=e.match(o);if(t&&t.length>=3)return{key:t[2],parent:c(t[1],window)};return{key:e,parent:window}}(n);if("function"!=typeof u.parent[u.key])return;var d={};function f(){t.emit("jsonp-end",[],d),e.removeEventListener("load",f,(0,P.m$)(!1)),e.removeEventListener("error",l,(0,P.m$)(!1))}function l(){t.emit("jsonp-error",[],d),t.emit("jsonp-end",[],d),e.removeEventListener("load",f,(0,P.m$)(!1)),e.removeEventListener("error",l,(0,P.m$)(!1))}r.inPlace(u.parent,[u.key],"cb-",d),e.addEventListener("load",f,(0,P.m$)(!1)),e.addEventListener("error",l,(0,P.m$)(!1)),t.emit("new-jsonp",[e.src],d)}(e[0])})),t}var k=r(5763);const H={};function L(e){const t=function(e){return(e||n.ee).get("mutation")}(e);if(!l.il||H[t.debugId])return t;H[t.debugId]=!0;var r=s(t),i=k.Yu.MO;return i&&(window.MutationObserver=function(e){return this instanceof i?new i(r(e,"fn-")):i.apply(this,arguments)},MutationObserver.prototype=i.prototype),t}const z={};function M(e){const t=function(e){return(e||n.ee).get("promise")}(e);if(z[t.debugId])return t;z[t.debugId]=!0;var r=n.c,o=s(t),a=k.Yu.PR;return a&&function(){function e(r){var n=t.context(),i=o(r,"executor-",n,null,!1);const s=Reflect.construct(a,[i],e);return t.context(s).getCtx=function(){return n},s}l._A.Promise=e,Object.defineProperty(e,"name",{value:"Promise"}),e.toString=function(){return a.toString()},Object.setPrototypeOf(e,a),["all","race"].forEach((function(r){const n=a[r];e[r]=function(e){let i=!1;[...e||[]].forEach((e=>{this.resolve(e).then(a("all"===r),a(!1))}));const o=n.apply(this,arguments);return o;function a(e){return function(){t.emit("propagate",[null,!i],o,!1,!1),i=i||!e}}}})),["resolve","reject"].forEach((function(r){const n=a[r];e[r]=function(e){const r=n.apply(this,arguments);return e!==r&&t.emit("propagate",[e,!0],r,!1,!1),r}})),e.prototype=a.prototype;const n=a.prototype.then;a.prototype.then=function(){var e=this,i=r(e);i.promise=e;for(var a=arguments.length,s=new Array(a),c=0;c e())),t};function m(e,t){i.inPlace(t,["onreadystatechange"],"fn-",E)}function b(){var e=this,t=r.context(e);e.readyState>3&&!t.resolved&&(t.resolved=!0,r.emit("xhr-resolved",[],e)),i.inPlace(e,f,"fn-",E)}if(function(e,t){for(var r in e)t[r]=e[r]}(o,p),p.prototype=o.prototype,i.inPlace(p.prototype,J,"-xhr-",E),r.on("send-xhr-start",(function(e,t){m(e,t),function(e){h.push(e),a&&(y?y.then(A):u?u(A):(w=-w,x.data=w))}(t)})),r.on("open-xhr-start",m),a){var y=c&&c.resolve();if(!u&&!c){var w=1,x=document.createTextNode(w);new a(A).observe(x,{characterData:!0})}}else t.on("fn-end",(function(e){e[0]&&e[0].type===d||A()}));function A(){for(var e=0;e {r.d(t,{t:()=>n});const n=r(3325).D.ajax},6660:(e,t,r)=>{r.d(t,{A:()=>i,t:()=>n});const n=r(3325).D.jserrors,i="nr@seenError"},3081:(e,t,r)=>{r.d(t,{gF:()=>o,mY:()=>i,t9:()=>n,vz:()=>s,xS:()=>a});const n=r(3325).D.metrics,i="sm",o="cm",a="storeSupportabilityMetrics",s="storeEventMetrics"},4649:(e,t,r)=>{r.d(t,{t:()=>n});const n=r(3325).D.pageAction},7633:(e,t,r)=>{r.d(t,{Dz:()=>i,OJ:()=>a,qw:()=>o,t9:()=>n});const n=r(3325).D.pageViewEvent,i="firstbyte",o="domcontent",a="windowload"},9251:(e,t,r)=>{r.d(t,{t:()=>n});const n=r(3325).D.pageViewTiming},3614:(e,t,r)=>{r.d(t,{BST_RESOURCE:()=>i,END:()=>s,FEATURE_NAME:()=>n,FN_END:()=>u,FN_START:()=>c,PUSH_STATE:()=>d,RESOURCE:()=>o,START:()=>a});const n=r(3325).D.sessionTrace,i="bstResource",o="resource",a="-start",s="-end",c="fn"+a,u="fn"+s,d="pushState"},7836:(e,t,r)=>{r.d(t,{BODY:()=>A,CB_END:()=>E,CB_START:()=>u,END:()=>x,FEATURE_NAME:()=>i,FETCH:()=>_,FETCH_BODY:()=>v,FETCH_DONE:()=>m,FETCH_START:()=>p,FN_END:()=>c,FN_START:()=>s,INTERACTION:()=>l,INTERACTION_API:()=>d,INTERACTION_EVENTS:()=>o,JSONP_END:()=>b,JSONP_NODE:()=>g,JS_TIME:()=>T,MAX_TIMER_BUDGET:()=>a,REMAINING:()=>f,SPA_NODE:()=>h,START:()=>w,originalSetTimeout:()=>y});var n=r(5763);const i=r(3325).D.spa,o=["click","submit","keypress","keydown","keyup","change"],a=999,s="fn-start",c="fn-end",u="cb-start",d="api-ixn-",f="remaining",l="interaction",h="spaNode",g="jsonpNode",p="fetch-start",m="fetch-done",v="fetch-body-",b="jsonp-end",y=n.Yu.ST,w="-start",x="-end",A="-body",E="cb"+x,T="jsTime",_="fetch"},5938:(e,t,r)=>{r.d(t,{W:()=>o});var n=r(5763),i=r(2177);class o{constructor(e,t,r){this.agentIdentifier=e,this.aggregator=t,this.ee=i.ee.get(e,(0,n.OP)(this.agentIdentifier).isolatedBacklog),this.featureName=r,this.blocked=!1}}},9144:(e,t,r)=>{r.d(t,{j:()=>m});var n=r(3325),i=r(5763),o=r(5546),a=r(2177),s=r(7894),c=r(8e3),u=r(3960),d=r(385),f=r(50),l=r(3081),h=r(8632);function g(){const e=(0,h.gG)();["setErrorHandler","finished","addToTrace","inlineHit","addRelease","addPageAction","setCurrentRouteName","setPageViewName","setCustomAttribute","interaction","noticeError","setUserId"].forEach((t=>{e[t]=function(){for(var r=arguments.length,n=new Array(r),i=0;i 1?r-1:0),i=1;i {e.exposed&&e.api[t]&&o.push(e.api[t](...n))})),o.length>1?o:o[0]}(t,...n)}}))}var p=r(2587);function m(e){let t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:{},m=arguments.length>2?arguments[2]:void 0,v=arguments.length>3?arguments[3]:void 0,{init:b,info:y,loader_config:w,runtime:x={loaderType:m},exposed:A=!0}=t;const E=(0,h.gG)();y||(b=E.init,y=E.info,w=E.loader_config),(0,i.Dg)(e,b||{}),(0,i.GE)(e,w||{}),(0,i.sU)(e,x),y.jsAttributes??={},d.v6&&(y.jsAttributes.isWorker=!0),(0,i.CX)(e,y),g();const T=function(e,t){t||(0,c.R)(e,"api");const h={};var g=a.ee.get(e),p=g.get("tracer"),m="api-",v=m+"ixn-";function b(t,r,n,o){const a=(0,i.C5)(e);return null===r?delete a.jsAttributes[t]:(0,i.CX)(e,{...a,jsAttributes:{...a.jsAttributes,[t]:r}}),x(m,n,!0,o||null===r?"session":void 0)(t,r)}function y(){}["setErrorHandler","finished","addToTrace","inlineHit","addRelease"].forEach((e=>h[e]=x(m,e,!0,"api"))),h.addPageAction=x(m,"addPageAction",!0,n.D.pageAction),h.setCurrentRouteName=x(m,"routeName",!0,n.D.spa),h.setPageViewName=function(t,r){if("string"==typeof t)return"/"!==t.charAt(0)&&(t="/"+t),(0,i.OP)(e).customTransaction=(r||"http://custom.transaction")+t,x(m,"setPageViewName",!0)()},h.setCustomAttribute=function(e,t){let r=arguments.length>2&&void 0!==arguments[2]&&arguments[2];if("string"==typeof e){if(["string","number"].includes(typeof t)||null===t)return b(e,t,"setCustomAttribute",r);(0,f.Z)("Failed to execute setCustomAttribute.\nNon-null value must be a string or number type, but a type of was provided."))}else(0,f.Z)("Failed to execute setCustomAttribute.\nName must be a string type, but a type of was provided."))},h.setUserId=function(e){if("string"==typeof e||null===e)return b("enduser.id",e,"setUserId",!0);(0,f.Z)("Failed to execute setUserId.\nNon-null value must be a string type, but a type of was provided."))},h.interaction=function(){return(new y).get()};var w=y.prototype={createTracer:function(e,t){var r={},i=this,a="function"==typeof t;return(0,o.p)(v+"tracer",[(0,s.z)(),e,r],i,n.D.spa,g),function(){if(p.emit((a?"":"no-")+"fn-start",[(0,s.z)(),i,a],r),a)try{return t.apply(this,arguments)}catch(e){throw p.emit("fn-err",[arguments,this,"string"==typeof e?new Error(e):e],r),e}finally{p.emit("fn-end",[(0,s.z)()],r)}}}};function x(e,t,r,i){return function(){return(0,o.p)(l.xS,["API/"+t+"/called"],void 0,n.D.metrics,g),i&&(0,o.p)(e+t,[(0,s.z)(),...arguments],r?null:this,i,g),r?void 0:this}}function A(){r.e(439).then(r.bind(r,7438)).then((t=>{let{setAPI:r}=t;r(e),(0,c.L)(e,"api")})).catch((()=>(0,f.Z)("Downloading runtime APIs failed...")))}return["actionText","setName","setAttribute","save","ignore","onEnd","getContext","end","get"].forEach((e=>{w[e]=x(v,e,void 0,n.D.spa)})),h.noticeError=function(e,t){"string"==typeof e&&(e=new Error(e)),(0,o.p)(l.xS,["API/noticeError/called"],void 0,n.D.metrics,g),(0,o.p)("err",[e,(0,s.z)(),!1,t],void 0,n.D.jserrors,g)},d.il?(0,u.b)((()=>A()),!0):A(),h}(e,v);return(0,h.Qy)(e,T,"api"),(0,h.Qy)(e,A,"exposed"),(0,h.EZ)("activatedFeatures",p.T),T}},3325:(e,t,r)=>{r.d(t,{D:()=>n,p:()=>i});const n={ajax:"ajax",jserrors:"jserrors",metrics:"metrics",pageAction:"page_action",pageViewEvent:"page_view_event",pageViewTiming:"page_view_timing",sessionReplay:"session_replay",sessionTrace:"session_trace",spa:"spa"},i={[n.pageViewEvent]:1,[n.pageViewTiming]:2,[n.metrics]:3,[n.jserrors]:4,[n.ajax]:5,[n.sessionTrace]:6,[n.pageAction]:7,[n.spa]:8,[n.sessionReplay]:9}}},n={};function i(e){var t=n[e];if(void 0!==t)return t.exports;var o=n[e]={exports:{}};return r[e](o,o.exports,i),o.exports}i.m=r,i.d=(e,t)=>{for(var r in t)i.o(t,r)&&!i.o(e,r)&&Object.defineProperty(e,r,{enumerable:!0,get:t[r]})},i.f={},i.e=e=>Promise.all(Object.keys(i.f).reduce(((t,r)=>(i.f[r](e,t),t)),[])),i.u=e=>(({78:"page_action-aggregate",147:"metrics-aggregate",242:"session-manager",317:"jserrors-aggregate",348:"page_view_timing-aggregate",412:"lazy-feature-loader",439:"async-api",538:"recorder",590:"session_replay-aggregate",675:"compressor",733:"session_trace-aggregate",786:"page_view_event-aggregate",873:"spa-aggregate",898:"ajax-aggregate"}[e]||e)+"."+{78:"ac76d497",147:"3dc53903",148:"1a20d5fe",242:"2a64278a",317:"49e41428",348:"bd6de33a",412:"2f55ce66",439:"30bd804e",538:"1b18459f",590:"cf0efb30",675:"ae9f91a8",733:"83105561",786:"06482edd",860:"03a8b7a5",873:"e6b09d52",898:"998ef92b"}[e]+"-1.236.0.min.js"),i.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),e={},t="NRBA:",i.l=(r,n,o,a)=>{if(e[r])e[r].push(n);else{var s,c;if(void 0!==o)for(var u=document.getElementsByTagName("script"),d=0;d {s.onerror=s.onload=null,clearTimeout(h);var i=e[r];if(delete e[r],s.parentNode&&s.parentNode.removeChild(s),i&&i.forEach((e=>e(n))),t)return t(n)},h=setTimeout(l.bind(null,void 0,{type:"timeout",target:s}),12e4);s.onerror=l.bind(null,s.onerror),s.onload=l.bind(null,s.onload),c&&document.head.appendChild(s)}},i.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},i.j=364,i.p="https://js-agent.newrelic.com/",(()=>{var e={364:0,953:0};i.f.j=(t,r)=>{var n=i.o(e,t)?e[t]:void 0;if(0!==n)if(n)r.push(n[2]);else{var o=new Promise(((r,i)=>n=e[t]=[r,i]));r.push(n[2]=o);var a=i.p+i.u(t),s=new Error;i.l(a,(r=>{if(i.o(e,t)&&(0!==(n=e[t])&&(e[t]=void 0),n)){var o=r&&("load"===r.type?"missing":r.type),a=r&&r.target&&r.target.src;s.message="Loading chunk "+t+" failed.\n("+o+": "+a+")",s.name="ChunkLoadError",s.type=o,s.request=a,n[1](s)}}),"chunk-"+t,t)}};var t=(t,r)=>{var n,o,[a,s,c]=r,u=0;if(a.some((t=>0!==e[t]))){for(n in s)i.o(s,n)&&(i.m[n]=s[n]);if(c)c(i)}for(t&&t(r);u {i.r(o);var e=i(3325),t=i(5763);const r=Object.values(e.D);function n(e){const n={};return r.forEach((r=>{n[r]=function(e,r){return!1!==(0,t.Mt)(r,"".concat(e,".enabled"))}(r,e)})),n}var a=i(9144);var s=i(5546),c=i(385),u=i(8e3),d=i(5938),f=i(3960),l=i(50);class h extends d.W{constructor(e,t,r){let n=!(arguments.length>3&&void 0!==arguments[3])||arguments[3];super(e,t,r),this.auto=n,this.abortHandler,this.featAggregate,this.onAggregateImported,n&&(0,u.R)(e,r)}importAggregator(){let e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:{};if(this.featAggregate||!this.auto)return;const r=c.il&&!0===(0,t.Mt)(this.agentIdentifier,"privacy.cookies_enabled");let n;this.onAggregateImported=new Promise((e=>{n=e}));const o=async()=>{let t;try{if(r){const{setupAgentSession:e}=await Promise.all([i.e(860),i.e(242)]).then(i.bind(i,3228));t=e(this.agentIdentifier)}}catch(e){(0,l.Z)("A problem occurred when starting up session manager. This page will not start or extend any session.",e)}try{if(!this.shouldImportAgg(this.featureName,t))return void(0,u.L)(this.agentIdentifier,this.featureName);const{lazyFeatureLoader:r}=await i.e(412).then(i.bind(i,8582)),{Aggregate:o}=await r(this.featureName,"aggregate");this.featAggregate=new o(this.agentIdentifier,this.aggregator,e),n(!0)}catch(e){(0,l.Z)("Downloading and initializing ".concat(this.featureName," failed..."),e),this.abortHandler?.(),n(!1)}};c.il?(0,f.b)((()=>o()),!0):o()}shouldImportAgg(r,n){return r!==e.D.sessionReplay||!1!==(0,t.Mt)(this.agentIdentifier,"session_trace.enabled")&&(!!n?.isNew||!!n?.state.sessionReplay)}}var g=i(7633),p=i(7894);class m extends h{static featureName=g.t9;constructor(r,n){let i=!(arguments.length>2&&void 0!==arguments[2])||arguments[2];if(super(r,n,g.t9,i),("undefined"==typeof PerformanceNavigationTiming||c.Tt)&&"undefined"!=typeof PerformanceTiming){const n=(0,t.OP)(r);n[g.Dz]=Math.max(Date.now()-n.offset,0),(0,f.K)((()=>n[g.qw]=Math.max((0,p.z)()-n[g.Dz],0))),(0,f.b)((()=>{const t=(0,p.z)();n[g.OJ]=Math.max(t-n[g.Dz],0),(0,s.p)("timing",["load",t],void 0,e.D.pageViewTiming,this.ee)}))}this.importAggregator()}}var v=i(1117),b=i(1284);class y extends v.w{constructor(e){super(e),this.aggregatedData={}}store(e,t,r,n,i){var o=this.getBucket(e,t,r,i);return o.metrics=function(e,t){t||(t={count:0});return t.count+=1,(0,b.D)(e,(function(e,r){t[e]=w(r,t[e])})),t}(n,o.metrics),o}merge(e,t,r,n,i){var o=this.getBucket(e,t,n,i);if(o.metrics){var a=o.metrics;a.count+=r.count,(0,b.D)(r,(function(e,t){if("count"!==e){var n=a[e],i=r[e];i&&!i.c?a[e]=w(i.t,n):a[e]=function(e,t){if(!t)return e;t.c||(t=x(t.t));return t.min=Math.min(e.min,t.min),t.max=Math.max(e.max,t.max),t.t+=e.t,t.sos+=e.sos,t.c+=e.c,t}(i,a[e])}}))}else o.metrics=r}storeMetric(e,t,r,n){var i=this.getBucket(e,t,r);return i.stats=w(n,i.stats),i}getBucket(e,t,r,n){this.aggregatedData[e]||(this.aggregatedData[e]={});var i=this.aggregatedData[e][t];return i||(i=this.aggregatedData[e][t]={params:r||{}},n&&(i.custom=n)),i}get(e,t){return t?this.aggregatedData[e]&&this.aggregatedData[e][t]:this.aggregatedData[e]}take(e){for(var t={},r="",n=!1,i=0;i t.max&&(t.max=e),e 2&&void 0!==arguments[2])||arguments[2];super(e,r,j.t,n),c.il&&((0,t.OP)(e).initHidden=Boolean("hidden"===document.visibilityState),(0,N.N)((()=>(0,s.p)("docHidden",[(0,p.z)()],void 0,j.t,this.ee)),!0),(0,O.bP)("pagehide",(()=>(0,s.p)("winPagehide",[(0,p.z)()],void 0,j.t,this.ee))),this.importAggregator())}}var P=i(3081);class C extends h{static featureName=P.t9;constructor(e,t){let r=!(arguments.length>2&&void 0!==arguments[2])||arguments[2];super(e,t,P.t9,r),this.importAggregator()}}var R,I=i(2210),k=i(1214),H=i(2177),L={};try{R=localStorage.getItem("__nr_flags").split(","),console&&"function"==typeof console.log&&(L.console=!0,-1!==R.indexOf("dev")&&(L.dev=!0),-1!==R.indexOf("nr_dev")&&(L.nrDev=!0))}catch(e){}function z(e){try{L.console&&z(e)}catch(e){}}L.nrDev&&H.ee.on("internal-error",(function(e){z(e.stack)})),L.dev&&H.ee.on("fn-err",(function(e,t,r){z(r.stack)})),L.dev&&(z("NR AGENT IN DEVELOPMENT MODE"),z("flags: "+(0,b.D)(L,(function(e,t){return e})).join(", ")));var M=i(6660);class B extends h{static featureName=M.t;constructor(r,n){let i=!(arguments.length>2&&void 0!==arguments[2])||arguments[2];super(r,n,M.t,i),this.skipNext=0;try{this.removeOnAbort=new AbortController}catch(e){}const o=this;o.ee.on("fn-start",(function(e,t,r){o.abortHandler&&(o.skipNext+=1)})),o.ee.on("fn-err",(function(t,r,n){o.abortHandler&&!n[M.A]&&((0,I.X)(n,M.A,(function(){return!0})),this.thrown=!0,(0,s.p)("err",[n,(0,p.z)()],void 0,e.D.jserrors,o.ee))})),o.ee.on("fn-end",(function(){o.abortHandler&&!this.thrown&&o.skipNext>0&&(o.skipNext-=1)})),o.ee.on("internal-error",(function(t){(0,s.p)("ierr",[t,(0,p.z)(),!0],void 0,e.D.jserrors,o.ee)})),this.origOnerror=c._A.onerror,c._A.onerror=this.onerrorHandler.bind(this),c._A.addEventListener("unhandledrejection",(t=>{const r=function(e){let t="Unhandled Promise Rejection: ";if(e instanceof Error)try{return e.message=t+e.message,e}catch(t){return e}if(void 0===e)return new Error(t);try{return new Error(t+(0,D.P)(e))}catch(e){return new Error(t)}}(t.reason);(0,s.p)("err",[r,(0,p.z)(),!1,{unhandledPromiseRejection:1}],void 0,e.D.jserrors,this.ee)}),(0,O.m$)(!1,this.removeOnAbort?.signal)),(0,k.gy)(this.ee),(0,k.BV)(this.ee),(0,k.em)(this.ee),(0,t.OP)(r).xhrWrappable&&(0,k.Kf)(this.ee),this.abortHandler=this.#e,this.importAggregator()}#e(){this.removeOnAbort?.abort(),this.abortHandler=void 0}onerrorHandler(t,r,n,i,o){"function"==typeof this.origOnerror&&this.origOnerror(...arguments);try{this.skipNext?this.skipNext-=1:(0,s.p)("err",[o||new F(t,r,n),(0,p.z)()],void 0,e.D.jserrors,this.ee)}catch(t){try{(0,s.p)("ierr",[t,(0,p.z)(),!0],void 0,e.D.jserrors,this.ee)}catch(e){}}return!1}}function F(e,t,r){this.message=e||"Uncaught error with no additional information",this.sourceURL=t,this.line=r}let U=1;const q="nr@id";function G(e){const t=typeof e;return!e||"object"!==t&&"function"!==t?-1:e===c._A?0:(0,I.X)(e,q,(function(){return U++}))}function V(e){if("string"==typeof e&&e.length)return e.length;if("object"==typeof e){if("undefined"!=typeof ArrayBuffer&&e instanceof ArrayBuffer&&e.byteLength)return e.byteLength;if("undefined"!=typeof Blob&&e instanceof Blob&&e.size)return e.size;if(!("undefined"!=typeof FormData&&e instanceof FormData))try{return(0,D.P)(e).length}catch(e){return}}}var X=i(7243);class W{constructor(e){this.agentIdentifier=e,this.generateTracePayload=this.generateTracePayload.bind(this),this.shouldGenerateTrace=this.shouldGenerateTrace.bind(this)}generateTracePayload(e){if(!this.shouldGenerateTrace(e))return null;var r=(0,t.DL)(this.agentIdentifier);if(!r)return null;var n=(r.accountID||"").toString()||null,i=(r.agentID||"").toString()||null,o=(r.trustKey||"").toString()||null;if(!n||!i)return null;var a=(0,_.M)(),s=(0,_.Ht)(),c=Date.now(),u={spanId:a,traceId:s,timestamp:c};return(e.sameOrigin||this.isAllowedOrigin(e)&&this.useTraceContextHeadersForCors())&&(u.traceContextParentHeader=this.generateTraceContextParentHeader(a,s),u.traceContextStateHeader=this.generateTraceContextStateHeader(a,c,n,i,o)),(e.sameOrigin&&!this.excludeNewrelicHeader()||!e.sameOrigin&&this.isAllowedOrigin(e)&&this.useNewrelicHeaderForCors())&&(u.newrelicHeader=this.generateTraceHeader(a,s,c,n,i,o)),u}generateTraceContextParentHeader(e,t){return"00-"+t+"-"+e+"-01"}generateTraceContextStateHeader(e,t,r,n,i){return i+"@nr=0-1-"+r+"-"+n+"-"+e+"----"+t}generateTraceHeader(e,t,r,n,i,o){if(!("function"==typeof c._A?.btoa))return null;var a={v:[0,1],d:{ty:"Browser",ac:n,ap:i,id:e,tr:t,ti:r}};return o&&n!==o&&(a.d.tk=o),btoa((0,D.P)(a))}shouldGenerateTrace(e){return this.isDtEnabled()&&this.isAllowedOrigin(e)}isAllowedOrigin(e){var r=!1,n={};if((0,t.Mt)(this.agentIdentifier,"distributed_tracing")&&(n=(0,t.P_)(this.agentIdentifier).distributed_tracing),e.sameOrigin)r=!0;else if(n.allowed_origins instanceof Array)for(var i=0;i 2&&void 0!==arguments[2])||arguments[2];super(r,n,Z.t,i),(0,t.OP)(r).xhrWrappable&&(this.dt=new W(r),this.handler=(e,t,r,n)=>(0,s.p)(e,t,r,n,this.ee),(0,k.u5)(this.ee),(0,k.Kf)(this.ee),function(r,n,i,o){function a(e){var t=this;t.totalCbs=0,t.called=0,t.cbTime=0,t.end=E,t.ended=!1,t.xhrGuids={},t.lastSize=null,t.loadCaptureCalled=!1,t.params=this.params||{},t.metrics=this.metrics||{},e.addEventListener("load",(function(r){_(t,e)}),(0,O.m$)(!1)),c.IF||e.addEventListener("progress",(function(e){t.lastSize=e.loaded}),(0,O.m$)(!1))}function s(e){this.params={method:e[0]},T(this,e[1]),this.metrics={}}function u(e,n){var i=(0,t.DL)(r);i.xpid&&this.sameOrigin&&n.setRequestHeader("X-NewRelic-ID",i.xpid);var a=o.generateTracePayload(this.parsedOrigin);if(a){var s=!1;a.newrelicHeader&&(n.setRequestHeader("newrelic",a.newrelicHeader),s=!0),a.traceContextParentHeader&&(n.setRequestHeader("traceparent",a.traceContextParentHeader),a.traceContextStateHeader&&n.setRequestHeader("tracestate",a.traceContextStateHeader),s=!0),s&&(this.dt=a)}}function d(e,t){var r=this.metrics,i=e[0],o=this;if(r&&i){var a=V(i);a&&(r.txSize=a)}this.startTime=(0,p.z)(),this.listener=function(e){try{"abort"!==e.type||o.loadCaptureCalled||(o.params.aborted=!0),("load"!==e.type||o.called===o.totalCbs&&(o.onloadCalled||"function"!=typeof t.onload)&&"function"==typeof o.end)&&o.end(t)}catch(e){try{n.emit("internal-error",[e])}catch(e){}}};for(var s=0;s 1?e[1]=i:e.push(i)}else e[0]&&e[0].headers&&s(e[0].headers,n)&&(this.dt=n);function s(e,t){var r=!1;return t.newrelicHeader&&(e.set("newrelic",t.newrelicHeader),r=!0),t.traceContextParentHeader&&(e.set("traceparent",t.traceContextParentHeader),t.traceContextStateHeader&&e.set("tracestate",t.traceContextStateHeader),r=!0),r}}function x(e,t){this.params={},this.metrics={},this.startTime=(0,p.z)(),this.dt=t,e.length>=1&&(this.target=e[0]),e.length>=2&&(this.opts=e[1]);var r,n=this.opts||{},i=this.target;"string"==typeof i?r=i:"object"==typeof i&&i instanceof Y?r=i.url:c._A?.URL&&"object"==typeof i&&i instanceof URL&&(r=i.href),T(this,r);var o=(""+(i&&i instanceof Y&&i.method||n.method||"GET")).toUpperCase();this.params.method=o,this.txSize=V(n.body)||0}function A(t,r){var n;this.endTime=(0,p.z)(),this.params||(this.params={}),this.params.status=r?r.status:0,"string"==typeof this.rxSize&&this.rxSize.length>0&&(n=+this.rxSize);var o={txSize:this.txSize,rxSize:n,duration:(0,p.z)()-this.startTime};i("xhr",[this.params,o,this.startTime,this.endTime,"fetch"],this,e.D.ajax)}function E(t){var r=this.params,n=this.metrics;if(!this.ended){this.ended=!0;for(var o=0;o 2&&void 0!==arguments[2])||arguments[2];super(e,t,we.t,r),this.importAggregator()}}new class{constructor(e){let t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:(0,_.ky)(16);c._A?(this.agentIdentifier=t,this.sharedAggregator=new y({agentIdentifier:this.agentIdentifier}),this.features={},this.desiredFeatures=new Set(e.features||[]),this.desiredFeatures.add(m),Object.assign(this,(0,a.j)(this.agentIdentifier,e,e.loaderType||"agent")),this.start()):(0,l.Z)("Failed to initial the agent. Could not determine the runtime environment.")}get config(){return{info:(0,t.C5)(this.agentIdentifier),init:(0,t.P_)(this.agentIdentifier),loader_config:(0,t.DL)(this.agentIdentifier),runtime:(0,t.OP)(this.agentIdentifier)}}start(){const t="features";try{const r=n(this.agentIdentifier),i=[...this.desiredFeatures];i.sort(((t,r)=>e.p[t.featureName]-e.p[r.featureName])),i.forEach((t=>{if(r[t.featureName]||t.featureName===e.D.pageViewEvent){const n=function(t){switch(t){case e.D.ajax:return[e.D.jserrors];case e.D.sessionTrace:return[e.D.ajax,e.D.pageViewEvent];case e.D.sessionReplay:return[e.D.sessionTrace];case e.D.pageViewTiming:return[e.D.pageViewEvent];default:return[]}}(t.featureName);n.every((e=>r[e]))||(0,l.Z)("".concat(t.featureName," is enabled but one or more dependent features has been disabled (").concat((0,D.P)(n),"). This may cause unintended consequences or missing data...")),this.features[t.featureName]=new t(this.agentIdentifier,this.sharedAggregator)}})),(0,T.Qy)(this.agentIdentifier,this.features,t)}catch(e){(0,l.Z)("Failed to initialize all enabled instrument classes (agent aborted) -",e);for(const e in this.features)this.features[e].abortHandler?.();const r=(0,T.fP)();return delete r.initializedAgents[this.agentIdentifier]?.api,delete r.initializedAgents[this.agentIdentifier]?.[t],delete this.sharedAggregator,r.ee?.abort(),delete r.ee?.get(this.agentIdentifier),!1}}}({features:[J,m,S,class extends h{static featureName=oe;constructor(t,r){if(super(t,r,oe,!(arguments.length>2&&void 0!==arguments[2])||arguments[2]),!c.il)return;const n=this.ee;let i;(0,k.QU)(n),this.eventsEE=(0,k.em)(n),this.eventsEE.on(se,(function(e,t){this.bstStart=(0,p.z)()})),this.eventsEE.on(ae,(function(t,r){(0,s.p)("bst",[t[0],r,this.bstStart,(0,p.z)()],void 0,e.D.sessionTrace,n)})),n.on(ce+ne,(function(e){this.time=(0,p.z)(),this.startPath=location.pathname+location.hash})),n.on(ce+ie,(function(t){(0,s.p)("bstHist",[location.pathname+location.hash,this.startPath,this.time],void 0,e.D.sessionTrace,n)}));try{i=new PerformanceObserver((t=>{const r=t.getEntries();(0,s.p)(te,[r],void 0,e.D.sessionTrace,n)})),i.observe({type:re,buffered:!0})}catch(e){}this.importAggregator({resourceObserver:i})}},C,xe,B,class extends h{static featureName=de;constructor(e,r){if(super(e,r,de,!(arguments.length>2&&void 0!==arguments[2])||arguments[2]),!c.il)return;if(!(0,t.OP)(e).xhrWrappable)return;try{this.removeOnAbort=new AbortController}catch(e){}let n,i=0;const o=this.ee.get("tracer"),a=(0,k._L)(this.ee),s=(0,k.Lg)(this.ee),u=(0,k.BV)(this.ee),d=(0,k.Kf)(this.ee),f=this.ee.get("events"),l=(0,k.u5)(this.ee),h=(0,k.QU)(this.ee),g=(0,k.Gm)(this.ee);function m(e,t){h.emit("newURL",[""+window.location,t])}function v(){i++,n=window.location.hash,this[ve]=(0,p.z)()}function b(){i--,window.location.hash!==n&&m(0,!0);var e=(0,p.z)();this[pe]=~~this[pe]+e-this[ve],this[ye]=e}function y(e,t){e.on(t,(function(){this[t]=(0,p.z)()}))}this.ee.on(ve,v),s.on(be,v),a.on(be,v),this.ee.on(ye,b),s.on(ge,b),a.on(ge,b),this.ee.buffer([ve,ye,"xhr-resolved"],this.featureName),f.buffer([ve],this.featureName),u.buffer(["setTimeout"+le,"clearTimeout"+fe,ve],this.featureName),d.buffer([ve,"new-xhr","send-xhr"+fe],this.featureName),l.buffer([me+fe,me+"-done",me+he+fe,me+he+le],this.featureName),h.buffer(["newURL"],this.featureName),g.buffer([ve],this.featureName),s.buffer(["propagate",be,ge,"executor-err","resolve"+fe],this.featureName),o.buffer([ve,"no-"+ve],this.featureName),a.buffer(["new-jsonp","cb-start","jsonp-error","jsonp-end"],this.featureName),y(l,me+fe),y(l,me+"-done"),y(a,"new-jsonp"),y(a,"jsonp-end"),y(a,"cb-start"),h.on("pushState-end",m),h.on("replaceState-end",m),window.addEventListener("hashchange",m,(0,O.m$)(!0,this.removeOnAbort?.signal)),window.addEventListener("load",m,(0,O.m$)(!0,this.removeOnAbort?.signal)),window.addEventListener("popstate",(function(){m(0,i>1)}),(0,O.m$)(!0,this.removeOnAbort?.signal)),this.abortHandler=this.#e,this.importAggregator()}#e(){this.removeOnAbort?.abort(),this.abortHandler=void 0}}],loaderType:"spa"})})(),window.NRBA=o})(); window.jQuery || document.write(' ') CKEDITOR_BASEPATH='https://f1000research.com/js/vendor/ckeditor/' window.reactTheme = 'research'; window.MathJax = { CommonHTML: { linebreaks: { automatic: true } }, 'HTML-CSS': { linebreaks: { automatic: true } }, SVG: { linebreaks: { automatic: true } }, AuthorInit: function() { MathJax.Hub.Register.MessageHook('End Process', function () { let timeout = false; // holder for timeout id const delay = 250; // delay after event is "complete" to run callback const reflowMath = function() { const dispFormulas = document.querySelectorAll('.disp-formula.panel'); if (!dispFormulas) { return; } for (const dispFormula of dispFormulas) { const child = dispFormula.querySelector('.MathJax_Preview').nextSibling.firstChild; const isMultiline = MathJax.Hub.getAllJax(dispFormula)[0].root.isMultiline; if (dispFormula.offsetWidth < child.offsetWidth || isMultiline) { MathJax.Hub.Queue(['Rerender', MathJax.Hub, dispFormula]); } } }; window.addEventListener('resize', function() { clearTimeout(timeout); // clear the timeout timeout = setTimeout(reflowMath, delay); // start timing for event "completion" }); }); }, }; if (window.location.hash == '#_=_'){ window.location = window.location.href.split('#')[0] } !function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function() {n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)} ;if(!f._fbq)f._fbq=n; n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window, document,'script','https://connect.facebook.net/en_US/fbevents.js'); fbq('init', '1641728616063202'); fbq('track', "PixelInitialized", {}); (function(h,o,t,j,a,r){ h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)}; h._hjSettings={hjid:2318163,hjsv:6}; a=o.getElementsByTagName('head')[0]; r=o.createElement('script');r.async=1; r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv; a.appendChild(r); })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv='); search file_upload Submit your research search menu close search Browse Gateways & Collections How to Publish Submit your Research My Submissions Article Guidelines Article Guidelines (New Versions) Open Data, Software and Code Guidelines Open Data and Accessible Source Materials Guidelines (HSS) Open Data, Software and Code Guidelines (PSE) Prepublication Checks Production Process Posters and Slides Guidelines Document Guidelines Article Processing Charges Peer Review Finding Article Reviewers About How it Works For Reviewers Our Advisors Policies Glossary FAQs For Developers Newsroom Contact My Research Submissions Content and Tracking Alerts My Details Sign In file_upload Submit your research { "@context": "https://schema.org", "@type": "ScholarlyArticle", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://f1000research.com/articles/3-94" }, "headline": "Data publication consensus and controversies", "datePublished": "2014-04-23T11:32:40", "dateModified": "2014-10-16T11:09:26", "author": [ { "@type": "Person", "name": "John Kratz" }, { "@type": "Person", "name": "Carly Strasser" } ], "publisher": { "@type": "Organization", "name": "F1000Research", "logo": { "@type": "ImageObject", "url": "https://f1000research.com/img/AMP/F1000Research_image.png", "height": 480, "width": 60 } }, "image": { "@type": "ImageObject", "url": "https://f1000research.com/img/AMP/F1000Research_image.png", "height": 1200, "width": 150 }, "description": "The movement to bring datasets into the scholarly record as first class research products (validated, preserved, cited, and credited) has been inching forward for some time, but now the pace is quickening. As data publication venues proliferate, significant debate continues over formats, processes, and terminology. Here, we present an overview of data publication initiatives underway and the current conversation, highlighting points of consensus and issues still in contention. Data publication implementations differ in a variety of factors, including the kind of documentation, the location of the documentation relative to the data, and how the data is validated. Publishers may present data as supplemental material to a journal article, with a descriptive “data paper,” or independently. Complicating the situation, different initiatives and communities use the same terms to refer to distinct but overlapping concepts. For instance, the term published means that the data is publicly available and citable to virtually everyone, but it may or may not imply that the data has been peer-reviewed. In turn, what is meant by data peer review is far from defined; standards and processes encompass the full range employed in reviewing the literature, plus some novel variations. Basic data citation is a point of consensus, but the general agreement on the core elements of a dataset citation frays if the data is dynamic or part of a larger set. Even as data publication is being defined, some are looking past publication to other metaphors, notably “data as software,” for solutions to the more stubborn problems." } { "@context": "http://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": "1", "item": { "@id": "https://f1000research.com/", "name": "Home" } }, { "@type": "ListItem", "position": "2", "item": { "@id": "https://f1000research.com/browse/articles", "name": "Browse" } }, { "@type": "ListItem", "position": "3", "item": { "@id": "https://f1000research.com/articles/3-94", "name": "Data publication consensus and controversies" } } ] } Home Browse Data publication consensus and controversies ALL Metrics - Views Downloads Get PDF Get XML Cite How to cite this article Kratz J and Strasser C. Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.12688/f1000research.3979.3 ) NOTE: If applicable, it is important to ensure the information in square brackets after the title is included in all citations of this article. Close Copy Citation Details Export Export Citation Sciwheel EndNote Ref. Manager Bibtex ProCite Sente EXPORT Select a format first Track Share ▬ ✚ Review Revised Data publication consensus and controversies [version 3; peer review: 3 approved] John Kratz 1 , Carly Strasser 1 John Kratz 1 , Carly Strasser 1 PUBLISHED 16 Oct 2014 Author details Author details 1 California Digital Library, University of California Office of the President, Oakland, CA, 94612, USA OPEN PEER REVIEW DETAILS REVIEWER STATUS This article is included in the Research on Research, Policy & Culture gateway. This article is included in the Data: Use and Reuse collection. Abstract The movement to bring datasets into the scholarly record as first class research products (validated, preserved, cited, and credited) has been inching forward for some time, but now the pace is quickening. As data publication venues proliferate, significant debate continues over formats, processes, and terminology. Here, we present an overview of data publication initiatives underway and the current conversation, highlighting points of consensus and issues still in contention. Data publication implementations differ in a variety of factors, including the kind of documentation, the location of the documentation relative to the data, and how the data is validated. Publishers may present data as supplemental material to a journal article, with a descriptive “data paper,” or independently. Complicating the situation, different initiatives and communities use the same terms to refer to distinct but overlapping concepts. For instance, the term published means that the data is publicly available and citable to virtually everyone, but it may or may not imply that the data has been peer-reviewed. In turn, what is meant by data peer review is far from defined; standards and processes encompass the full range employed in reviewing the literature, plus some novel variations. Basic data citation is a point of consensus, but the general agreement on the core elements of a dataset citation frays if the data is dynamic or part of a larger set. Even as data publication is being defined, some are looking past publication to other metaphors, notably “data as software,” for solutions to the more stubborn problems. READ ALL READ LESS Corresponding Author(s) John Kratz ( [email protected] ) Close Corresponding author: John Kratz Competing interests: No competing interests were disclosed. Grant information: JK is supported by a Council on Library and Information Resources/Digital Library Foundation Postdoctoral Fellowship in Data Curation for the Sciences and Social Sciences funded by the California Digital Library and the Alfred P. Sloan Foundation. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Copyright: © 2014 Kratz J and Strasser C. This is an open access article distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. Data associated with the article are available under the terms of the Creative Commons Zero "No rights reserved" data waiver (CC0 1.0 Public domain dedication). How to cite: Kratz J and Strasser C. Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.12688/f1000research.3979.3 ) First published: 23 Apr 2014, 3 :94 ( https://doi.org/10.12688/f1000research.3979.1 ) Latest published: 16 Oct 2014, 3 :94 ( https://doi.org/10.12688/f1000research.3979.3 ) Revised Amendments from Version 2 This version no longer presents three models for data publication based on documentation. Instead, we treat documentation as an essential feature and discuss three forms of documentation in parallel with forms of availability, citation, and validation. The figure has been updated to reflect this reorganization. Numerous minor additions, corrections and clarifications were made throughout in response to referee and reader comments. Most significantly, the discussions of paper-independent documentation and validation have been expanded, as has the concluding "beyond data publication." This version no longer presents three models for data publication based on documentation. Instead, we treat documentation as an essential feature and discuss three forms of documentation in parallel with forms of availability, citation, and validation. The figure has been updated to reflect this reorganization. Numerous minor additions, corrections and clarifications were made throughout in response to referee and reader comments. Most significantly, the discussions of paper-independent documentation and validation have been expanded, as has the concluding "beyond data publication." See the authors' detailed response to the review by Mark Parsons and Peter Fox READ REVIEWER RESPONSES What does data publication mean? The idea that researchers should share data to advance knowledge and promote the common good is an old one, but in recent years the conversation has shifted from sharing data to publishing data 1 – 3 . This shift in language stems from the conviction that datasets should join the scholarly record and be afforded the same first-class status as traditional research products like journal articles 4 , 5 . While many in the scholarly communication community share this goal, different people and organizations often refer to different things with the phrase data publication . Lawrence et al. (2011) define formal data Publication (upper-case “P”) as making data as permanently available as possible following “a process which means it can appear along with easily digestible information as to its trustworthiness, reliability, format and content” 3 . Callaghan et al. (2012) draw an explicit distinction between Published and published data: p ublished data is at least available, while P ublished data is persistent, documented, and peer-reviewed 5 . P ublication refers to the scholarly literature, while p ublication is used in the sense of any kind of printed and distributed material. Actual usage is considerably more complicated. Data publication overlaps with terms like data sharing , data release , and open data . A data publication might be a spreadsheet on a website, a set of images in an institutional archive, a stream of readings from a weather station transmitted over the internet, or a peer-reviewed article describing a dataset; a data publisher might be a data journal publisher, archive, database, or repository. Despite uncertainty over precisely what qualifies, the scholarly communication community largely agrees on three essential properties of a data publication ( Figure 1 ) 2 , 5 . First, published data is publicly available now and for the indefinite future; access might demand payment of fees or acceptance of a legal agreement, but is not subject to the whims of the author. Second, published data must be adequately documented such that, at a minimum, a researcher in the same field could reproduce or reuse it. Third, like a book or journal article, a data publication can be formally cited . Data citation maintains the integrity of the expanded scholarly record and offers a reward– in the currency of academic prestige– to encourage researchers to publish data. Open questions flock around a fourth property: how and to what extent a published dataset must be validated . Here, we will consider data that is persistently available, documented, and citable to be published, whatever the level of validation. Figure 1. To be published, datasets are typically deposited in a repository to make them available, documented to support reproduction and reuse, and assigned an identifier to facilitate citation. Some, but not all, publishers review datasets to validate them. Why publish data? The underlying goals of data publication are to enable research to be reproduced and data to be reused . Hidden primary data exacerbates science’s very public “reproducibility crisis” 6 – 10 , recently illustrated by the collapse of a pair of irreproducible Nature articles describing a simple method to transform any cell into a stem cell 11 , 12 . Psychology’s “closed data culture” 13 enabled Diederik Stapel to invent data for an astonishing 55 papers, prompting calls for routine psychology data publication 13 – 15 . Widespread publication of the data underlying research papers could help expose honest errors as well as fraud 16 . The leaders of the US National Institutes of Health (NIH) recently suggested “greater transparency of the data that are the basis of published manuscripts” as one way to improve scientific reproducibility 17 . Journals already frequently require authors to supply underlying data on request. In 2011, Alsheikh-Ali et al. found that 88% of high-impact journals required a statement regarding the availability of underlying data, and half of those made willingness to provide data a condition of publication 18 . However, authors of 59% of the papers examined in the study failed to adhere to the availability instructions. Vines et al. (2014) could only obtain underlying data from 101 of 516 papers published from 1991 to 2011 19 . Availability dropped off sharply with time; out of the 62 oldest papers, data was available from only two. Now, some journals require that underlying data be published simultaneously with the article. In 2010, a coalition of Ecology and Evolutionary Biology journals began to require that the data underlying articles be archived with a maximum embargo of one year 20 , 21 . F1000Research has had a similar policy (without an embargo period) since its inception, and the Public Library of Science (PLOS) journals followed suit earlier this year 22 . Although there can be no substitute for funding new experiments and data collection, appropriate data reuse lowers costs and accelerates research. Documenting, publishing, and archiving data is time consuming and costly, but usually far less so than repeating the data collection. Open Context published archaeological data from a site in eastern Turkey at the substantial cost of $10,000–15,000, but this expense is minor compared to $800,000 spent to collect the data 23 . Piwowar (2011) contrasted the impact of $100,000 in National Science Foundation (NSF) grants, which generates an average of three to four papers, with an estimate that the same investment in curating, archiving, and publishing data could contribute to over 1,000 publications 24 . Furthermore, while some data is merely expensive to replace, time-dependent or ephemeral data, (e.g., climate records or observations of unique astronomical events) can never be recreated for any price 25 . Availability Fundamentally, to publish is to make public, and to publish data is to make data publicly available. Present availability requires mechanisms for access; future availability also requires preservation (e.g., long-term storage, format migration) 25 – 27 . As in print publication, published data need not be free or legally unencumbered, and data use agreements constrain many published datasets. If access is limited, it should be contingent on clear and objective criteria; writing a request to the creator for permission should not be part of the process. For example, before granting access to restricted data, The interuniversity Consortium for Political and Social Research (ICPSR) evaluates the applicant’s ability to handle the data securely, but not the merit of the research. The most common source of access restrictions is the need to protect the privacy of human research subjects. In the United States, the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy Rule severely limits the disclosure of medical information 28 . As a practical matter, publishing a dataset usually includes depositing it in a trustworthy repository. What constitutes “trustworthy” is somewhat subjective and there are a handful of certification schemes to choose from. In 2007, The Center for Research Libraries (CRL) published the most extensive scheme: the Trusted Repository Audit Checklist (TRAC) 29 . Many repositories consult TRAC for self-assessment, but only four ( listed by the CRL ) have completed the lengthy and rigorous process to be officially certified. That same year, DANS released the Data Seal of Approval (DSA) guidelines; 31 repositories have been stamped with the DSA since then. The Trusted Digital Repository framework incorporates the DSA, a TRAC-derived standard, and a third standard from the German Institute for Standardization (DIN) to give repositories flexibility in the processes and standards by which they are to be certified. Repositories seeking to join the World Data System (WDS) are certified to perform particular role (i.e., data publisher) based on a self-description and possibly a site visit; the WDS currently boasts 56 regular members. Even taken together, these standards certify only a fraction of the hundreds of repositories in operation (e.g., the 973 now listed Databib or the 609 at re3data.org ). In practice, the perceived trustworthiness of a repository often derives from the reputation of its managing organization. For instance, repositories run by governments or large universities are likely to be considered trustworthy (although the effects of the 2013 US government shutdown on the PubMed biomedical article database 30 might give one pause). Documentation To be useful or reproducible, a dataset must be accompanied by descriptive information (i.e., metadata) 25 . Preparing documentation is frequently the most laborious step for researchers in taking data from useable within the lab to useable by others, and rewarding this effort is a major impetus for data publication. Dataset documentation– which might resemble a paper– is a natural hook for bringing data into the scholarly record. The Opportunities for Data Exchange (ODE) project elaborated Jim Gray’s pyramidal model of online scientific data 31 into five classes of relationship between data and the literature: ‘desk-drawer’ data and four forms of publication 4 . Similarly, five classes of data publication described by Lawrence et al. (2011) have recognizably different kinds of documentation 3 . Note, however, that a single dataset may have relationships with multiple articles or other documentation, and an article may use or describe multiple datasets. Here, we will discuss three non-mutually-exclusive relationships with the literature: a dataset may supplement a traditional research paper, be the subject of a “data paper”, or be independently documented by its publisher. Data that supplements a paper The most familiar kind of data publication is a traditional journal article accompanied by underlying data. That data can be hosted by the journal as supplementary material or deposited in a third-party repository. The trend is away from supplemental material because repositories are considered to be better suited to ensure long-term preservation and access to the data. For instance, The Journal of Neuroscience stopped publishing supplemental material in 2010; the announcement promotes disciplinary repositories as “vastly superior to supplemental material as a mechanism for disseminating data” 32 . Data underlying any peer-reviewed or otherwise “reputable” publication can be deposited in the Dryad repository. Dryad makes data available and citable, but the publisher of the article must manage any assessment of scientific validity. Research Compendia compiles published articles together with all the underlying code and data. Beyond repositories like these specifically for paper-related data, many more publishers that do not require such a relationship are nevertheless pleased to publish data underlying or described by a paper. This kind of data publication supports reproduction of an analysis, but not necessarily reuse. For example, the PLOS data policy requires publication of only the data needed to reproduce the article’s finding. Consequently, not all of the data collected must be published, and the documentation need not support reuse for an unrelated purpose. Data as the subject of a paper A data paper describes a dataset with thoroughly detailed rationale and collection methods, but lacks any analysis or conclusions 33 . Data papers are flourishing as a new article type in journals such as F1000Research , Internet Archaeology , and GigaScience , as well as in dedicated journals like Earth System Science Data 34 , Geoscience Data Journal , Nature Publishing Group’s Scientific Data , and a trio of “metajournals” from Ubiquity Press. The strength of a data paper is in providing rich documentation, which is especially useful for unique and heterogeneous “long-tail” 35 research data. Data paper length and structure varies between journals, but the tendency is toward a short, tightly structured format. All journals require an abstract, collection methods, and a description of the dataset; a few encourage authors to suggest potential uses for the data (e.g., Internet Archaeology , and Open Health Data ). Some journals supplement this general framework with field-specific sections. (e.g., Internet Archaeology and the Journal of Open Archaeology Data each include a section for temporal and geographic scope). Data papers are most sharply defined not by the presence of any particular information, but by the absence of analysis or conclusions. A crisp distinction from other article types is important because many journals do not consider a data paper to be prior publication if the authors seek to publish an analysis of the same dataset (e.g., Nature -titled journals, Science , and others listed by F1000Research ). Data journals generally limit themselves to publishing the description of the dataset; a trusted repository publishes the data itself. For instance, Scientific Data and Geoscience Data Journal each direct authors to a list of approved repositories. One exception, GigaScience hosts data in an integrated repository named GigaDB . Another, The International Journal of Robotics Research 33 permits authors to host datasets on their own websites. Data papers are predated by an approach that Lawrence et al. (2011) call data publication by proxy , in which a paper providing a general description of a database or dataset serves as a citable proxy 3 . Proxy publications are distinguished from data papers in that they may contain analysis or conclusions drawn from the dataset and they may not contain all of the information needed to use the data. For example, the Climatic Research Unit of the University of East Anglia asks dataset users cite to papers associated with a dataset instead of the data itself. In the biosciences, Nucleic Acids Research (NAR) annually publishes a massive issue devoted to such articles; the 2014 database issue featured 58 papers describing new databases and 123 updates on existing resources 36 . Participating databases typically ask users to cite the most recent NAR paper. Proxy publication or data paper citation serves to award scholarly credit, but fails at other functions of citation and should be supplemented with direct citation of the data. Independent documentation Dataset documentation need not take the form of a journal article. Together with data, repositories and databases publish documentation– minimal or rich, structured or freeform– that sometimes fulfills the needs of reproducibility and reuse without reference to the literature. Even so, an independently documented dataset might also be described by a data paper or support any number of traditional articles. Academic, governmental, and commercial repositories publish data from diverse place- and interest-based research communities through varying processes with or without linkage to the literature. Institutional repositories preserve and publish any kind of data generated by the research communities they serve, e.g., University of California researchers deposit data in Merritt , while Purdue University researchers use the Purdue Research Repository (PURR) . At the national level, the Dutch Data Archiving and Networked Services (DANS) accepts a broad range of data from researchers in the Netherlands. Figshare and Zenodo publish data from any researcher in any field. These broad-topic publishers are well suited to handle heterogeneous or long-tail data that does not fit comfortably in a specialized repository. But, because repositories typically cannot assemble domain expertise across such a broad range of disciplines, this inclusiveness imposes limits on documentation requirements and validation. While Figshare and Zenodo do accommodate rich documentation, they require very little. Interest-based research communities are served by a thriving ecosystem of specialized data publishers. The broadest of these publishers serve entire disciplines, e.g., the Digital Archaeological Record (tDAR) . A narrower example from the life sciences is the group of databases centered around model organisms, such as WormBase 37 or FlyBase 38 ; these databases aggregate diverse, but finite, data types and benefit from extensive domain expertise. Along similar lines, a data publisher may deal with a particular data-type, such as gene expression data in the Gene Expression Omnibus (GEO) or seismological data in SeismicPortal . Focus on a particular type of data facilitates rigorous technical validation and development of specialized metadata requirements to ensure the data is useable. For instance, GEO data ingest meshes with Minimum Information About a Microarray Experiment (MIAME) 39 documentation guidelines 40 . As a final example, a publisher might be devoted to a particular scientific instrument or facility, such as the One Degree Imager Portal, Pipeline, and Archive (ODI-PPA) or the Worldwide LHC Computing Grid ), the massive infrastructure built to handle the output of the Large Hadron Collider (LHC). Unlike most other publishers, these emphasize real time access to data coming off the instruments. Because researchers know the databases that serve their community, data in disciplinary repositories is easy to discover and because it is relatively standardized, it is easy to reuse. A disadvantage is that the data from a single research program can be distributed across many repositories (e.g., gene expression data in one, sequence data in another), whereas an institutional or broad-scope repository can publish the whole research story. Citability Data citation is the element of publication that has come the farthest toward consensus. In early 2014, a coalition of organizations brought together by Future Of Research Communication and E-Scholarship (FORCE11) 41 released a Joint Declaration of Data Citation Principles . The first of the eight principles states, in part, that “[d]ata citations should be accorded the same importance in the scholarly record as citations of other research objects, such as publications”. Most of the time, this means that when a published dataset contributes to a paper, it should be cited formally in the reference list. Unfortunately, actual practice lags far behind this consensus. Not all article publishers allow data citations in the references and, even when permitted, most authors refer to data in the text without a formal citation 42 . Many data publishers provide no guidance on citation; others ask users to cite a proxy publication (e.g., from the NAR database issue). However, a growing number of data publishers do supply users with explicit citation instructions; Dryad, Figshare, and Zenodo dataset landing pages all display a formatted citation and links for import into reference managers. Many data publishers facilitate formal citation by assigning unique permanent identifiers, most commonly the same ones used for journal articles: Digital Object Identifiers (DOIs). In addition to precisely specifying what resource is being cited, a DOI can be resolved to locate the referenced dataset. Note, however, that a DOI is neither sufficient nor necessary for citability, which demands that the referenced object be persistent and locatable via the citation. If a dataset moves and the DOI is not updated with the new location, the citation breaks. Conversely, a well-maintained web-address works as well as a DOI in theory– although a DOI is more likely to be maintained in practice. Simple case The present consensus is that a dataset should be cited using, at a minimum, five elements largely familiar from article citations: creator(s), title, year, publisher and identifier. This format agrees with Committee on Data for Science and Technology (CODATA) recommendations 43 and conveys all the information required to obtain a DataCite DOI 44 or be listed in the Thomson-Reuters Data Citation Index . The basic format works well when a dataset can be cited like an article, but that is not always the case. Deep citation One major complication data citation faces is the need for deep citation . When supporting an assertion in writing, it usually suffices to cite the entirety of an article or the page of a book and leave it to the inquisitive reader to find the relevant passage. But, to reproduce an analysis performed on a subset of a larger dataset, the reader needs to know exactly what subset was used (e.g., a limited range of dates, only the adult subjects, wind speed but not direction). Datasets vary so widely in structure that there may not be a good general solution for describing subsets. The most common suggestion is to cite the entire dataset in the reference list and describe the subset in the text of the paper 45 . The Federation of Earth Science Information Partners (ESIP) and the National Snow and Ice Data Center (NSIDC) both recommend defining the subset in the citation itself, using a format suited to the dataset’s internal structure (e.g., a temporal or spatial range, a list of variables, or an internal identifier). Dynamic datasets A second major complication arises when datasets change. In the past, the printing process cemented one version of an article as the version of record. Even for traditional scholarly literature, web-based publishing and preprint servers (e.g., arXiv.org ) are complicating the situation, but datasets are especially prone to be dynamic . Two kinds of dynamic datasets warrant consideration: growing datasets that add new data while never changing or deleting existing data, and revisable datasets where data may by added, deleted, or changed. Consider USC00046336, a weather station at the Oakland Museum of California. Each day, the high temperature, low temperature and amount of precipitation recorded at the Museum 46 flow, together with data from more than 20,000 other stations, into the swelling Global Historical Climate Network (GHCN)-Daily 47 dataset. Or, consider WormBase, the genome database used by the Caenorhabditis elegans research community. WormBase encompasses genomic sequences of C. elegans and 20 related species massively annotated with gene structures, protein sequences, expression patterns, and a host of other information from empirical data and computational predictions. Every two months, WormBase administrators respond to new data and better computational models by issuing a revised version with new material added and inaccurate material deleted or corrected. Additions and updates to published datasets are extremely valuable, but a researcher seeking to reproduce an analysis of a dynamic dataset needs access to a particular version. To enable that access, previous versions must be preserved and citable. Growing datasets can be cited with an access date or a date range in the citation, as recommended by ESIP and NSIDC. Revisable datasets are more difficult; the most common approach is to accumulate revisions and periodically publish a new version with a citable version number. For example, WormBase identifies each release with a version number and makes all of the previous versions available. Controversy persists around the specific issue of identifiers for dynamic datasets. DataCite recommends, but does not insist, that their DOIs refer to immutable digital objects. NSIDC and ESIP instruct researchers to use a single identifier for growing datasets and include the access date in the citation; each major version of a revisable datasets gets a new identifier, but minor versions do not. In contrast, the Digital Curation Centre (DCC), Dataverse , and the UK Natural Environment Research Council (NERC) insist that any change to a dataset should trigger a new identifier 5 , 45 , 48 . To handle the difficulties with dynamic data that this policy creates, the DCC recommends periodically issuing growing datasets a new identifier that refers to the time-slice of new records and freezing versions of revisable datasets as individually-identified snapshots . Just-in-time identifiers The difficulties surrounding deep citation and dynamic data could potentially be solved by turning the identifier-issuing process on its head. Instead of the dataset publisher issuing identifiers for data at the level that researchers seem likely to cite, researchers could issue identifiers for only the part of the dataset that they want to cite. The Research Data Alliance (RDA) Data Citation Working Group recently put forth a sophisticated proposal applicable to data in (or convertible to) databases. Identifiers created under this scheme would wrap together identification of a database, a query to return the cited dataset, the version of the database queried for this analysis, and a number of other useful components. The ultimate promise is to provide a simple yet precise citation for any selection of data, at the cost of technical complexity “under the hood”. Validation Data validation is the least resolved aspect of data publication, and fundamental questions are still unanswered: What minimum level of quality should a published dataset guarantee? How and by what criteria can datasets be evaluated against that guarantee? How should dynamic datasets be handled? Is literature peer-review an appropriate model? Callaghan et al. (2012) 5 draw a useful distinction between technical and scientific review. Technical review verifies that a dataset is complete, its description is complete, and that the two match up. Domain expertise is generally not required, and many repositories provide at least some level of technical review. Scientific review evaluates the methods of data collection, the overall plausibility of the data, and the likely reuse value. Scientific review does require domain expertise, making this level of validation more difficult to organize 13 . When data is published with a data paper, review may be split between the repository for technical review and the data journal for scientific review. Data paper peer review Peer review guarantees that journal articles entering the scholarly record reach some level of validity (although the aforementioned reproducibility crisis calls into question exactly what that level is). In many fields, peer-reviewed publications enjoy a much higher status than any other literature. Any effort to apply the prestige of “publication” to datasets cascades naturally into an effort to apply the prestige of “peer review”. But as data validation seeks to model itself on literature peer review, literature peer review itself is in flux 49 – 51 . Open peer review at F1000Research and post-publication commenting at PubMed Commons are just two of many ongoing web-enabled experiments in article evaluation. Journal article reviewers traditionally consider whether the methods used are appropriate for the questions asked and the data collected support the conclusions drawn. In the absence of particular questions and conclusions, it is not obvious what peer review of data should certify. A dataset may serve for some purposes, but not for others and a reviewer may anticipate many potential uses for the data, but surely not all 52 . Researchers are already over-whelmed by peer review of articles 53 and could find any increased workload unreasonable. Despite all these difficulties, venues for peer-reviewed data papers are opening rapidly. Data paper journals wrap scientific peer review of the paper and the dataset together into a single process. GigaScience , an exception, assigns technical review of the dataset to a separate data reviewer. The guidelines that various data journals provide to reviewers are fairly uniform, except that about half consider novelty or potential impact, while the rest only require the dataset to be scientifically sound. Although the guidelines are similar, review processes differ widely. As an example, compare Biodiversity Journal and Scientific Data . Both journals divide reviewer guidelines into three sections along similar lines, which Biodiversity Journal calls “quality of the data”, “quality of the description”, and “consistency between manuscript and data”. Scientific Data follows a traditional peer-review process: an editor appoints reviewers who are encouraged to remain anonymous. In contrast, review at Biodiversity Journal follows a flexible and open process featuring entirely optional anonymity and multiple types of reviewer. There, an editor appoints two or three “nominated” reviewers who must report back and several “panel” reviewers who read the paper and only comment at their discretion. Additionally, the authors may choose to open the paper to public comment during the review process. Independent data validation Data journals all model their data validation more or less faithfully on literature peer review, but independent data validation practices and proposals are considerably more varied. Lawrence et al. (2011) propose a set of independent data peer review guidelines similar to the ones used by data journals 3 . Each of The National Aeronautics and Space Administration (NASA) Distributed Active Archive Centers (DAACs) draws on an affiliated User Working Group for domain expertise. The NSIDC combines an internal assessment of the effort that will be required to publish a dataset at a desired level of service (roughly corresponding to technical review) with an external assessment of scientific quality. The Planetary Data System (PDS) peer-reviews datasets via an in-person meeting with representatives of the repository, the dataset creators, and the reviewers. Pre-publication validation can be supplemented or replaced by post-publication feedback from successful or unsuccessful reusers. Parsons et al. (2010) suggest that “data use in its own right provides a form of review”, and go on to point out that the context of reuse demonstrates that the data is not simply “good”, but fit for some particular purpose 52 . The DANS repository solicits feedback from researchers who use its datasets: users are asked to rate the dataset on a one to five scale in each of six criteria (e.g., data quality, quality of the documentation, structure of the dataset) 54 , 55 . Researchers trust peer review in part because they understand the process and its limitations; if researchers come to understand them, alternate pre- or post-publication validation processes could potentially provide the same level of assurance. Two examples from archaeology, Open Context and the Digital Archaeological Record (tDAR), illustrate the diversity of approaches to data validation. Open Context provides multiple validation processes that incorporate peer review beyond a simple accept/reject binary 23 . Each Open Context dataset is rated from one to five based not on quality per se , but on the thoroughness of the validation; a one comes with no guarantees, a three has passed a technical review, and a five has passed external peer review. Whereas Open Context is a boutique publisher, focusing on data presentation and reuse, tDAR is a large repository primarily concerned with collecting and preserving archaeology data for future use. tDAR is able to operate at scale by performing only technical validation and streamlining data deposition with a minimum of mandatory description. However, tDAR also serves as a platform for high-quality data publication. The repository accommodates contributors who provide more information, and much of the content is deposited by digital curators who can be relied on to supply rich descriptions. Furthermore, two data paper journals, Internet Archaeology and Journal of Open Archaeological Data , recommend both tDAR and Open Context as repositories for their peer-reviewed data. Thus, data validation depends not only on discipline and data type, but on a host of external factors, including the goals of the organizations and researchers involved. Beyond data publication Consensus abides wherever traditional scholarly publication offers a clear model for data; controversy churns wherever the literature offers only murky guidance. Static datasets of manageable size and simple structure can be made available, identified, and cited like the literature. Dynamic and complex datasets raise questions that attract multiple and sometimes conflicting answers. Where the guidance of the print metaphor threatens to give out, it must be extended creatively— or abandoned for another approach entirely. Parsons and Fox (2013) 56 argue that thinking about data through the metaphor of print publication is often misleading. They advocate treating publication as only one metaphor in a larger ecosystem of metaphors for sharing data. For example, they associate the uniform, high-volume output from instruments like the Large Hadron Collider with industrial production and suggest “Big Iron” as an alternative metaphor for this kind of data. Another alternative metaphor that seems to be gaining particular traction is “data as software” 57 . Here, one thinks of releasing a dataset like a piece of software and regards subsequent changes as analogous to updated versions. The open-source software community has already developed many potentially relevant tools for working collaboratively, managing multiple versions, and tracking attribution. Ram (2013) 58 catalogs a multitude of scientific uses for the software version control system Git , including data management. Open Context uses Git and Mantis Bug Tracker to track and correct dataset errors. The Dat project “aim[s] to bring to data a style of collaboration similar to what Git brings to source code”. Furthermore, projects such as IPython Notebook integrate data, processing, and analysis into a single package. Unfortunately, scientific software struggles for recognition 59 just as data does, so that metaphor offers little guidance for navigating the academic reward system. On the other hand, the publication metaphor targets this system explicitly, but leaves numerous other gaps. Although some aspects of data publication have matured to a firm and useful consensus– exemplified most powerfully by the Joint Declaration of Data Citation Principles– the field as a whole is still burgeoning. Controversial issues, such as validation, may be best addressed by presenting an array of options rather than converging on a single solution. In the ongoing conversation, data publication may come to refer to only those means of dissemination most directly drawn from the scholarly literature, or it may open as a canopy over a range of approaches. Whichever the case, it is our hope and expectation that for the foreseeable future, mixing of metaphors and contemplation of the unique properties of research data will continue to yield novel forms of data-centered scholarly production. Author contributions JK collected information and prepared the first draft of the manuscript. JK and CS designed the scope and direction of the study. Both authors contributed to the writing and editing of the manuscript. Competing interests No competing interests were disclosed. Grant information JK is supported by a Council on Library and Information Resources/Digital Library Foundation Postdoctoral Fellowship in Data Curation for the Sciences and Social Sciences funded by the California Digital Library and the Alfred P. Sloan Foundation. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Acknowledgements The authors would like to thank colleagues at the CDL and Jodi Reeves Flores for productive discussions. Margaret Smith and Christina Doyle contributed invaluable suggestions for editing the manuscript. Faculty Opinions recommended References 1. Costello MJ: Motivating online publication of data. BioScience. 2009; 59 (5): 418–427. Publisher Full Text 2. Smith VS: Data publication: towards a database of everything. BMC Res Notes. 2009; 2 : 113. PubMed Abstract | Publisher Full Text | Free Full Text 3. Lawrence B, Jones C, Matthews B, et al. : Citation and peer review of data: Moving towards formal data publication. Int J Digit Curation. 2011; 6 (2): 4–37. Publisher Full Text 4. Reilly S, Wouter S, Schrimpf S, et al. : Report on integration of data and publications. Zenodo. 2011. Publisher Full Text 5. Callaghan S, Donegan S, Pepler S, et al. : Making data a first class scientific output: Data citation and publication by NERC’s environmental data centres. Int J Digit Curation. 2012; 7 (1): 107–113. Publisher Full Text 6. Mobley A, Linder SK, Braeuer R, et al. : A survey on data reproducibility in cancer research provides insights into our limited ability to translate findings from the laboratory to the clinic. PLoS One. 2013; 8 (5): e63221. PubMed Abstract | Publisher Full Text | Free Full Text 7. Pashler H, Harris CR: Is the replicability crisis overblown? three arguments examined. Perspect Psychol Sci. 2012; 7 (6): 531–536. Publisher Full Text 8. Zimmer C: Rise in scientific journal retractions prompts calls for reform. The New York Times . 2012. Reference Source 9. Hiltzik M: Science has lost its way, at a big cost to humanity. Los Angeles Times. 2013. Reference Source 10. Begley CG, Ellis LM: Drug development: Raise standards for preclinical cancer research. Nature. 2012; 483 (7391): 531–533. PubMed Abstract | Publisher Full Text 11. Cyranoski D: Acid-bath stem-cell study under investigation. Nature. 2014. Publisher Full Text 12. Tabuchi H: One author of a startling stem cell study calls for its retraction. The New York Times . 2014. Reference Source 13. Doorn P, Dillo I, Van Horik R: Lies, damned lies and research data: Can data sharing prevent data fraud? Int J Digit Curation. 2013; 8 (1): 229–243. Publisher Full Text 14. Committee L, Committee N, Committee D: Flawed science: The fraudulent research practices of social psychologist diederik stapel. Tech Rep. 2012. Reference Source 15. Wicherts JM: Psychology must learn a lesson from fraud case. Nature. 2011; 480 (7375): 7. PubMed Abstract | Publisher Full Text 16. Drew BT, Gazis R, Cabezas P, et al. : Lost branches on the tree of life. PLoS Biol. 2013; 11 (9): e1001636. PubMed Abstract | Publisher Full Text | Free Full Text 17. Collins FS, Tabak LA: Policy: NIH plans to enhance reproducibility. Nature. 2014; 505 (7485): 612–613. PubMed Abstract | Publisher Full Text | Free Full Text 18. Alsheikh-Ali AA, Qureshi W, Al Mallah MH: Public availability of published research data in high-impact journals. PLoS One. 2011; 6 (9): e24357. PubMed Abstract | Publisher Full Text | Free Full Text 19. Vines TH, Albert AYK, Andrew RL: The availability of research data declines rapidly with article age. Curr Biol. 2014; 24 (1): 94–7. PubMed Abstract | Publisher Full Text 20. Whitlock MC, McPeek MA, Rausher MD: Data archiving. Am Nat. 2010; 175 (2): 145–146. PubMed Abstract | Publisher Full Text 21. Fairbairn DJ: The advent of mandatory data archiving. Evolution. 2011; 65 (1): 1–2. PubMed Abstract | Publisher Full Text 22. Bloom T, Ganley E, Winker M: Data access for the open access literature: PLOS’s data policy. PLoS Biol. 2014; 12 (2): e1001797. Publisher Full Text | Free Full Text 23. Kansa EC, Kansa SW: We all know that a 14 is a sheep: Data publication and professionalism in archaeological communication. J Endocrinol Metab Arch Heritage Studies. 2013; 1 (1): 88–97. Reference Source 24. Piwowar HA, Vision TJ, Whitlock MC: Data archiving is a good investment. Nature. 2011; 473 (7347): 285–285. PubMed Abstract | Publisher Full Text 25. Gray J, Szalay AS, Thakar AR, et al. : Online scientific data curation, publication, and archiving. 2002; 103. Publisher Full Text 26. Waters D, Garrett J: Preserving Digital Information. Report of the Task Force on Archiving of Digital Information. ERIC. 1996. Reference Source 27. Beagrie N: Digital curation for science, digital libraries, and individuals. Int J Digit Curation. 2008; 1 (1): 3–16. Publisher Full Text 28. Office for Civil Rights. Renal resource guide. 2003. Reference Source 29. Center for Research Libraries (U.S.) and OCLC. Trustworthy repositories audit & certification (TRAC) criteria and checklist. Center for Research Libraries; OCLC Online Computer Library Center, Inc Chicago: Dublin, Ohio. 2007. Reference Source 30. Hayden EC: NIH shutdown effects multiply. Nature. 2013. Publisher Full Text 31. Gray J: Jim gray on eScience: A transformed scientific method. In Tony Hey, STewarT Tansley, Stewart, and Kristin Tolle, editors, The fourth paradigm: data-intensive scientific discovery , pages xvii–xxxi. USA. Microsoft Research. 2009. Reference Source 32. Maunsell J: Announcement regarding supplemental material. J Neurosci. 2010; 30 (32): 10599–10600. Reference Source 33. Newman P, Corke P: Data papers — peer reviewed publication of high quality data sets. Int J Rob Res. 2009; 28 (5): 587–587. Publisher Full Text 34. Pfeiffenberger H, Carlson D: “Earth system science data” (ESSD) — a peer reviewed journal for publication of data. D-Lib Magazine. 2011; 17 (1/2). Publisher Full Text 35. Bryan Heidorn P: Shedding light on the dark data in the long tail of science. Libr Trends. 2008; 57 (2): 280–299. Publisher Full Text 36. Fernández-Suárez XM, Rigden DJ, Galperin MY: The 2014 nucleic acids research database issue and an updated NAR online molecular biology database collection. Nucleic Acids Res. 2014; 42 (Database issue): D1–D6. PubMed Abstract | Publisher Full Text | Free Full Text 37. Harris TW, Baran J, Bieri T, et al. : WormBase 2014: new views of curated biology. Nucleic Acids Res. 2014; 42 (Database issue): D789–793. PubMed Abstract | Publisher Full Text | Free Full Text 38. St Pierre SE, Ponting L, Stefancsik R, et al. : FlyBase 102--advanced approaches to interrogating FlyBase. Nucleic Acids Res. 2014; 42 (Database issue): D780–788. PubMed Abstract | Publisher Full Text | Free Full Text 39. Brazma A, Hingamp P, Quackenbush J, et al. : Minimum information about a microarray experiment (MIAME)-toward standards for microarray data. Nat Genet. 2001; 29 (4): 365–371. PubMed Abstract | Publisher Full Text 40. Barrett T, Edgar R: NCBI GEO standards and services for microarray data. Nat Biotechnol. 2006; 24 (12): 1471–1472. PubMed Abstract | Publisher Full Text | Free Full Text 41. FORCE11. Improving future research communication and e-scholarship. 2012. Reference Source 42. Mooney H, Newton M: The anatomy of a data citation: Discovery, reuse, and credit. J Libr schol commun. 2012; 1 (1): eP1035. Publisher Full Text 43. CODATA-ICSTI Task Group on Data Citation Standards and Practices. Out of cite, out of mind: The current state of practice, policy, and technology for the citation of data. Data Sci J. 2013; 12 : 1–75. Publisher Full Text 44. Starr J, Gastl A: isCitedBy: a metadata scheme for DataCite. D-Lib Magazine. 2011; 17 (1). Publisher Full Text 45. Altman M, King G: A proposed standard for the scholarly citation of quantitative data. D-Lib Magazine. 2007; 13 (3/4). Publisher Full Text 46. Global Historical Climate Data Network. Daily summaries station details: OAKLAND MUSEUM, CA US, GHCND:USC00046336. Reference Source 47. Menne MJ, Durre I, Vose RS, et al. : An overview of the global historical climatology network-daily database. J Atmos Ocean Technol. 2012; 29 (7): 897–910. Publisher Full Text 48. Ball A, Duke M: How to cite datasets and link to publications. 2012. Reference Source 49. Pulverer B: A transparent black box. EMBO J. 2010; 29 (23): 3891–3892. PubMed Abstract | Publisher Full Text | Free Full Text 50. Herron DM: Is expert peer review obsolete? A model suggests that post-publication reader review may exceed the accuracy of traditional peer review. Surg Endosc. 2012; 26 (8): 2275–2280. PubMed Abstract | Publisher Full Text 51. Kriegeskorte N, Walther A, Deca D: An emerging consensus for open evaluation: 18 visions for the future of scientific publishing. Front Comput Neurosci. 2012; 6 : 94. PubMed Abstract | Publisher Full Text | Free Full Text 52. Parsons MA, Duerr R, Minster JB: Data citation and peer review. Eos, Transactions American Geophysical Union. 2010; 91 (34): 297–298. Publisher Full Text 53. Diederich F: Are we refereeing ourselves to death? The peer-review system at its limit. Angew Chem Int Ed Engl. 2013; 52 (52): 13828–9. PubMed Abstract | Publisher Full Text 54. Grootveld M, Van Egmond J: editors. Data Reviews, peer-reviewed research data. Number 5 in DANS Studies in Digital Archiving. Data Archiving and Networked Services. 2011. Reference Source 55. Grootveld M, Van Egmond J: Peer-reviewed open research data: Results of a pilot. Int J Digital Curation. 2012; 7 (2): 81–91. Publisher Full Text 56. Parsons MA, Fox PA: Is data publication the right metaphor? Data Sci J. 2013; 12 : WDS32–WDS46. Publisher Full Text 57. Schopf JM: Treating data like software: a case for production quality data. In Proceedings of the 12th ACM/IEEE-CS joint conference on Digital Libraries , JCDL ’12, New York, NY USA, 2012; 153–156. ACM. Publisher Full Text 58. Ram K: Git can facilitate greater reproducibility and increased transparency in science. Source Code Biol Med. 2013; 8 (1): 7. PubMed Abstract | Publisher Full Text | Free Full Text 59. Pradal C, Varoquaux G, Langtangen HP: Publishing scientific software matters. J Comput Sci. 2013; 4 (5): 311–312. Publisher Full Text Comments on this article Comments (7) Version 3 VERSION 3 PUBLISHED 16 Oct 2014 Revised Reader Comment 12 Sep 2017 Judith Winters , University of York, UK 12 Sep 2017 Reader Comment The link you have provided to the journal Internet Archaeology is totally incorrect. The journal URL is http://intarch.ac.uk/ The link you did include is not in any way affiliated to ... Continue reading The link you have provided to the journal Internet Archaeology is totally incorrect. The journal URL is http://intarch.ac.uk/ The link you did include is not in any way affiliated to the journal. The link you have provided to the journal Internet Archaeology is totally incorrect. The journal URL is http://intarch.ac.uk/ The link you did include is not in any way affiliated to the journal. Competing Interests: No competing interests were disclosed. Close Report a concern Reader Comment 01 Dec 2014 Leonardo Candela , ISTI-CNR, Italy 01 Dec 2014 Reader Comment A detailed discussion on Data Journals is here https://www.researchgate.net/publication/268686470_Data_Journals_A_Survey In this piece we are not claiming that "data papers" are the solution to data publishing issues. However, they represent a potential ... Continue reading A detailed discussion on Data Journals is here https://www.researchgate.net/publication/268686470_Data_Journals_A_Survey In this piece we are not claiming that "data papers" are the solution to data publishing issues. However, they represent a potential solution to some issues. A detailed discussion on Data Journals is here https://www.researchgate.net/publication/268686470_Data_Journals_A_Survey In this piece we are not claiming that "data papers" are the solution to data publishing issues. However, they represent a potential solution to some issues. Competing Interests: No competing interests were disclosed. Close Report a concern Comment ADD YOUR COMMENT Version 2 VERSION 2 PUBLISHED 16 May 2014 Revised Discussion is closed on this version, please comment on the latest version above. Reader Comment 22 Aug 2014 Leonardo Candela , ISTI-CNR, Italy 22 Aug 2014 Reader Comment Rather than a comment, I highlight here a potential issue in Reference 3. If I'm not mistaking it should be: Lawrence, B.; Jones, C.; Matthews, B.; Pepler, S. & Callaghan, S. ... Continue reading Rather than a comment, I highlight here a potential issue in Reference 3. If I'm not mistaking it should be: Lawrence, B.; Jones, C.; Matthews, B.; Pepler, S. & Callaghan, S. Citation and Peer Review of Data: Moving Towards Formal Data Publication International Journal of Digital Curation, 2011 , 6 , 4-37 doi:10.2218/ijdc.v6i2.205 Rather than a comment, I highlight here a potential issue in Reference 3. If I'm not mistaking it should be: Lawrence, B.; Jones, C.; Matthews, B.; Pepler, S. & Callaghan, S. Citation and Peer Review of Data: Moving Towards Formal Data Publication International Journal of Digital Curation, 2011 , 6 , 4-37 doi:10.2218/ijdc.v6i2.205 Competing Interests: No competing interests were disclosed. Close Report a concern Discussion is closed on this version, please comment on the latest version above. Version 1 VERSION 1 PUBLISHED 23 Apr 2014 Discussion is closed on this version, please comment on the latest version above. Reader Comment 06 May 2014 Eric Kansa , Open Context (http://opencontext.org), USA 06 May 2014 Reader Comment This is an excellent, and a tremendously useful overview of the issues involved in data publishing. From my perspective in archaeology, the discussion of tDAR and Open Context is useful, ... Continue reading This is an excellent, and a tremendously useful overview of the issues involved in data publishing. From my perspective in archaeology, the discussion of tDAR and Open Context is useful, since these different systems try to serve different needs. You may find this poster by Beth Sheehan comparing these different systems useful as well: http://www.slideshare.net/asist_org/rdap14-comparing-disciplinary-repositories-tdar-vs-open-context One small point of clarification on a minor factual point. The Journal of Open Archaeological Data (JOAD) also lists Open Context ( http://opencontext.org ) as a repository for data, see: http://openarchaeologydata.metajnl.com/about/editorialPolicies#opencontext Similarly, Internet Archaeology also lists Open Context in the same vein: http://intarch.ac.uk/authors/data-papers.html This is an excellent, and a tremendously useful overview of the issues involved in data publishing. From my perspective in archaeology, the discussion of tDAR and Open Context is useful, since these different systems try to serve different needs. You may find this poster by Beth Sheehan comparing these different systems useful as well: http://www.slideshare.net/asist_org/rdap14-comparing-disciplinary-repositories-tdar-vs-open-context One small point of clarification on a minor factual point. The Journal of Open Archaeological Data (JOAD) also lists Open Context ( http://opencontext.org ) as a repository for data, see: http://openarchaeologydata.metajnl.com/about/editorialPolicies#opencontext Similarly, Internet Archaeology also lists Open Context in the same vein: http://intarch.ac.uk/authors/data-papers.html Competing Interests: I direct Open Context (see: http://opencontext.org/about/people), so I have a professional interest in discussions of this project. Close Report a concern Reader Comment 02 May 2014 Konrad Hinsen , Centre de Biophysique Moléculaire (CNRS), France 02 May 2014 Reader Comment First of all, thanks for this article, which is a good introduction to the problems surrounding data publication. One aspect which deserves more attention is the question "What is data?" Or, ... Continue reading First of all, thanks for this article, which is a good introduction to the problems surrounding data publication. One aspect which deserves more attention is the question "What is data?" Or, more precisely, which categories of data should be distinguished with respect to publication? This is related to the last paragraph of this article that starts with "Ultimately, while “data as software” is promising, data is not software." Data is indeed not software - but software is data. I would like to propose the following categories of scientific data: Observational data. This is the "raw input" of science: data from experiments, observations, polls, etc. Machine-readable information generated by humans. This category includes software, input files, workflows, etc. Information for human consumption but also stored electronically could be included as well: articles, drawings, software documentation, etc. Data resulting from a computation: processed observational data, output of simulations, etc. Data in category 1 is not reproducible in any way, and thus needs to be archived and published. Data in category 2 cannot be reproduced exactly by anyone else, but could be regenerated approximately from less complete/precise data by a domain expert. Nevertheless, it should be archived and published as well in order to produce a complete and accurate record of scientific activities. Data in category 3 can be reproduced by computation if the data in categories 1 and 2 is available. It may be convenient to share it nevertheless, in particular if recomputation is expensive, but it's less fundamental than categories 1 and 2. I believe that these categories are more useful than the traditional separation into data, software, and writeup, in particular for questions such as archiving, citing, and updating. In particular, the vague term "dataset" does not distinguish clearly between categories 1 and 3. First of all, thanks for this article, which is a good introduction to the problems surrounding data publication. One aspect which deserves more attention is the question "What is data?" Or, more precisely, which categories of data should be distinguished with respect to publication? This is related to the last paragraph of this article that starts with "Ultimately, while “data as software” is promising, data is not software." Data is indeed not software - but software is data. I would like to propose the following categories of scientific data: Observational data. This is the "raw input" of science: data from experiments, observations, polls, etc. Machine-readable information generated by humans. This category includes software, input files, workflows, etc. Information for human consumption but also stored electronically could be included as well: articles, drawings, software documentation, etc. Data resulting from a computation: processed observational data, output of simulations, etc. Data in category 1 is not reproducible in any way, and thus needs to be archived and published. Data in category 2 cannot be reproduced exactly by anyone else, but could be regenerated approximately from less complete/precise data by a domain expert. Nevertheless, it should be archived and published as well in order to produce a complete and accurate record of scientific activities. Data in category 3 can be reproduced by computation if the data in categories 1 and 2 is available. It may be convenient to share it nevertheless, in particular if recomputation is expensive, but it's less fundamental than categories 1 and 2. I believe that these categories are more useful than the traditional separation into data, software, and writeup, in particular for questions such as archiving, citing, and updating. In particular, the vague term "dataset" does not distinguish clearly between categories 1 and 3. Competing Interests: none Close Report a concern Reader Comment 01 May 2014 Hans Pfeiffenberger , Alfred Wegener Institut, Germany 01 May 2014 Reader Comment Dear authors, your article is a very noteworthy and valuable, broad overview of many of the issues surrounding "data publication". I would like to offer this as recommended reading to anybody ... Continue reading Dear authors, your article is a very noteworthy and valuable, broad overview of many of the issues surrounding "data publication". I would like to offer this as recommended reading to anybody unfamiliar with the field. However, there is one omission and one erroneous/misleading statement which I strongly suggest to correct: In the first paragraph of "Data as the subject of a paper" you list a number of quite representative examples of data journals, but manage to omit the probably first example of a "pure" data journal (with peer review of data), ESSD , founded in 2008. A brief summary of ESSD's rationale and approach was published 2011 in D-Lib Magazine, doi:10.1045/january2011-pfeiffenberger In the second paragraph of "Citability" you write "DOI is neither sufficient nor necessary for citability- if a dataset moves and the DOI is not updated, the citation breaks and, conversely a well-maintained web-address works as well as a DOI." I regard this as strongly misleading, at least for a novice to the domain of publishing or identifiers/DOIs: What typically breaks, sooner or later, is a bookmark with a "normal" URL. The DOI system - which I would characterize as "handle system with a policy" - was set up to work around that fact of life. The contracts data centers (DC) have to sign with "their" (DataCite) DOI registration agency typically contain wording such as: "DC has to ensure that registered content will be available for the entire duration of the agreement." (See "contractual form" , linked to from TIB's "DOI registration" page.) Admittedly, this and other such agreements are difficult to find. By the way, this agreement also adresses the issue of fixity: "Once an item is registered, it may not be altered. If an item is changed, it has to be registered with a new DOI name." Beyond those corrections, I suggest you provide the reader with some pointers about the venues where the ongoing discussions about data publication issues are actually being led. E.g., there are a number of working and interest groups at the Research Data Alliance (not just the one on Data Citation) best regards, Hans Pfeiffenberger Dear authors, your article is a very noteworthy and valuable, broad overview of many of the issues surrounding "data publication". I would like to offer this as recommended reading to anybody unfamiliar with the field. However, there is one omission and one erroneous/misleading statement which I strongly suggest to correct: In the first paragraph of "Data as the subject of a paper" you list a number of quite representative examples of data journals, but manage to omit the probably first example of a "pure" data journal (with peer review of data), ESSD , founded in 2008. A brief summary of ESSD's rationale and approach was published 2011 in D-Lib Magazine, doi:10.1045/january2011-pfeiffenberger In the second paragraph of "Citability" you write "DOI is neither sufficient nor necessary for citability- if a dataset moves and the DOI is not updated, the citation breaks and, conversely a well-maintained web-address works as well as a DOI." I regard this as strongly misleading, at least for a novice to the domain of publishing or identifiers/DOIs: What typically breaks, sooner or later, is a bookmark with a "normal" URL. The DOI system - which I would characterize as "handle system with a policy" - was set up to work around that fact of life. The contracts data centers (DC) have to sign with "their" (DataCite) DOI registration agency typically contain wording such as: "DC has to ensure that registered content will be available for the entire duration of the agreement." (See "contractual form" , linked to from TIB's "DOI registration" page.) Admittedly, this and other such agreements are difficult to find. By the way, this agreement also adresses the issue of fixity: "Once an item is registered, it may not be altered. If an item is changed, it has to be registered with a new DOI name." Beyond those corrections, I suggest you provide the reader with some pointers about the venues where the ongoing discussions about data publication issues are actually being led. E.g., there are a number of working and interest groups at the Research Data Alliance (not just the one on Data Citation) best regards, Hans Pfeiffenberger Competing Interests: I happen to be the founder and chief editor of ESSD Close Report a concern Reader Comment 30 Apr 2014 Chris HJ Hartgerink , Liberate Science GmbH, Germany 30 Apr 2014 Reader Comment Possibly of interest to your paper is dat , a program in development to provide version control of datasets (more so than git is able to). It has received funding recently ... Continue reading Possibly of interest to your paper is dat , a program in development to provide version control of datasets (more so than git is able to). It has received funding recently from the Knight Foundation (see here ) and is something worth looking out for in terms of data sharing, but more importantly, preservation and logging. Thank you for writing this — it provides a succinct introduction to an important issue. Possibly of interest to your paper is dat , a program in development to provide version control of datasets (more so than git is able to). It has received funding recently from the Knight Foundation (see here ) and is something worth looking out for in terms of data sharing, but more importantly, preservation and logging. Thank you for writing this — it provides a succinct introduction to an important issue. Competing Interests: No competing interests were disclosed. Close Report a concern Discussion is closed on this version, please comment on the latest version above. Author details Author details 1 California Digital Library, University of California Office of the President, Oakland, CA, 94612, USA Competing interests No competing interests were disclosed. Grant information JK is supported by a Council on Library and Information Resources/Digital Library Foundation Postdoctoral Fellowship in Data Curation for the Sciences and Social Sciences funded by the California Digital Library and the Alfred P. Sloan Foundation. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Article Versions (3) version 3 Revised Published: 16 Oct 2014, 3:94 https://doi.org/10.12688/f1000research.3979.3 version 2 Revised Published: 16 May 2014, 3:94 https://doi.org/10.12688/f1000research.3979.2 version 1 Published: 23 Apr 2014, 3:94 https://doi.org/10.12688/f1000research.3979.1 Copyright © 2014 Kratz J and Strasser C. This is an open access article distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. Data associated with the article are available under the terms of the Creative Commons Zero "No rights reserved" data waiver (CC0 1.0 Public domain dedication). Download Export To Sciwheel Bibtex EndNote ProCite Ref. Manager (RIS) Sente metrics Views Downloads F1000Research - - PubMed Central info_outline Data from PMC are received and updated monthly. - - Citations open_in_new 0 open_in_new 0 open_in_new SEE MORE DETAILS CITE how to cite this article Kratz J and Strasser C. Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.12688/f1000research.3979.3 ) NOTE: If applicable, it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS track receive updates on this article Track an article to receive email alerts on any updates to this article. TRACK THIS ARTICLE Share Open Peer Review Current Reviewer Status: ? Key to Reviewer Statuses VIEW HIDE Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions Version 3 VERSION 3 PUBLISHED 16 Oct 2014 Revised Views 0 Cite How to cite this report: Parsons M. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.5878.r6447 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v3#referee-response-6447 NOTE: it is important to ensure the information in square brackets after the title is included in this citation. Close Copy Citation Details Reviewer Report 06 Nov 2014 Mark Parsons , Research Data Alliance, Troy, NY, USA Approved VIEWS 0 https://doi.org/10.5256/f1000research.5878.r6447 A nice rewrite and a very much improved paper, especially since it is now properly classified as a review article. Just a few small corrections listed below. Page 4, Para 5: "Writing a request to the creator should [very rarely] be part ... Continue reading READ ALL A nice rewrite and a very much improved paper, especially since it is now properly classified as a review article. Just a few small corrections listed below. Page 4, Para 5: "Writing a request to the creator should [very rarely] be part of the process" As noted before creator permission is sometimes legitimate. Page 5, para 2: "The most familiar kind of data publication is a traditional journal article accompanied by underlying data. " [citation needed] or change the sentence. Page 5, para 7 "Data papers are predated by an approach that Lawrence et al. (2011) call data publication by proxy..." This is not true. As Hans Pfeiffenberger notes, ESSD dates back to 2008. Indeed I wouldn't be surprised if Lawrence chatted a bit with ESSD editors, Pfeiffenberger and Carlson, in preparing his paper. Page 6, para 1 NSIDC does do external scientific reviews but they only go outside when they don’t have expertise in house. So it's sort of a combined approach. A quibble, but they pride themselves on in-house scientific expertise and engagement. Page 6 para 2: This paragraph is a little confused. Domain repositories don’t usually serve interdisciplinary use very well, but I don’t see how it’s necessarily bad to be distributed. What do you mean by publishing the whole research story? No one entity can do that. Competing Interests: No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Parsons M. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.5878.r6447 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v3#referee-response-6447 NOTE: it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS Report a concern Respond or Comment COMMENT ON THIS REPORT Version 2 VERSION 2 PUBLISHED 16 May 2014 Revised Views 0 Cite How to cite this report: Dillo I. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4518.r4540 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v2#referee-response-4540 NOTE: it is important to ensure the information in square brackets after the title is included in this citation. Close Copy Citation Details Reviewer Report 10 Jun 2014 Ingrid Dillo , Data Archiving and Networking Services (DANS), The Hague, The Netherlands Approved VIEWS 0 https://doi.org/10.5256/f1000research.4518.r4540 The article focuses on a topic that receives a lot of interest these days. Therefore it is very timely. The article provides a useful and valuable overview of the current state of affairs and the ongoing debate. The title does ... Continue reading READ ALL The article focuses on a topic that receives a lot of interest these days. Therefore it is very timely. The article provides a useful and valuable overview of the current state of affairs and the ongoing debate. The title does justice to the content of the article. So does the abstract. This is the second version of the article. I do not see many changes in the text based on the earlier critical comments made by Mark Parsons and Peter Fox. The overview is very informative for everyone who needs a quick introduction into the subject. I do miss the opinion of the authors themselves on the issues at hand and on the quoted suggestions by others. This would have been appropriate in a concluding paragraph. Detailed comments: In the Introduction I miss a clear link between data publishing and data citation and creating the possibility for researchers to receive academic credits for their work on data. This academic credit is crucial as an incentive for researchers to put valuable time and effort in sharing their data. In the paragraph Why publish data? a reference to the Dutch fraud cases might be useful, as these cases got a lot of international attention and more or less triggered the discussion in the Netherlands with respect to research data management, long term preservation of data and data publishing and citation. A reference could be: Doorn P, Dillo I, van Horik R: Lies, Damned Lies and Research Data: Can Data Sharing Prevent Data Fraud? International Journal of Digital Curation. 2013; 8 (1): 229-243 http://dx.doi.org/10.2218/ijdc.v8i1.256 In the paragraph Types of data publication a threefold model is introduced to categorize data publications. It is not clear how this model relates to the terminology and categorisation presented in the introduction. This could be somewhat confusing for the reader. Furthermore, there are of course many other models available, e.g. that of the The Data Publication Pyramid, developed on the basis of the Jim Gray pyramid, to express the different manifestation forms that research data can have in the publication process: Reilly S, Schallier W, Schrimpf S, et al. : Report on integration of data and publications. October 2011. Located at: http://www.stm-assoc.org/2011_12_5_ODE_Report_On_Integration_of_Data_and_Publications.pdf Or the model presented in the report: Costas, R., Meijer, I., Zahedi, Z. and Wouters, P. (2013). The Value of Research Data - Metrics for datasets from a cultural and technical point of view. A Knowledge Exchange Report, available from www.knowledge-exchange.info/datametrics With respect to trustworthy digital repositories, I would like to add a few comments. First of all, in Europe a European Framework for Audit and Certification of Digital Repositories is emerging. It contains three certification standards (DSA, DIN31644/NESTOR seal and ISO13636) and three levels of certification (basic, extended and formal) see: http://www.trusteddigitalrepository.eu/Site/Trusted%20Digital%20Repository.html Of these three standards, only DSA has been up and running for some time now ,with 31 seals awarded and 30 ongoing self-assessments at this moment. The NESTOR seal has become available only very recently and the ISO standard is not yet officially available. The accompanying ISO 16919 standard: Requirements for bodies providing audit and certification of candidate trustworthy digital repositories, has been published very recently and now the ISO organization needs to be set up in the different countries, including the training of national auditors. The audits done by CRL are not fully official, since CRL is no formal ISO accreditation body. In Europe we see a growing interest in TDRs, coming from funders who want to push open data and data sharing and demand the deposit of publicly funded data in long term TDRs. Furthermore European research infrastructures and projects are also looking more and more into the issue of trust hen it comes to data sharing and a groeing number of them is incorporating (parts of) the DSA guidelines into there repositories and policies (e.g. CESSDA, CLARIN, EUDAT). Yet another certification procedure is offered by the ICSU/WDS to repositories that aim to become a member of the World Data System. See: https://www.icsu-wds.org/community/membership/certification The certification of TDRs could also help publishers/editorial boards with Data Availability Policies to point their authors to the right repositories for the long-term storage of their data. Competing Interests: No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Dillo I. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4518.r4540 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v2#referee-response-4540 NOTE: it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS Report a concern Respond or Comment COMMENT ON THIS REPORT Views 0 Cite How to cite this report: Costello M. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4518.r4543 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v2#referee-response-4543 NOTE: it is important to ensure the information in square brackets after the title is included in this citation. Close Copy Citation Details Reviewer Report 28 May 2014 Mark Costello , Institute of Marine Science, University of Auckland, Auckland, New Zealand Approved VIEWS 0 https://doi.org/10.5256/f1000research.4518.r4543 Having made some similar comments myself I must agree with this review. But a few points may merit amendment: Abstract: Note that what 'publication' means is the same as in print as in digital form. It does not imply peer-review or editorial ... Continue reading READ ALL Having made some similar comments myself I must agree with this review. But a few points may merit amendment: Abstract: Note that what 'publication' means is the same as in print as in digital form. It does not imply peer-review or editorial oversight in either format. Citability: Yes, data citations are important but some datasets and web-based resources do not show how they should be cited, some journals do not allow citations to web resources in the Reference list, and even were both possible, too many authors neglect to cite actual datasets and instead cite a web site (which may have many datasets) or a related print paper. I agree that a DOI is not enough and only permanent if it is updated when documents are moved. A full author-tile-publisher citation as you suggest is more informative and human readable. I do not think it is problematic to cite parts of datasets. Pages and chapters in books are already cited for example. In most datasets it is also possible to identify individual dat records. Also, the actual data used could be provided in an Appendix so the reader is left in no doubt. Neither do I think 'versioning' is a problem. Where new data are added (e.g. to a time-series) then they comprise a new dataset, as they would if published in print. Where many corrections are made they a dataset can be treated like a paper; i.e. the original can be 'retracted' and replaced, or the new version be published with the metadata stating that it is more accurate. You mention venues for peer-reviewed data papers. For this article to advance previous articles, perhaps it could expand on these venues and how they manage the details of the peer-review process? I have published a few papers you may find of interest: Costello MJ, Wieczorek J. 2014. Best practice for biodiversity data management and publication. Biological Conservation, 173, 68-73. http://www.vliz.be/en/imis?module=ref&refid=234968 Costello MJ, Appeltans W, Bailly N, Berendsohn WG, de Jong Y, Edwards M, Froese R, Huettmann F, Los W, Mees J, Segers H, Bisby FA. 2014. Strategies for the sustainability of online open-access biodiversity databases. Biological Conservation 173, 155-165. http://www.marinebiology.ugent.be/component/imis/?module=ref&refid=230520 Costello MJ, Michener WK, Gahegan M, Zhang Z-Q, Bourne P. 2013. Data should be published, cited and peer-reviewed. Trends in Ecology and Evolution 28 (8) , 454-461. http://dx.doi.org/10.1016/j.tree.2013.05.002 Costello, M.J., Vanden Berghe E. 2006. “Ocean Biodiversity Informatics” enabling a new era in marine biology research and management. Marine Ecology Progress Series 316, 203-214. http://www.int-res.com/abstracts/meps/v316/ Costello MJ, Michener WK, Gahegan M, Zhang Z-Q, Bourne P, Chavan V. 2012. Quality assurance and intellectual property rights in advancing biodiversity data publications. ver. 1.0, Copenhagen: Global Biodiversity Information Facility, Pp. 33, ISBN: 87‐92020‐49‐6. Accessible at http://links.gbif.org/qa_ipr_advancing_biodiversity_data_publishing_en_v1 . Competing Interests: No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Costello M. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4518.r4543 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v2#referee-response-4543 NOTE: it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS Report a concern Respond or Comment COMMENT ON THIS REPORT Version 1 VERSION 1 PUBLISHED 23 Apr 2014 Views 0 Cite How to cite this report: Parsons M and Fox P. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4264.r4541 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v1#referee-response-4541 NOTE: it is important to ensure the information in square brackets after the title is included in this citation. Close Copy Citation Details Reviewer Report 06 May 2014 Mark Parsons , Research Data Alliance, Troy, NY, USA Peter Fox , Rensselaer Polytechnic Institute, Troy, NY, USA Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.4264.r4541 General Comments : Note: This review was written by Parsons and accepted (with some modification) by Fox. Insights likely come from conversations between Fox and Parsons, errors from Parsons . I am very glad the authors wrote this essay. It is a well-written, needed, ... Continue reading READ ALL General Comments : Note: This review was written by Parsons and accepted (with some modification) by Fox. Insights likely come from conversations between Fox and Parsons, errors from Parsons . I am very glad the authors wrote this essay. It is a well-written, needed, and useful summary of the current status of “data publication” from a certain perspective. The authors, however, need to be bolder and more analytical. This is an opinion piece, yet I see little opinion. A certain view is implied by the organization of the paper and the references chosen, but they could be more explicit. The paper would be both more compelling and useful to a broad readership if the authors moved beyond providing a simple summary of the landscape and examined why there is controversy in some areas and then use the evidence they have compiled to suggest a path forward. They need to be more forthright in saying what data publication means to them, or what parts of it they do not deal with. Are they satisfied with the Lawrence et al. definition? Do they accept the critique of Parsons and Fox? What is the scope of their essay? The authors take a rather narrow view of data publication, which I think hinders their analyses. They describe three types of (digital) data publication: Data as a supplement to an article; data as the subject of a paper; and data independent of a paper. The first two types are relatively new and they represent very little of the data actually being published or released today. The last category, which is essentially an “other” category, is rich in its complexity and encompasses the vast majority of data released. I was disappointed that the examples of this type were only the most bare-bones (Zenodo and Figshare). I think a deeper examination of this third category and its complexity would help the authors better characterize the current landscape and suggest paths forward. Some questions the authors might consider: Are these really the only three models in consideration or does the publication model overstate a consensus around a certain type of data publication? Why are there different models and which approach is better for different situations? Do they have different business models or imply different social contracts? Might it also be worthy of typing “publishers” instead of “publications”? For example, do domain repositories vs. institutional repositories vs. publishers address the issues differently? Are these models sustaining models or just something to get us through the next 5-10 years while we really figure it out? I think this oversimplification inhibited some deeper analysis in other areas as well. I would like to see more examination of the validation requirement beyond the lens of peer review, and I would like a deeper examination of incentives and credit beyond citation. I thought the validation section of the paper was very relevant, but somewhat light. I like the choice of the term validation as more accurate than “quality” and it fits quite well with Callaghan’s useful distinction between technical and scientific review, but I think the authors overemphasize the peer-review style approach. The authors rightly argue that “peer-review” is where the publication metaphor leads us, but it may be a false path. They overstate some difficulties of peer-review (No-one looks at every data value? No, they use statistics, visualization, and other techniques.) while not fully considering who is responsible for what. We need a closer examination of different roles and who are appropriate validators (not necessarily conventional peers). The narrowly defined models of data publication may easily allow for a conventional peer-review process, but it is much more complex in the real-world “other” category. The authors discuss some of this in what they call “independent data validation,” but they don’t draw any conclusions. Only the simplest of research data collections are validated only by the original creators. More often there are teams working together to develop experiments, sampling protocols, algorithms, etc. There are additional teams who assess, calibrate, and revise the data as they are collected and assembled. The authors discuss some of this in their examples like the PDS and tDAR, but I wish they were more analytical and offered an opinion on the way forward. Are there emerging practices or consensus in these team-based schemes? The level of service concept illustrated by Open Context may be one such area. Would formalizing or codifying some of these processes accomplish the same as peer-review or more? What is the role of the curator or data scientist in all of this? Given the authors’s backgrounds, I was surprised this role was not emphasized more. Finally, I think it is a mistake for science review to be the main way to assess reuse value. It has been shown time and again that data end up being used effectively (and valued) in ways that original experts never envisioned or even thought valid. The discussion of data citation was good and captured the state of the art well, but again I would have liked to see some views on a way forward. Have we solved the basic problem and are now just dealing with edge cases? Is the “just-in-time identifier” the way to go? What are the implications? Will the more basic solutions work in the interim? More critically, are we overemphasizing the role of citation to provide academic credit? I was gratified that the authors referenced the Parsons and Fox paper which questions the whole data publication metaphor, but I was surprised that they only discussed the “data as software” alternative metaphor. That is a useful metaphor, but I think the ecosystem metaphor has broader acceptance. I mention this because the authors critique the software metaphor because “using it to alter or affect the academic reward system is a tricky prospect”. Yet there is little to suggest that data publication and corresponding citation alters that system either. Indeed there is little if any evidence that data publication and citation incentivize data sharing or stewardship. As Christine Borgman suggests, we need to look more closely at who we are trying to incentivize to do what . There is no reason to assume it follows the same model as research literature publication. It may be beyond the scope of this paper to fully examine incentive structures, but it at least needs to be acknowledged that building on the current model doesn’t seem to be working. Finally, what is the takeaway message from this essay? It ends rather abruptly with no summary, no suggested directions or immediate challenges to overcome, no call to action, no indications of things we should stop trying, and only brief mention of alternative perspectives. What do the authors want us to take away from this paper? Overall though, this is a timely and needed essay. It is well researched and nicely written with rich metaphor. With modifications addressing the detailed comments below and better recognizing the complexity of the current data publication landscape, this will be a worthwhile review paper. With more significant modification where the authors dig deeper into the complexities and controversies and truly grapple with their implications to suggest a way forward, this could be a very influential paper. It is possible that the definitions of “publication” and “peer-review” need not be just stretched but changed or even rejected. Detailed comments: The whole paper needs a quick copy edit. There are a few typos, missing words, and wrong verb tenses. Note the word “data” is a plural noun. E.g., Data are not software, nor are they literature. (NSICD, instead of NSIDC) Page 2, para 2: “citability is addressed by assigning a PID.” This is not true, as the authors discuss on page 4, para 4. Indeed, page 4, para 4 seems to contradict itself. Citation is more than a locator/identifier In the discussion of “Data independent of any paper” it is worth noting that there may often be linkages between these data and myriad papers. Indeed a looser concept of a data paper has existed for some time, where researchers request a citation to a paper even though it is not the data nor fully describes the data (e.g the CRU temp records) Page 4, para 1: I’m not sure it’s entirely true that published data cannot involve requesting permission. In past work with Indigenous knowledge holders, they were willing to publish summary data and then provide the details when satisfied the use was appropriate and not exploitive. I think those data were “published” as best they could be. A nit, perhaps, but it highlights that there are few if any hard and fast rules about data publication. Page 4, para 2: You may also want to mention the WDS certification effort, which is combining with the DSA via an RDA Working Group: Page 4, para 2: The joint declaration of data citation principles involved many more organizations than Force11, CODATA, and DCC. Please credit them all (maybe in a footnote). The glory of the effort was that it was truly a joint effort across many groups. There is no leader. Force11 was primarily a convener. Page 4, para 6: The deep citation approach recommended by ESIP is not to just to list variables or a range of data. It is to identify a “structural index” for the data and to use this to reference subsets. In Earth science this structural index is often space and time, but many other indices are possible--location in a gene sequence, file type, variable, bandwidth, viewing angle, etc. It is not just for “straightforward” data sets. Page 5, para 5: I take issue with the statement that few repositories provide scientific review. I can think of a couple dozen that do just off the top of my head, and I bet most domain repositories have some level of science review. The “scientists” may not always be in house, but the repository is a team facilitator. See my general comments. Page 5, para 10: The PDS system is only unusual in that it is well documented and advertised. As mentioned, this team style approach is actually fairly common Page 6, para 3: Parsons and Fox don’t just argue that the data publication metaphor is limiting. They also say it is misleading. That should be acknowledged at least, if not actively grappled with. Competing Interests: No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however we have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Parsons M and Fox P. Reviewer Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4264.r4541 ) The direct URL for this report is: https://f1000research.com/articles/3-94/v1#referee-response-4541 NOTE: it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS Report a concern Author Response 12 May 2014 John Kratz , California Digital Library, University of California Office of the President, Oakland, CA, 94612, USA 12 May 2014 Author Response Thank you for refereeing our paper and thank you especially for delivering your report so quickly. We submitted the paper as a review article, not an opinion piece, and it was ... Continue reading Thank you for refereeing our paper and thank you especially for delivering your report so quickly. We submitted the paper as a review article, not an opinion piece, and it was reclassified somewhere along the way. I contacted an editor at F1000 about the issue, and I believe it will be switched back shortly. While there is undoubtedly a viewpoint inherent in the way we have organized the manuscript, it was our intention to deliver a timely summary of the current landscape as a foundation for future thinking, not to offer prescriptions or to endorse particular approaches. We have no shortage of opinions about data publication, and a true opinion piece may follow at some point, but our aim here was to remain fairly neutral. I think the paper you are asking for would also be valuable, but it's an entirely different paper from the one we have written. That said, your report is full of suggestions for expansion of analysis and clarification of scope that would absolutely improve the paper (e.g. the question of why some issues resist consensus more than others is an excellent one), and we will certainly address them in the next version. Thank you for refereeing our paper and thank you especially for delivering your report so quickly. We submitted the paper as a review article, not an opinion piece, and it was reclassified somewhere along the way. I contacted an editor at F1000 about the issue, and I believe it will be switched back shortly. While there is undoubtedly a viewpoint inherent in the way we have organized the manuscript, it was our intention to deliver a timely summary of the current landscape as a foundation for future thinking, not to offer prescriptions or to endorse particular approaches. We have no shortage of opinions about data publication, and a true opinion piece may follow at some point, but our aim here was to remain fairly neutral. I think the paper you are asking for would also be valuable, but it's an entirely different paper from the one we have written. That said, your report is full of suggestions for expansion of analysis and clarification of scope that would absolutely improve the paper (e.g. the question of why some issues resist consensus more than others is an excellent one), and we will certainly address them in the next version. Competing Interests: I am an author of the selected paper. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 12 May 2014 John Kratz , California Digital Library, University of California Office of the President, Oakland, CA, 94612, USA 12 May 2014 Author Response Thank you for refereeing our paper and thank you especially for delivering your report so quickly. We submitted the paper as a review article, not an opinion piece, and it was ... Continue reading Thank you for refereeing our paper and thank you especially for delivering your report so quickly. We submitted the paper as a review article, not an opinion piece, and it was reclassified somewhere along the way. I contacted an editor at F1000 about the issue, and I believe it will be switched back shortly. While there is undoubtedly a viewpoint inherent in the way we have organized the manuscript, it was our intention to deliver a timely summary of the current landscape as a foundation for future thinking, not to offer prescriptions or to endorse particular approaches. We have no shortage of opinions about data publication, and a true opinion piece may follow at some point, but our aim here was to remain fairly neutral. I think the paper you are asking for would also be valuable, but it's an entirely different paper from the one we have written. That said, your report is full of suggestions for expansion of analysis and clarification of scope that would absolutely improve the paper (e.g. the question of why some issues resist consensus more than others is an excellent one), and we will certainly address them in the next version. Thank you for refereeing our paper and thank you especially for delivering your report so quickly. We submitted the paper as a review article, not an opinion piece, and it was reclassified somewhere along the way. I contacted an editor at F1000 about the issue, and I believe it will be switched back shortly. While there is undoubtedly a viewpoint inherent in the way we have organized the manuscript, it was our intention to deliver a timely summary of the current landscape as a foundation for future thinking, not to offer prescriptions or to endorse particular approaches. We have no shortage of opinions about data publication, and a true opinion piece may follow at some point, but our aim here was to remain fairly neutral. I think the paper you are asking for would also be valuable, but it's an entirely different paper from the one we have written. That said, your report is full of suggestions for expansion of analysis and clarification of scope that would absolutely improve the paper (e.g. the question of why some issues resist consensus more than others is an excellent one), and we will certainly address them in the next version. Competing Interests: I am an author of the selected paper. Close Report a concern COMMENT ON THIS REPORT Comments on this article Comments (7) Version 3 VERSION 3 PUBLISHED 16 Oct 2014 Revised Reader Comment 12 Sep 2017 Judith Winters , University of York, UK 12 Sep 2017 Reader Comment The link you have provided to the journal Internet Archaeology is totally incorrect. The journal URL is http://intarch.ac.uk/ The link you did include is not in any way affiliated to ... Continue reading The link you have provided to the journal Internet Archaeology is totally incorrect. The journal URL is http://intarch.ac.uk/ The link you did include is not in any way affiliated to the journal. The link you have provided to the journal Internet Archaeology is totally incorrect. The journal URL is http://intarch.ac.uk/ The link you did include is not in any way affiliated to the journal. Competing Interests: No competing interests were disclosed. Close Report a concern Reader Comment 01 Dec 2014 Leonardo Candela , ISTI-CNR, Italy 01 Dec 2014 Reader Comment A detailed discussion on Data Journals is here https://www.researchgate.net/publication/268686470_Data_Journals_A_Survey In this piece we are not claiming that "data papers" are the solution to data publishing issues. However, they represent a potential ... Continue reading A detailed discussion on Data Journals is here https://www.researchgate.net/publication/268686470_Data_Journals_A_Survey In this piece we are not claiming that "data papers" are the solution to data publishing issues. However, they represent a potential solution to some issues. A detailed discussion on Data Journals is here https://www.researchgate.net/publication/268686470_Data_Journals_A_Survey In this piece we are not claiming that "data papers" are the solution to data publishing issues. However, they represent a potential solution to some issues. Competing Interests: No competing interests were disclosed. Close Report a concern Comment ADD YOUR COMMENT Version 2 VERSION 2 PUBLISHED 16 May 2014 Revised Discussion is closed on this version, please comment on the latest version above. Reader Comment 22 Aug 2014 Leonardo Candela , ISTI-CNR, Italy 22 Aug 2014 Reader Comment Rather than a comment, I highlight here a potential issue in Reference 3. If I'm not mistaking it should be: Lawrence, B.; Jones, C.; Matthews, B.; Pepler, S. & Callaghan, S. ... Continue reading Rather than a comment, I highlight here a potential issue in Reference 3. If I'm not mistaking it should be: Lawrence, B.; Jones, C.; Matthews, B.; Pepler, S. & Callaghan, S. Citation and Peer Review of Data: Moving Towards Formal Data Publication International Journal of Digital Curation, 2011 , 6 , 4-37 doi:10.2218/ijdc.v6i2.205 Rather than a comment, I highlight here a potential issue in Reference 3. If I'm not mistaking it should be: Lawrence, B.; Jones, C.; Matthews, B.; Pepler, S. & Callaghan, S. Citation and Peer Review of Data: Moving Towards Formal Data Publication International Journal of Digital Curation, 2011 , 6 , 4-37 doi:10.2218/ijdc.v6i2.205 Competing Interests: No competing interests were disclosed. Close Report a concern Discussion is closed on this version, please comment on the latest version above. Version 1 VERSION 1 PUBLISHED 23 Apr 2014 Discussion is closed on this version, please comment on the latest version above. Reader Comment 06 May 2014 Eric Kansa , Open Context (http://opencontext.org), USA 06 May 2014 Reader Comment This is an excellent, and a tremendously useful overview of the issues involved in data publishing. From my perspective in archaeology, the discussion of tDAR and Open Context is useful, ... Continue reading This is an excellent, and a tremendously useful overview of the issues involved in data publishing. From my perspective in archaeology, the discussion of tDAR and Open Context is useful, since these different systems try to serve different needs. You may find this poster by Beth Sheehan comparing these different systems useful as well: http://www.slideshare.net/asist_org/rdap14-comparing-disciplinary-repositories-tdar-vs-open-context One small point of clarification on a minor factual point. The Journal of Open Archaeological Data (JOAD) also lists Open Context ( http://opencontext.org ) as a repository for data, see: http://openarchaeologydata.metajnl.com/about/editorialPolicies#opencontext Similarly, Internet Archaeology also lists Open Context in the same vein: http://intarch.ac.uk/authors/data-papers.html This is an excellent, and a tremendously useful overview of the issues involved in data publishing. From my perspective in archaeology, the discussion of tDAR and Open Context is useful, since these different systems try to serve different needs. You may find this poster by Beth Sheehan comparing these different systems useful as well: http://www.slideshare.net/asist_org/rdap14-comparing-disciplinary-repositories-tdar-vs-open-context One small point of clarification on a minor factual point. The Journal of Open Archaeological Data (JOAD) also lists Open Context ( http://opencontext.org ) as a repository for data, see: http://openarchaeologydata.metajnl.com/about/editorialPolicies#opencontext Similarly, Internet Archaeology also lists Open Context in the same vein: http://intarch.ac.uk/authors/data-papers.html Competing Interests: I direct Open Context (see: http://opencontext.org/about/people), so I have a professional interest in discussions of this project. Close Report a concern Reader Comment 02 May 2014 Konrad Hinsen , Centre de Biophysique Moléculaire (CNRS), France 02 May 2014 Reader Comment First of all, thanks for this article, which is a good introduction to the problems surrounding data publication. One aspect which deserves more attention is the question "What is data?" Or, ... Continue reading First of all, thanks for this article, which is a good introduction to the problems surrounding data publication. One aspect which deserves more attention is the question "What is data?" Or, more precisely, which categories of data should be distinguished with respect to publication? This is related to the last paragraph of this article that starts with "Ultimately, while “data as software” is promising, data is not software." Data is indeed not software - but software is data. I would like to propose the following categories of scientific data: Observational data. This is the "raw input" of science: data from experiments, observations, polls, etc. Machine-readable information generated by humans. This category includes software, input files, workflows, etc. Information for human consumption but also stored electronically could be included as well: articles, drawings, software documentation, etc. Data resulting from a computation: processed observational data, output of simulations, etc. Data in category 1 is not reproducible in any way, and thus needs to be archived and published. Data in category 2 cannot be reproduced exactly by anyone else, but could be regenerated approximately from less complete/precise data by a domain expert. Nevertheless, it should be archived and published as well in order to produce a complete and accurate record of scientific activities. Data in category 3 can be reproduced by computation if the data in categories 1 and 2 is available. It may be convenient to share it nevertheless, in particular if recomputation is expensive, but it's less fundamental than categories 1 and 2. I believe that these categories are more useful than the traditional separation into data, software, and writeup, in particular for questions such as archiving, citing, and updating. In particular, the vague term "dataset" does not distinguish clearly between categories 1 and 3. First of all, thanks for this article, which is a good introduction to the problems surrounding data publication. One aspect which deserves more attention is the question "What is data?" Or, more precisely, which categories of data should be distinguished with respect to publication? This is related to the last paragraph of this article that starts with "Ultimately, while “data as software” is promising, data is not software." Data is indeed not software - but software is data. I would like to propose the following categories of scientific data: Observational data. This is the "raw input" of science: data from experiments, observations, polls, etc. Machine-readable information generated by humans. This category includes software, input files, workflows, etc. Information for human consumption but also stored electronically could be included as well: articles, drawings, software documentation, etc. Data resulting from a computation: processed observational data, output of simulations, etc. Data in category 1 is not reproducible in any way, and thus needs to be archived and published. Data in category 2 cannot be reproduced exactly by anyone else, but could be regenerated approximately from less complete/precise data by a domain expert. Nevertheless, it should be archived and published as well in order to produce a complete and accurate record of scientific activities. Data in category 3 can be reproduced by computation if the data in categories 1 and 2 is available. It may be convenient to share it nevertheless, in particular if recomputation is expensive, but it's less fundamental than categories 1 and 2. I believe that these categories are more useful than the traditional separation into data, software, and writeup, in particular for questions such as archiving, citing, and updating. In particular, the vague term "dataset" does not distinguish clearly between categories 1 and 3. Competing Interests: none Close Report a concern Reader Comment 01 May 2014 Hans Pfeiffenberger , Alfred Wegener Institut, Germany 01 May 2014 Reader Comment Dear authors, your article is a very noteworthy and valuable, broad overview of many of the issues surrounding "data publication". I would like to offer this as recommended reading to anybody ... Continue reading Dear authors, your article is a very noteworthy and valuable, broad overview of many of the issues surrounding "data publication". I would like to offer this as recommended reading to anybody unfamiliar with the field. However, there is one omission and one erroneous/misleading statement which I strongly suggest to correct: In the first paragraph of "Data as the subject of a paper" you list a number of quite representative examples of data journals, but manage to omit the probably first example of a "pure" data journal (with peer review of data), ESSD , founded in 2008. A brief summary of ESSD's rationale and approach was published 2011 in D-Lib Magazine, doi:10.1045/january2011-pfeiffenberger In the second paragraph of "Citability" you write "DOI is neither sufficient nor necessary for citability- if a dataset moves and the DOI is not updated, the citation breaks and, conversely a well-maintained web-address works as well as a DOI." I regard this as strongly misleading, at least for a novice to the domain of publishing or identifiers/DOIs: What typically breaks, sooner or later, is a bookmark with a "normal" URL. The DOI system - which I would characterize as "handle system with a policy" - was set up to work around that fact of life. The contracts data centers (DC) have to sign with "their" (DataCite) DOI registration agency typically contain wording such as: "DC has to ensure that registered content will be available for the entire duration of the agreement." (See "contractual form" , linked to from TIB's "DOI registration" page.) Admittedly, this and other such agreements are difficult to find. By the way, this agreement also adresses the issue of fixity: "Once an item is registered, it may not be altered. If an item is changed, it has to be registered with a new DOI name." Beyond those corrections, I suggest you provide the reader with some pointers about the venues where the ongoing discussions about data publication issues are actually being led. E.g., there are a number of working and interest groups at the Research Data Alliance (not just the one on Data Citation) best regards, Hans Pfeiffenberger Dear authors, your article is a very noteworthy and valuable, broad overview of many of the issues surrounding "data publication". I would like to offer this as recommended reading to anybody unfamiliar with the field. However, there is one omission and one erroneous/misleading statement which I strongly suggest to correct: In the first paragraph of "Data as the subject of a paper" you list a number of quite representative examples of data journals, but manage to omit the probably first example of a "pure" data journal (with peer review of data), ESSD , founded in 2008. A brief summary of ESSD's rationale and approach was published 2011 in D-Lib Magazine, doi:10.1045/january2011-pfeiffenberger In the second paragraph of "Citability" you write "DOI is neither sufficient nor necessary for citability- if a dataset moves and the DOI is not updated, the citation breaks and, conversely a well-maintained web-address works as well as a DOI." I regard this as strongly misleading, at least for a novice to the domain of publishing or identifiers/DOIs: What typically breaks, sooner or later, is a bookmark with a "normal" URL. The DOI system - which I would characterize as "handle system with a policy" - was set up to work around that fact of life. The contracts data centers (DC) have to sign with "their" (DataCite) DOI registration agency typically contain wording such as: "DC has to ensure that registered content will be available for the entire duration of the agreement." (See "contractual form" , linked to from TIB's "DOI registration" page.) Admittedly, this and other such agreements are difficult to find. By the way, this agreement also adresses the issue of fixity: "Once an item is registered, it may not be altered. If an item is changed, it has to be registered with a new DOI name." Beyond those corrections, I suggest you provide the reader with some pointers about the venues where the ongoing discussions about data publication issues are actually being led. E.g., there are a number of working and interest groups at the Research Data Alliance (not just the one on Data Citation) best regards, Hans Pfeiffenberger Competing Interests: I happen to be the founder and chief editor of ESSD Close Report a concern Reader Comment 30 Apr 2014 Chris HJ Hartgerink , Liberate Science GmbH, Germany 30 Apr 2014 Reader Comment Possibly of interest to your paper is dat , a program in development to provide version control of datasets (more so than git is able to). It has received funding recently ... Continue reading Possibly of interest to your paper is dat , a program in development to provide version control of datasets (more so than git is able to). It has received funding recently from the Knight Foundation (see here ) and is something worth looking out for in terms of data sharing, but more importantly, preservation and logging. Thank you for writing this — it provides a succinct introduction to an important issue. Possibly of interest to your paper is dat , a program in development to provide version control of datasets (more so than git is able to). It has received funding recently from the Knight Foundation (see here ) and is something worth looking out for in terms of data sharing, but more importantly, preservation and logging. Thank you for writing this — it provides a succinct introduction to an important issue. Competing Interests: No competing interests were disclosed. Close Report a concern Discussion is closed on this version, please comment on the latest version above. keyboard_arrow_left keyboard_arrow_right Open Peer Review Reviewer Status info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions Reviewer Reports Invited Reviewers 1 2 3 Version 3 (revision) 16 Oct 14 read Version 2 (revision) 16 May 14 read read Version 1 23 Apr 14 read Mark Parsons , Research Data Alliance, Troy, NY, USA Peter Fox , Rensselaer Polytechnic Institute, Troy, NY, USA Mark Costello , University of Auckland, Auckland, New Zealand Ingrid Dillo , Data Archiving and Networking Services (DANS), The Hague, The Netherlands Comments on this article All Comments (7) Add a comment Sign up for content alerts Sign Up You are now signed up to receive this alert Browse by related subjects keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2014 Parsons M. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 06 Nov 2014 | for Version 3 Mark Parsons , Research Data Alliance, Troy, NY, USA 0 Views copyright © 2014 Parsons M. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (0) Approved info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions A nice rewrite and a very much improved paper, especially since it is now properly classified as a review article. Just a few small corrections listed below. Page 4, Para 5: "Writing a request to the creator should [very rarely] be part of the process" As noted before creator permission is sometimes legitimate. Page 5, para 2: "The most familiar kind of data publication is a traditional journal article accompanied by underlying data. " [citation needed] or change the sentence. Page 5, para 7 "Data papers are predated by an approach that Lawrence et al. (2011) call data publication by proxy..." This is not true. As Hans Pfeiffenberger notes, ESSD dates back to 2008. Indeed I wouldn't be surprised if Lawrence chatted a bit with ESSD editors, Pfeiffenberger and Carlson, in preparing his paper. Page 6, para 1 NSIDC does do external scientific reviews but they only go outside when they don’t have expertise in house. So it's sort of a combined approach. A quibble, but they pride themselves on in-house scientific expertise and engagement. Page 6 para 2: This paragraph is a little confused. Domain repositories don’t usually serve interdisciplinary use very well, but I don’t see how it’s necessarily bad to be distributed. What do you mean by publishing the whole research story? No one entity can do that. Competing Interests No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. reply Respond to this report Responses (0) Parsons M. Peer Review Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.5878.r6447) NOTE: it is important to ensure the information in square brackets after the title is included in this citation. The direct URL for this report is: https://f1000research.com/articles/3-94/v3#referee-response-6447 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2014 Dillo I. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 10 Jun 2014 | for Version 2 Ingrid Dillo , Data Archiving and Networking Services (DANS), The Hague, The Netherlands 0 Views copyright © 2014 Dillo I. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (0) Approved info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions The article focuses on a topic that receives a lot of interest these days. Therefore it is very timely. The article provides a useful and valuable overview of the current state of affairs and the ongoing debate. The title does justice to the content of the article. So does the abstract. This is the second version of the article. I do not see many changes in the text based on the earlier critical comments made by Mark Parsons and Peter Fox. The overview is very informative for everyone who needs a quick introduction into the subject. I do miss the opinion of the authors themselves on the issues at hand and on the quoted suggestions by others. This would have been appropriate in a concluding paragraph. Detailed comments: In the Introduction I miss a clear link between data publishing and data citation and creating the possibility for researchers to receive academic credits for their work on data. This academic credit is crucial as an incentive for researchers to put valuable time and effort in sharing their data. In the paragraph Why publish data? a reference to the Dutch fraud cases might be useful, as these cases got a lot of international attention and more or less triggered the discussion in the Netherlands with respect to research data management, long term preservation of data and data publishing and citation. A reference could be: Doorn P, Dillo I, van Horik R: Lies, Damned Lies and Research Data: Can Data Sharing Prevent Data Fraud? International Journal of Digital Curation. 2013; 8 (1): 229-243 http://dx.doi.org/10.2218/ijdc.v8i1.256 In the paragraph Types of data publication a threefold model is introduced to categorize data publications. It is not clear how this model relates to the terminology and categorisation presented in the introduction. This could be somewhat confusing for the reader. Furthermore, there are of course many other models available, e.g. that of the The Data Publication Pyramid, developed on the basis of the Jim Gray pyramid, to express the different manifestation forms that research data can have in the publication process: Reilly S, Schallier W, Schrimpf S, et al. : Report on integration of data and publications. October 2011. Located at: http://www.stm-assoc.org/2011_12_5_ODE_Report_On_Integration_of_Data_and_Publications.pdf Or the model presented in the report: Costas, R., Meijer, I., Zahedi, Z. and Wouters, P. (2013). The Value of Research Data - Metrics for datasets from a cultural and technical point of view. A Knowledge Exchange Report, available from www.knowledge-exchange.info/datametrics With respect to trustworthy digital repositories, I would like to add a few comments. First of all, in Europe a European Framework for Audit and Certification of Digital Repositories is emerging. It contains three certification standards (DSA, DIN31644/NESTOR seal and ISO13636) and three levels of certification (basic, extended and formal) see: http://www.trusteddigitalrepository.eu/Site/Trusted%20Digital%20Repository.html Of these three standards, only DSA has been up and running for some time now ,with 31 seals awarded and 30 ongoing self-assessments at this moment. The NESTOR seal has become available only very recently and the ISO standard is not yet officially available. The accompanying ISO 16919 standard: Requirements for bodies providing audit and certification of candidate trustworthy digital repositories, has been published very recently and now the ISO organization needs to be set up in the different countries, including the training of national auditors. The audits done by CRL are not fully official, since CRL is no formal ISO accreditation body. In Europe we see a growing interest in TDRs, coming from funders who want to push open data and data sharing and demand the deposit of publicly funded data in long term TDRs. Furthermore European research infrastructures and projects are also looking more and more into the issue of trust hen it comes to data sharing and a groeing number of them is incorporating (parts of) the DSA guidelines into there repositories and policies (e.g. CESSDA, CLARIN, EUDAT). Yet another certification procedure is offered by the ICSU/WDS to repositories that aim to become a member of the World Data System. See: https://www.icsu-wds.org/community/membership/certification The certification of TDRs could also help publishers/editorial boards with Data Availability Policies to point their authors to the right repositories for the long-term storage of their data. Competing Interests No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. reply Respond to this report Responses (0) Dillo I. Peer Review Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4518.r4540) NOTE: it is important to ensure the information in square brackets after the title is included in this citation. The direct URL for this report is: https://f1000research.com/articles/3-94/v2#referee-response-4540 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2014 Costello M. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 28 May 2014 | for Version 2 Mark Costello , Institute of Marine Science, University of Auckland, Auckland, New Zealand 0 Views copyright © 2014 Costello M. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (0) Approved info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions Having made some similar comments myself I must agree with this review. But a few points may merit amendment: Abstract: Note that what 'publication' means is the same as in print as in digital form. It does not imply peer-review or editorial oversight in either format. Citability: Yes, data citations are important but some datasets and web-based resources do not show how they should be cited, some journals do not allow citations to web resources in the Reference list, and even were both possible, too many authors neglect to cite actual datasets and instead cite a web site (which may have many datasets) or a related print paper. I agree that a DOI is not enough and only permanent if it is updated when documents are moved. A full author-tile-publisher citation as you suggest is more informative and human readable. I do not think it is problematic to cite parts of datasets. Pages and chapters in books are already cited for example. In most datasets it is also possible to identify individual dat records. Also, the actual data used could be provided in an Appendix so the reader is left in no doubt. Neither do I think 'versioning' is a problem. Where new data are added (e.g. to a time-series) then they comprise a new dataset, as they would if published in print. Where many corrections are made they a dataset can be treated like a paper; i.e. the original can be 'retracted' and replaced, or the new version be published with the metadata stating that it is more accurate. You mention venues for peer-reviewed data papers. For this article to advance previous articles, perhaps it could expand on these venues and how they manage the details of the peer-review process? I have published a few papers you may find of interest: Costello MJ, Wieczorek J. 2014. Best practice for biodiversity data management and publication. Biological Conservation, 173, 68-73. http://www.vliz.be/en/imis?module=ref&refid=234968 Costello MJ, Appeltans W, Bailly N, Berendsohn WG, de Jong Y, Edwards M, Froese R, Huettmann F, Los W, Mees J, Segers H, Bisby FA. 2014. Strategies for the sustainability of online open-access biodiversity databases. Biological Conservation 173, 155-165. http://www.marinebiology.ugent.be/component/imis/?module=ref&refid=230520 Costello MJ, Michener WK, Gahegan M, Zhang Z-Q, Bourne P. 2013. Data should be published, cited and peer-reviewed. Trends in Ecology and Evolution 28 (8) , 454-461. http://dx.doi.org/10.1016/j.tree.2013.05.002 Costello, M.J., Vanden Berghe E. 2006. “Ocean Biodiversity Informatics” enabling a new era in marine biology research and management. Marine Ecology Progress Series 316, 203-214. http://www.int-res.com/abstracts/meps/v316/ Costello MJ, Michener WK, Gahegan M, Zhang Z-Q, Bourne P, Chavan V. 2012. Quality assurance and intellectual property rights in advancing biodiversity data publications. ver. 1.0, Copenhagen: Global Biodiversity Information Facility, Pp. 33, ISBN: 87‐92020‐49‐6. Accessible at http://links.gbif.org/qa_ipr_advancing_biodiversity_data_publishing_en_v1 . Competing Interests No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. reply Respond to this report Responses (0) Costello M. Peer Review Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4518.r4543) NOTE: it is important to ensure the information in square brackets after the title is included in this citation. The direct URL for this report is: https://f1000research.com/articles/3-94/v2#referee-response-4543 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2014 Parsons M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 06 May 2014 | for Version 1 Mark Parsons , Research Data Alliance, Troy, NY, USA Peter Fox , Rensselaer Polytechnic Institute, Troy, NY, USA 0 Views copyright © 2014 Parsons M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (1) Approved With Reservations info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions General Comments : Note: This review was written by Parsons and accepted (with some modification) by Fox. Insights likely come from conversations between Fox and Parsons, errors from Parsons . I am very glad the authors wrote this essay. It is a well-written, needed, and useful summary of the current status of “data publication” from a certain perspective. The authors, however, need to be bolder and more analytical. This is an opinion piece, yet I see little opinion. A certain view is implied by the organization of the paper and the references chosen, but they could be more explicit. The paper would be both more compelling and useful to a broad readership if the authors moved beyond providing a simple summary of the landscape and examined why there is controversy in some areas and then use the evidence they have compiled to suggest a path forward. They need to be more forthright in saying what data publication means to them, or what parts of it they do not deal with. Are they satisfied with the Lawrence et al. definition? Do they accept the critique of Parsons and Fox? What is the scope of their essay? The authors take a rather narrow view of data publication, which I think hinders their analyses. They describe three types of (digital) data publication: Data as a supplement to an article; data as the subject of a paper; and data independent of a paper. The first two types are relatively new and they represent very little of the data actually being published or released today. The last category, which is essentially an “other” category, is rich in its complexity and encompasses the vast majority of data released. I was disappointed that the examples of this type were only the most bare-bones (Zenodo and Figshare). I think a deeper examination of this third category and its complexity would help the authors better characterize the current landscape and suggest paths forward. Some questions the authors might consider: Are these really the only three models in consideration or does the publication model overstate a consensus around a certain type of data publication? Why are there different models and which approach is better for different situations? Do they have different business models or imply different social contracts? Might it also be worthy of typing “publishers” instead of “publications”? For example, do domain repositories vs. institutional repositories vs. publishers address the issues differently? Are these models sustaining models or just something to get us through the next 5-10 years while we really figure it out? I think this oversimplification inhibited some deeper analysis in other areas as well. I would like to see more examination of the validation requirement beyond the lens of peer review, and I would like a deeper examination of incentives and credit beyond citation. I thought the validation section of the paper was very relevant, but somewhat light. I like the choice of the term validation as more accurate than “quality” and it fits quite well with Callaghan’s useful distinction between technical and scientific review, but I think the authors overemphasize the peer-review style approach. The authors rightly argue that “peer-review” is where the publication metaphor leads us, but it may be a false path. They overstate some difficulties of peer-review (No-one looks at every data value? No, they use statistics, visualization, and other techniques.) while not fully considering who is responsible for what. We need a closer examination of different roles and who are appropriate validators (not necessarily conventional peers). The narrowly defined models of data publication may easily allow for a conventional peer-review process, but it is much more complex in the real-world “other” category. The authors discuss some of this in what they call “independent data validation,” but they don’t draw any conclusions. Only the simplest of research data collections are validated only by the original creators. More often there are teams working together to develop experiments, sampling protocols, algorithms, etc. There are additional teams who assess, calibrate, and revise the data as they are collected and assembled. The authors discuss some of this in their examples like the PDS and tDAR, but I wish they were more analytical and offered an opinion on the way forward. Are there emerging practices or consensus in these team-based schemes? The level of service concept illustrated by Open Context may be one such area. Would formalizing or codifying some of these processes accomplish the same as peer-review or more? What is the role of the curator or data scientist in all of this? Given the authors’s backgrounds, I was surprised this role was not emphasized more. Finally, I think it is a mistake for science review to be the main way to assess reuse value. It has been shown time and again that data end up being used effectively (and valued) in ways that original experts never envisioned or even thought valid. The discussion of data citation was good and captured the state of the art well, but again I would have liked to see some views on a way forward. Have we solved the basic problem and are now just dealing with edge cases? Is the “just-in-time identifier” the way to go? What are the implications? Will the more basic solutions work in the interim? More critically, are we overemphasizing the role of citation to provide academic credit? I was gratified that the authors referenced the Parsons and Fox paper which questions the whole data publication metaphor, but I was surprised that they only discussed the “data as software” alternative metaphor. That is a useful metaphor, but I think the ecosystem metaphor has broader acceptance. I mention this because the authors critique the software metaphor because “using it to alter or affect the academic reward system is a tricky prospect”. Yet there is little to suggest that data publication and corresponding citation alters that system either. Indeed there is little if any evidence that data publication and citation incentivize data sharing or stewardship. As Christine Borgman suggests, we need to look more closely at who we are trying to incentivize to do what . There is no reason to assume it follows the same model as research literature publication. It may be beyond the scope of this paper to fully examine incentive structures, but it at least needs to be acknowledged that building on the current model doesn’t seem to be working. Finally, what is the takeaway message from this essay? It ends rather abruptly with no summary, no suggested directions or immediate challenges to overcome, no call to action, no indications of things we should stop trying, and only brief mention of alternative perspectives. What do the authors want us to take away from this paper? Overall though, this is a timely and needed essay. It is well researched and nicely written with rich metaphor. With modifications addressing the detailed comments below and better recognizing the complexity of the current data publication landscape, this will be a worthwhile review paper. With more significant modification where the authors dig deeper into the complexities and controversies and truly grapple with their implications to suggest a way forward, this could be a very influential paper. It is possible that the definitions of “publication” and “peer-review” need not be just stretched but changed or even rejected. Detailed comments: The whole paper needs a quick copy edit. There are a few typos, missing words, and wrong verb tenses. Note the word “data” is a plural noun. E.g., Data are not software, nor are they literature. (NSICD, instead of NSIDC) Page 2, para 2: “citability is addressed by assigning a PID.” This is not true, as the authors discuss on page 4, para 4. Indeed, page 4, para 4 seems to contradict itself. Citation is more than a locator/identifier In the discussion of “Data independent of any paper” it is worth noting that there may often be linkages between these data and myriad papers. Indeed a looser concept of a data paper has existed for some time, where researchers request a citation to a paper even though it is not the data nor fully describes the data (e.g the CRU temp records) Page 4, para 1: I’m not sure it’s entirely true that published data cannot involve requesting permission. In past work with Indigenous knowledge holders, they were willing to publish summary data and then provide the details when satisfied the use was appropriate and not exploitive. I think those data were “published” as best they could be. A nit, perhaps, but it highlights that there are few if any hard and fast rules about data publication. Page 4, para 2: You may also want to mention the WDS certification effort, which is combining with the DSA via an RDA Working Group: Page 4, para 2: The joint declaration of data citation principles involved many more organizations than Force11, CODATA, and DCC. Please credit them all (maybe in a footnote). The glory of the effort was that it was truly a joint effort across many groups. There is no leader. Force11 was primarily a convener. Page 4, para 6: The deep citation approach recommended by ESIP is not to just to list variables or a range of data. It is to identify a “structural index” for the data and to use this to reference subsets. In Earth science this structural index is often space and time, but many other indices are possible--location in a gene sequence, file type, variable, bandwidth, viewing angle, etc. It is not just for “straightforward” data sets. Page 5, para 5: I take issue with the statement that few repositories provide scientific review. I can think of a couple dozen that do just off the top of my head, and I bet most domain repositories have some level of science review. The “scientists” may not always be in house, but the repository is a team facilitator. See my general comments. Page 5, para 10: The PDS system is only unusual in that it is well documented and advertised. As mentioned, this team style approach is actually fairly common Page 6, para 3: Parsons and Fox don’t just argue that the data publication metaphor is limiting. They also say it is misleading. That should be acknowledged at least, if not actively grappled with. Competing Interests No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however we have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 12 May 2014 John Kratz, California Digital Library, University of California Office of the President, Oakland, CA, 94612, USA Thank you for refereeing our paper and thank you especially for delivering your report so quickly. We submitted the paper as a review article, not an opinion piece, and it was reclassified somewhere along the way. I contacted an editor at F1000 about the issue, and I believe it will be switched back shortly. While there is undoubtedly a viewpoint inherent in the way we have organized the manuscript, it was our intention to deliver a timely summary of the current landscape as a foundation for future thinking, not to offer prescriptions or to endorse particular approaches. We have no shortage of opinions about data publication, and a true opinion piece may follow at some point, but our aim here was to remain fairly neutral. I think the paper you are asking for would also be valuable, but it's an entirely different paper from the one we have written. That said, your report is full of suggestions for expansion of analysis and clarification of scope that would absolutely improve the paper (e.g. the question of why some issues resist consensus more than others is an excellent one), and we will certainly address them in the next version. View more View less Competing Interests I am an author of the selected paper. reply Respond Report a concern Parsons M and Fox P. Peer Review Report For: Data publication consensus and controversies [version 3; peer review: 3 approved] . F1000Research 2014, 3 :94 ( https://doi.org/10.5256/f1000research.4264.r4541) NOTE: it is important to ensure the information in square brackets after the title is included in this citation. The direct URL for this report is: https://f1000research.com/articles/3-94/v1#referee-response-4541 Alongside their report, reviewers assign a status to the article: Approved - the paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations - A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved - fundamental flaws in the paper seriously undermine the findings and conclusions Adjust parameters to alter display View on desktop for interactive features Includes Interactive Elements View on desktop for interactive features Competing Interests Policy Provide sufficient details of any financial or non-financial competing interests to enable users to assess whether your comments might lead a reasonable person to question your impartiality. Consider the following examples, but note that this is not an exhaustive list: Examples of 'Non-Financial Competing Interests' Within the past 4 years, you have held joint grants, published or collaborated with any of the authors of the selected paper. You have a close personal relationship (e.g. parent, spouse, sibling, or domestic partner) with any of the authors. You are a close professional associate of any of the authors (e.g. scientific mentor, recent student). You work at the same institute as any of the authors. You hope/expect to benefit (e.g. favour or employment) as a result of your submission. You are an Editor for the journal in which the article is published. Examples of 'Financial Competing Interests' You expect to receive, or in the past 4 years have received, any of the following from any commercial organisation that may gain financially from your submission: a salary, fees, funding, reimbursements. You expect to receive, or in the past 4 years have received, shared grant support or other funding with any of the authors. You hold, or are currently applying for, any patents or significant stocks/shares relating to the subject matter of the paper you are commenting on. Stay Updated Sign up for content alerts and receive a weekly or monthly email with all newly published articles Register with F1000Research Already registered? Sign in Not now, thanks close PLEASE NOTE If you are an AUTHOR of this article, please check that you signed in with the account associated with this article otherwise we cannot automatically identify your role as an author and your comment will be labelled as a “User Comment”. If you are a REVIEWER of this article, please check that you have signed in with the account associated with this article and then go to your account to submit your report, please do not post your review here. If you do not have access to your original account, please contact us . All commenters must hold a formal affiliation as per our Policies . The information that you give us will be displayed next to your comment. User comments must be in English, comprehensible and relevant to the article under discussion. We reserve the right to remove any comments that we consider to be inappropriate, offensive or otherwise in breach of the User Comment Terms and Conditions . Commenters must not use a comment for personal attacks. When criticisms of the article are based on unpublished data, the data should be made available. I accept the User Comment Terms and Conditions Please confirm that you accept the User Comment Terms and Conditions. Affiliation ✕ refresh Please enter your institution. Note: To add your institution or organisation, start typing the name and then select the correct name from the list. Where applicable, the name will appear in both the original language and in English. Do not paste in the name. If the name does not appear in the drop-down list, we will display the information you have entered. ✕ refresh Country/Region * USA UK Canada China France Germany Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo Cook Islands Costa Rica Cote d'Ivoire Croatia Cuba Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Federated States of Micronesia Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and Mcdonald Islands Holy See (Vatican City State) Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Israel Italy Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo (Serbia and Montenegro) Kuwait Kyrgyzstan Lao People's Democratic Republic Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Minor Outlying Islands of the United States Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands Antilles New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea North Macedonia Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Reunion Romania Russian Federation Rwanda Saint Helena Saint Kitts and Nevis Saint Lucia Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Is South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand The Gambia The Netherlands Timor-Leste Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu UK USA Uganda Ukraine United Arab Emirates United States Virgin Islands Uruguay Uzbekistan Vanuatu Venezuela Vietnam Wallis and Futuna West Bank and Gaza Strip Western Sahara Yemen Zambia Zimbabwe Please select your country/region. You must enter a comment. Competing Interests Please disclose any competing interests that might be construed to influence your judgment of the article's or peer review report's validity or importance. Competing Interests Policy Provide sufficient details of any financial or non-financial competing interests to enable users to assess whether your comments might lead a reasonable person to question your impartiality. Consider the following examples, but note that this is not an exhaustive list: Examples of 'Non-Financial Competing Interests' Within the past 4 years, you have held joint grants, published or collaborated with any of the authors of the selected paper. You have a close personal relationship (e.g. parent, spouse, sibling, or domestic partner) with any of the authors. You are a close professional associate of any of the authors (e.g. scientific mentor, recent student). You work at the same institute as any of the authors. You hope/expect to benefit (e.g. favour or employment) as a result of your submission. You are an Editor for the journal in which the article is published. Examples of 'Financial Competing Interests' You expect to receive, or in the past 4 years have received, any of the following from any commercial organisation that may gain financially from your submission: a salary, fees, funding, reimbursements. You expect to receive, or in the past 4 years have received, shared grant support or other funding with any of the authors. You hold, or are currently applying for, any patents or significant stocks/shares relating to the subject matter of the paper you are commenting on. Please state your competing interests The comment has been saved. An error has occurred. Please try again. Cancel Post var lTitle = "Data publication consensus and controversies".replace("'", ''); var linkedInUrl = "http://www.linkedin.com/shareArticle?url=https://f1000research.com/articles/3-94/v3" + "&title=" + encodeURIComponent(lTitle) + "&summary=" + encodeURIComponent('Read the article by '); var deliciousUrl = "https://del.icio.us/post?url=https://f1000research.com/articles/3-94/v3&title=" + encodeURIComponent(lTitle); var redditUrl = "http://reddit.com/submit?url=https://f1000research.com/articles/3-94/v3" + "&title=" + encodeURIComponent(lTitle); linkedInUrl += encodeURIComponent('Kratz J and Strasser C'); var offsetTop = /chrome/i.test( navigator.userAgent ) ? 4 : -10; var addthis_config = { ui_offset_top: offsetTop, services_compact : "facebook,twitter,www.linkedin.com,www.mendeley.com,reddit.com", services_expanded : "facebook,twitter,www.linkedin.com,www.mendeley.com,reddit.com", services_custom : [ { name: "LinkedIn", url: linkedInUrl, icon:"/img/icon/at_linkedin.svg" }, { name: "Mendeley", url: "http://www.mendeley.com/import/?url=https://f1000research.com/articles/3-94/v3/mendeley", icon:"/img/icon/at_mendeley.svg" }, { name: "Reddit", url: redditUrl, icon:"/img/icon/at_reddit.svg" }, ] }; var addthis_share = { url: "https://f1000research.com/articles/3-94", templates : { twitter : "Data publication consensus and controversies. Kratz J and Strasser C, published by " + "@F1000Research" + ", https://f1000research.com/articles/3-94/v3" } }; if (typeof(addthis) != "undefined"){ addthis.addEventListener('addthis.ready', checkCount); addthis.addEventListener('addthis.menu.share', checkCount); } $(".f1r-shares-twitter").attr("href", "https://twitter.com/intent/tweet?text=" + addthis_share.templates.twitter); $(".f1r-shares-facebook").attr("href", "https://www.facebook.com/sharer/sharer.php?u=" + addthis_share.url); $(".f1r-shares-linkedin").attr("href", addthis_config.services_custom[0].url); $(".f1r-shares-reddit").attr("href", addthis_config.services_custom[2].url); $(".f1r-shares-mendelay").attr("href", addthis_config.services_custom[1].url); function checkCount(){ setTimeout(function(){ $(".addthis_button_expanded").each(function(){ var count = $(this).text(); if (count !== "" && count != "0") $(this).removeClass("is-hidden"); else $(this).addClass("is-hidden"); }); }, 1000); } close How to cite this report {{reportCitation}} Cancel Copy Citation Details $(function(){R.ui.buttonDropdowns('.dropdown-for-downloads');}); $(function(){R.ui.toolbarDropdowns('.toolbar-dropdown-for-downloads');}); $.get("/articles/acj/3979/5878") new F1000.Clipboard(); new F1000.ThesaurusTermsDisplay("articles", "article", "5878"); $(document).ready(function() { $( "#frame1" ).on('load', function() { var mydiv = $(this).contents().find("div"); var h = mydiv.height(); console.log(h) }); var tooltipLivingFigure = jQuery(".interactive-living-figure-label .icon-more-info"), titleLivingFigure = tooltipLivingFigure.attr("title"); tooltipLivingFigure.simpletip({ fixed: true, position: ["-115", "30"], baseClass: 'small-tooltip', content:titleLivingFigure + " " }); tooltipLivingFigure.removeAttr("title"); $("body").on("click", ".cite-living-figure", function(e) { e.preventDefault(); var ref = $(this).attr("data-ref"); $(this).closest(".living-figure-list-container").find("#" + ref).fadeIn(200); }); $("body").on("click", ".close-cite-living-figure", function(e) { e.preventDefault(); $(this).closest(".popup-window-wrapper").fadeOut(200); }); $(document).on("mouseup", function(e) { var metricsContainer = $(".article-metrics-popover-wrapper"); if (!metricsContainer.is(e.target) && metricsContainer.has(e.target).length === 0) { $(".article-metrics-close-button").click(); } }); var articleId = $('#articleId').val(); if($("#main-article-count-box").attachArticleMetrics) { $("#main-article-count-box").attachArticleMetrics(articleId, { articleMetricsView: true }); } }); var figshareWidget = $(".new_figshare_widget"); if (figshareWidget.length > 0) { window.figshare.load("f1000", function(Widget) { // Select a tag/tags defined in your page. In this tag we will place the widget. _.map(figshareWidget, function(el){ var widget = new Widget({ articleId: $(el).attr("figshare_articleId") //height:300 // this is the height of the viewer part. [Default: 550] }); widget.initialize(); // initialize the widget widget.mount(el); // mount it in a tag that's on your page // this will save the widget on the global scope for later use from // your JS scripts. This line is optional. //window.widget = widget; }); }); } close Error Close Add Reset F1000.MICROSERVICES.AFFILIATION = ''; $(document).ready(function () { $('.js-affiliations-form').each((index, form) => { new AffiliationForm({ formId: form.id, institutionErrorSelector: '.comment-enter-institution', departmentErrorSelector: '.comment-enter-department', placeSelector: '.js-add-comment-place', stateSelector: '.js-add-comment-state', zipCodeSelector: '.js-add-comment-zipcode', countrySelector: '.js-add-comment-country', countryErrorSelector: '.comment-enter-country', }); }); }); $(document).ready(function () { var reportIds = { "4544": 0, "6428": 0, "4540": 70, "6429": 0, "4829": 0, "4541": 306, "4830": 0, "4542": 0, "6447": 63, "4543": 69, }; $(".referee-response-container,.js-referee-report").each(function(index, el) { var reportId = $(el).attr("data-reportid"), reportCount = reportIds[reportId] || 0; $(el).find(".comments-count-container,.js-referee-report-views").html(reportCount); }); var uuidInput = $("#article_uuid"), oldUUId = uuidInput.val(), newUUId = "64dc5f76-c1fb-4771-803b-664aacbb3c31"; uuidInput.val(newUUId); $("a[href*='article_uuid=']").each(function(index, el) { var newHref = $(el).attr("href").replace(oldUUId, newUUId); $(el).attr("href", newHref); }); }); An innovative open access publishing platform offering rapid publication and open peer review, whilst supporting data deposition and sharing. Browse Gateways Collections How it Works Contact For Developers Cookie Notice Privacy Notice RSS Submit Your Research Follow us © 2012-2026 F1000 Research Ltd. ISSN 2046-1402 | Legal | Partner of Research4Life • CrossRef • ORCID • FAIRSharing R.templateTests.simpleTemplate = R.template(' $text $text $text $text $text '); R.templateTests.runTests(); var F1000platform = new F1000.Platform({ name: "f1000research", displayName: "F1000Research", hostName: "f1000research.com", id: "1", editorialEmail: "[email protected]", infoEmail: "[email protected]", usePmcStats: true }); $(function(){R.ui.dropdowns('.dropdown-for-authors, .dropdown-for-about, .dropdown-for-myresearch');}); // $(function(){R.ui.dropdowns('.dropdown-for-referees');}); $(document).ready(function () { if ($(".cookie-warning").is(":visible")) { $(".sticky").css("margin-bottom", "35px"); $(".devices").addClass("devices-and-cookie-warning"); } $(".cookie-warning .close-button").click(function (e) { $(".devices").removeClass("devices-and-cookie-warning"); $(".sticky").css("margin-bottom", "0"); }); $("#tweeter-feed .tweet-message").each(function (i, message) { var self = $(message); self.html(linkify(self.html())); }); $(".partner").on("mouseenter mouseleave", function() { $(this).find(".gray-scale, .colour").toggleClass("is-hidden"); }); }); Sign In Remember me Forgotten your password? Sign In Cancel Email or password not correct. Please try again Please wait... $(function(){ // Note: All the setup needs to run against a name attribute and *not* the id due the clonish // nature of facebox... $("a[id=googleSignInButton]").click(function(event){ event.preventDefault(); $("input[id=oAuthSystem]").val("GOOGLE"); $("form[id=oAuthForm]").submit(); }); $("a[id=facebookSignInButton]").click(function(event){ event.preventDefault(); $("input[id=oAuthSystem]").val("FACEBOOK"); $("form[id=oAuthForm]").submit(); }); $("a[id=orcidSignInButton]").click(function(event){ event.preventDefault(); $("input[id=oAuthSystem]").val("ORCID"); $("form[id=oAuthForm]").submit(); }); }); If you've forgotten your password, please enter your email address below and we'll send you instructions on how to reset your password. The email address should be the one you originally registered with F1000. Email address not valid, please try again You registered with F1000 via Google, so we cannot reset your password. To sign in, please click here . If you still need help with your Google account password, please click here . You registered with F1000 via Facebook, so we cannot reset your password. To sign in, please click here . If you still need help with your Facebook account password, please click here . Code not correct, please try again Reset password Cancel Email us for further assistance. Server error, please try again. If your email address is registered with us, we will email you instructions to reset your password. If you think you should have received this email but it has not arrived, please check your spam filters and/or contact for further assistance. Please wait... Register $(document).ready(function () { signIn.createSignInAsRow($("#sign-in-form-gfb-popup")); $(".target-field").each(function () { var uris = $(this).val().split("/"); if (uris.pop() === "login") { $(this).val(uris.toString().replace(",","/")); } }); });