Strategic priorities and challenges in research software funding: Results from an international survey

Strategic priorities and challenges in research... | 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/13-1447" }, "headline": "Strategic priorities and challenges in research software funding: Results from an international survey", "datePublished": "2024-11-29T18:36:13", "dateModified": "2025-01-06T10:25:58", "author": [ { "@type": "Person", "name": "Eric A. Jensen" }, { "@type": "Person", "name": "Daniel S. Katz" } ], "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": " Background Research software is increasingly recognized as critical infrastructure in contemporary science. It spans a broad spectrum, including source code files, algorithms, scripts, computational workflows, and executables, all created for or during research. While research funders have developed programs, initiatives, and policies to bolster research software’s role, there has been no empirical study of how these funders prioritize support for research software. Understanding their priorities is essential to clarify where current support is concentrated and to identify strategic gaps. Methods We conducted an online mixed methods survey of international research funders (n=36) to explore their priorities in supporting research software. The survey gathered data on the specific outcomes funders emphasize in their programs and initiatives for research software. Results The survey revealed that funders place strong emphasis on developing skills, promoting software sustainability, embedding open science practices, building community and collaboration, advancing research software funding mechanisms, increasing software visibility and use, fostering innovation, and ensuring security. Conclusions The findings highlight opportunities to enhance research software’s role through increased funder attention on professional recognition for software contributions and the non-technical, social aspects of research software sustainability. Addressing these areas could lead to more effective support and development of research software, ultimately benefitting the entire research ecosystem. " } { "@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/13-1447", "name": "Strategic priorities and challenges in research software funding:..." } } ] } Home Browse Strategic priorities and challenges in research software funding:... ALL Metrics - Views Downloads Get PDF Get XML Cite How to cite this article Jensen EA and Katz DS. Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.12688/f1000research.155879.2 ) 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 ▬ ✚ Research Article Revised Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] Eric A. Jensen https://orcid.org/0000-0002-8332-4507 1 , Daniel S. Katz 1 Eric A. Jensen https://orcid.org/0000-0002-8332-4507 1 , Daniel S. Katz 1 PUBLISHED 06 Jan 2025 Author details Author details 1 National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, IL, USA Eric A. Jensen Roles: Conceptualization, Data Curation, Formal Analysis, Investigation, Methodology, Project Administration, Writing – Original Draft Preparation, Writing – Review & Editing Daniel S. Katz Roles: Conceptualization, Funding Acquisition, Investigation, Project Administration, Resources, Supervision, Writing – Review & Editing OPEN PEER REVIEW DETAILS REVIEWER STATUS This article is included in the Research on Research, Policy & Culture gateway. Abstract Background Research software is increasingly recognized as critical infrastructure in contemporary science. It spans a broad spectrum, including source code files, algorithms, scripts, computational workflows, and executables, all created for or during research. While research funders have developed programs, initiatives, and policies to bolster research software’s role, there has been no empirical study of how these funders prioritize support for research software. Understanding their priorities is essential to clarify where current support is concentrated and to identify strategic gaps. Methods We conducted an online mixed methods survey of international research funders (n=36) to explore their priorities in supporting research software. The survey gathered data on the specific outcomes funders emphasize in their programs and initiatives for research software. Results The survey revealed that funders place strong emphasis on developing skills, promoting software sustainability, embedding open science practices, building community and collaboration, advancing research software funding mechanisms, increasing software visibility and use, fostering innovation, and ensuring security. Conclusions The findings highlight opportunities to enhance research software’s role through increased funder attention on professional recognition for software contributions and the non-technical, social aspects of research software sustainability. Addressing these areas could lead to more effective support and development of research software, ultimately benefitting the entire research ecosystem. READ ALL READ LESS Keywords Research software, research policy, research funding, science systems, FAIR, open science Corresponding Author(s) Eric A. Jensen ( [email protected] ) Close Corresponding author: Eric A. Jensen Competing interests: No competing interests were disclosed. Grant information: The Alfred P. Sloan Foundation funded this research via a grant to the National Center for Supercomputing Applications at the University of Illinois Urbana-Champaign for a project entitled “Charting the Course: Policy and Planning for Sustainable Research Software” (G-2022-19344). The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Copyright: © 2025 Jensen EA and Katz DS. 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. How to cite: Jensen EA and Katz DS. Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.12688/f1000research.155879.2 ) First published: 29 Nov 2024, 13 :1447 ( https://doi.org/10.12688/f1000research.155879.1 ) Latest published: 06 Jan 2025, 13 :1447 ( https://doi.org/10.12688/f1000research.155879.2 ) Revised Amendments from Version 1 Changes have been made primarily to the Methods section to add further detail on the study's limitations and context. Changes have been made primarily to the Methods section to add further detail on the study's limitations and context. See the authors' detailed response to the review by Claire Jean-Quartier See the authors' detailed response to the review by Mario Coccia See the authors' detailed response to the review by Adrian Barnett READ REVIEWER RESPONSES Introduction Research software is increasingly recognized as critical infrastructure in the contemporary research ecosystem ( Barker et al., 2022 ; Jensen & Katz, 2023b ; Knowles et al., 2021 ; Hocquet et al., 2024 ). Research software spans a broad spectrum, including source code files, algorithms, scripts, computational workflows, and executables, all created for or during research ( Gruenpeter et al., 2021 ). With the growing reliance on computational methods across the sciences, supporting software development, maintenance, and impact is more essential than ever (e.g., Barker et al., 2020 ; Jay et al., 2021 ). For this reason, some research funders have developed programs, initiatives and policies to bolster research software’s role and impact ( Hertweck et al., 2024 ; Strasser et al., 2022 ). The research software landscape includes government and philanthropic funding sources ( Barker & Katz, 2022 ) that are seeking impact within the scientific ecosystem and beyond from their investments (e.g., Jensen et al., 2022 ). Research software is often open source and is sometimes tied to the larger open science movement that aims to improve transparency and reproducibility in research. To date, there has been no empirical study of how software is supported by research funders, the aims of such support and the priorities that underpin it. This information is needed to clarify where current funder support is concentrated and highlight significant gaps. This study investigates the range of efforts by research funders to support the sustainability and impact of research software. The aim is for these findings to inform improvements in funder strategies that would bolster research software’s role and value for academic research and the wider society. This paper draws on part of the dataset from this survey to address the following research question: What are the top priorities of international research funding organizations related to research software? Methods This research was carried out using a survey combining qualitative and quantitative items. The survey was designed to investigate how research software funders support research software’s sustainability and impact. Survey design The survey designed for this study began by collecting profile information, including institutional affiliation and job title. The survey gathered information about respondents’ organization’s initiatives, policies, or programs to support research software. The range of questions yielded too much data for one article. In this article, we focus exclusively on the results generated via an open-ended question asking about the top priorities for the respondents’ organizations’ support for research software: “What are your organization’s top priorities related to research software?” (see Jensen, 2024 for the extended data underpinning this article). Four open-response text boxes were provided for respondents to indicate and list these priorities. Clearly, potentially relevant variables were not included in the survey design for this exploratory study. These include details on the exact amount of funding spent on research software and other details about which many research funders would be unable to readily report either because the information is not actively tracked or relevant data do not currently exist. Sampling This survey was aimed at international research funders, including governmental and non-governmental (e.g., philanthropic) funders. A list of contacts to invite to participate in this survey was created based on participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors. ReSA is an international organization involving research policymakers, funders and organizations that recognize software’s importance in their work. This means that a ReSA-focused sample is likely to over-represent research funders who already view research software as important. For this reason, this paper does not claim that its findings generalize to the global population of research funders; rather, the claims focus on current patterns in research software funding. This initial list of people was refined, with removals based on individuals having moved to unrelated professional roles or being unavailable long-term, for example, due to personal issues. The final, refined contact list comprised 71 people. After removing individuals when a member of their organization already provided a complete answer or when the person turned out to no longer be working on a relevant topic or to be otherwise unavailable (total of n=30), 41 people remained. Five of these individuals did not complete the survey, while 36 people (representing 30 research funding organizations) did, yielding a response rate of 88%. Fully completed survey responses were not required for individuals to be retained in the sample, resulting in varied sample bases across survey questions. The sample includes research funders in North and South America, Europe, Oceania and Asia, but over-represents North America and European funder representatives. Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities. Continent Count North America 15 South America 4 Europe 12 Oceania 3 Asia 1 The respondents represented research funders supported by governmental (n=26), philanthropic (n=6) and corporate (n=1) resources. Respondents’ job titles span the following categories: Senior Leadership and Executive , such as a Vice President of Strategy; Program and Project Management , such as Senior Program Manager; Planning and Business Development ; Scientific, Technical and IT , such as Scientific Information Lead. Most respondents 72.7% (n=24) answered ‘Yes’ to the question, “Has your organization established any policies, initiatives or programs aimed at supporting research software?”, while 18.2% (n=6) said ‘No’ and 9.1% (n=3) ‘Unsure’. Data collection, management and analysis Data collection took place from December 2023 to May 2024. The mean completion time for the detailed survey was 28 minutes and 13 seconds. The data were cleaned and prepared for analysis by removing any identifiable respondent details. The data analysis process followed a standard thematic qualitative analysis approach (e.g., Jensen & Laurie, 2016 ). This involved first identifying themes and organizing the data accordingly. Dimensions of each theme were identified where relevant. Then data extracts were selected from the survey responses associated with each theme and theme dimension. In line with qualitative research methodology, the focus is on presence or absence of ideas in the survey responses, not quantification. However, prevalence has been used to organize the results section, as the more prevalent themes also come with a more extensive set of data extracts and potential dimensions. The results section below presents each theme in turn, with data extracts providing evidence to support the description of the themes. Results The survey reveals several priorities driving research funders’ support for research software. These themes are presented below, ordered from the most to least prevalent categories. Many of these categories overlap, so the boundaries between themes are porous. After each point is explained below, a verbatim data extract in the form of a block quotation from the survey responses is presented to substantiate the explanation. Skills The first identified theme, Skills , shows funders are prioritizing equipping researchers and other research professionals with competencies in software development, maintenance, and sustainability best practices. Supporting the training and retention of qualified staff to ensure human expertise and support within and between institutions. Funders were keen to ensure sufficient skilled personnel capable of writing and maintaining software. Skills - ensuring that there are enough skilled people writing software. Such skill development was viewed as foundational for research software as a field. Building the necessary skills, training, infrastructure, and incentives to support the growth of the [research software] field. Respondents noted a priority focus on researchers’ software skills, seeking to support “train [ing] researchers to cope with research software on different levels.” Training: We have an active initiative to train researchers to build software and digital research infrastructure. However, international funder priorities also included software-related skills for other research professionals. Invest in the training of both professional research and support staff to be able to reuse, develop, and maintain sustainable research software. Overall, the funder representatives indicated that training and skills development support was an important pathway to advancing research software. Software sustainability Software Sustainability emerged as a significant priority for research software funders. Sustainability means “the software will continue to be available in the future, on new platforms, meeting new needs” ( Katz, 2024 ). Indeed, the term sustainability was frequently used to answer this question about top priorities for research software funding, such as “supporting research software sustainability” or “identifying pathways to sustaining the research software.” In this section, we focus on non-financial aspects of software sustainability that respondents highlighted. Indeed, this priority was expressed in many ways. Sustainability and reuse of software. How can we reduce legacy debt and ensure that research software is continuously improved and reused. Reducing waste by maximizing the use of existing software was a notable focus evident in funders’ responses. Fund research software sustainability, and in particular incentivize the reuse and improvement of existing research software by providing funding to improve existing software. Some responses evinced the view that sustainability needed to be supported because it was part of ‘best practice’ in research software: “Promote the best practices for the production of sustainable research software.” Others focused on keeping software relevant and useful as a pathway to sustainability: “Support improvements to essential open source tools in [a specific field of] research”. Another response highlighted the importance of having standardized measures and practices to ensure sustainability. Establish metrics and best practices for software sustainability and integrate these into [the] software development lifecycle. In sum, the responses signaled funders’ full-throated commitment to ensuring research software’s long-term viability and continuous improvement (also see Barker et al., 2022 ). Open science The theme of Open Science highlights respondents’ emphasis on promoting open sharing, reuse, and accessibility of research software, adhering to the principles of open science. This theme is evident in the responses of research software funder representatives, who highlighted the importance of “open source practices” in fostering a collaborative and transparent research environment. One respondent articulates the goal of promoting open sharing and reuse through significant initiatives, stating, “To promote the open sharing and reuse of research software, mainly through the European Open Science Cloud.” Many funder representatives highlighted maintaining, improving, and “making research software reusable” in their survey responses. This indicates a strategic effort to leverage established platforms to facilitate research software’s open distribution and reuse, thereby enhancing its accessibility and impact. One respondent took an expansive view of what was included in efforts to integrate open science principles within research software: “Open Science including Accessibility, Inclusion, Reproducibility, Recognition, and security.” Another respondent called for a more explicit integration of research software into open science policies, saying, “Include research software more explicitly in our open science policies.” This points to the need for clear policy frameworks that explicitly address the role of research software in open science, ensuring that it is systematically included and supported (e.g., see Jiménez et al., 2017 ). This set of responses reflects a commitment to fostering an environment where a wide range of users and developers can contribute to and benefit from open-source research software. Building community and collaboration The theme of building community and collaboration among research software funders encompassed three main dimensions: Enhancing community engagement, fostering international collaboration, and sharing best practices through professional networks. These community-related priorities were ultimately aimed at spreading and embedding good practices in research software. The emphasis on community engagement highlights the importance of involving diverse groups in developing and maintaining scientific software. Funders prioritize approaches that ensure high-quality software through community involvement. They seek to promote opportunities that engage new communities in software development, making these resources accessible to under-represented communities and broadening participation in data science. Promote opportunities to engage new communities in software development and make these resources accessible to under-represented communities interested in data science. Another respondent emphasizes the importance of inclusivity in open source communities of practice: Supporting diverse participants (users and developers) in scientific open source (research) software. Additionally, there is a focus on community-focused software development and dissemination, ensuring that the processes and outcomes of software projects align with the community’s needs and contributions. Enhance community-focused software development and dissemination. International collaboration was identified as another critical dimension, focusing on creating a global network for software production. Funders aimed to facilitate work across institutions to prevent duplication of efforts and ensure that lesser-resourced institutions can equally benefit from open-source software, whether it be code, databases, or extensive infrastructure. This collaborative approach leveraged collective expertise and resources, promoting efficiency and innovation. Enabling work across institutions so that there is no duplication of effort and lesser-resourced institutions can benefit from OSS (whether bits of code, databases, or huge infrastructure) as much as the larger institutions. Moreover, fostering international collaboration is seen as a way to enhance the production of research software by tapping into a diverse pool of global expertise. Foster international collaboration in the production of research software. Funders prioritized disseminating best practices as a means of building robust communities around software development. Respondents emphasized the need for networks to share successful strategies and methodologies, ensuring that effective practices are widely adopted. This was aimed at contributing to improving research software quality and community development. Best practice and community - ensuring that there are networks to disseminate best practice and build communities. In addition to promoting best practices, there is a focus on developing community-based approaches for ensuring and improving the quality of scientific software. Development of community-based approaches for ensuring and improving the quality of scientific software and code. This response shows that funders linked community-building goals with practical concerns about continuous improvement and quality assurance of research software. Advancing research software funding The theme of advancing research software funding encompasses “funding new research software”, strategic planning of funding support, and fostering collaborative efforts to improve software impact. Funders noted the need for financial resources to support research software, for example, by “creating instruments to fund the production of high-quality research software.” They also emphasized the importance of developing plans to guide funding decisions over the medium term. Our primary priority is developing a strategy for how to fund [research software for the] next [several years]. Such a forward-looking approach is undoubtedly challenging in the constantly evolving research software landscape. Collaboration also emerged as a funder priority, with a systemic focus. Fund joint developments of research software useful for the [research] ecosystem in collaboration with other institutions. Overall, the theme of advancing research software funding highlighted funders’ commitment to creating strategic funding for research software. Increasing software visibility and use Funders highlighted the need to make existing research software more visible to a broader range of researchers. Provide visibility to successful computational projects from users of our platform, not only about the science but also about the software being developed. Additionally, there was a focus on enabling existing software to facilitate wider adoption and make it more accessible and usable. Make existing research software more visible [and] shape some of that software for wider adoption. [emphasis added] One funder noted the need for a centralized research software portal where researchers could access information on supported platforms, tools, and services. Developing a comprehensive catalog of currently supported [research software] platforms, tools and services that researchers can access via [a] single portal, including the cloud resources needed to run those services. Another funder’s related suggestion also focused on bolstering the visibility of research software through a shared portal or database. Develop a profile of funding and support programs for [research software], with a focus on those infrastructures that have a national and international impact, but also including emerging RS platforms that have not yet established their role/impact. The aim of increasing the visibility of research software in this way was “encouraging the [scientific] field to use research software.” Ultimately, these efforts aim to enhance the overall impact of research software. Innovation A small number of funders noted prioritizing integrating advanced technologies in software development. One funder noted the importance of “transitioning to accelerated compute” and maintaining pace with advancements in large-scale computing resources. Cutting edge - ensuring that software is developed to keep pace with the next generation of large-scale compute and supports the best research. A specific ‘innovation’ example mentioned was the “use of Generative AI in software engineering.” Such priorities reflected a forward-looking approach from a small subset of funders aiming to ensure that research software continues to support research effectively. Security Funders raised the theme of “security” in the development and use of research software, including ensuring “data security,” enhancing software security, and conducting “Security Awareness Training.” Security: Research software will not be able to be reused if IT departments are not confident that it is secure[,] even for Open science projects. While infrequently mentioned compared to other themes and with limited detail in the responses, security was seen as a fundamental issue to be addressed for a small number of research software funders. Discussion In this paper, we have described the priorities guiding research software funders. Here, we consider the implications of these priorities for advancing research software’s role in the scientific ecosystem. Within the skills development priorities highlighted by respondents, several technical training topics to support the design, development and deployment of research software were mentioned. This funder priority aligns with an identified need for training in research software skills (e.g., Carver et al., 2022 ; Cosden et al., 2022 ). Moreover, this skills theme suggests that there is recognition among funders that there is a need to invest in the people who underpin research software (e.g., Hartley & Barker, 2023 ; Katz, 2021 ). However, the more social aspects of research software sustainability and impact were not explicitly mentioned by any respondents. Addressing such social aspects and non-technical skills is an essential need in the field. For example, research software projects need to be able to identify relevant parties to engage with, maintain effective communication with current and potential users, establish a robust framework for monitoring and addressing evolving needs in a user community, and ensure good user experiences with the software. A recently published report highlighted “UX design, product management, and community management” as examples of key roles that often go unfunded in open source research software projects ( Iacovou, 2024 ). Iacovou (2024) noted that this averred gap in available support was part of a broader need to address the critical social and community aspects of research software sustainability. While respondents in our survey explicitly noted community building and management, supporting the development of the skills underpinning this kind of work was not highlighted as a priority for research software funders. Software sustainability emerged as a prominent theme in responses by research software funders. Software sustainability is a complex and, in some ways, an irresolvable challenge due to ever-shifting contexts on the broader research ecosystem (e.g., Howison, 2020 ; Katz, 2024 ). However, there is clearly a need for funders to address not only the technical aspects of software sustainability but also the social and professional infrastructure that bolsters long-term sustainability (e.g., Carver et al., 2021 ). The theme of Open Science in the survey responses emphasized promoting open sharing, reuse, and accessibility of research software. This is achieved through strategic initiatives, including open science principles, explicit policy integration, support for diverse participants, and promoting open source practices. For example, funding open-source tools has been a major focus in the Chan Zuckerberg Initiative’s Essential Open Source Software for Science (EOSS) program, which has focused on software for biomedical research. A recent report on the EOSS program highlighted wide-ranging benefits from this investment in terms of scientific progress and diversifying scientific open source software teams and communities ( Hertweck et al., 2024 ). This suggests good alignment between funder priorities and the evidence base about what is yielding practical scientific and broader impacts. Different practical ways of ensuring that research software contributes to such a healthy and open ecosystem are being discussed in the research software field (e.g., McKiernan et al., 2023 ; Sonabend et al., 2024 ; Sellanga et al., 2024 ). For example, applying FAIR (Findable, Accessible, Interoperable and Reusable) principles to research software has been highlighted as an essential step in the literature ( Barker et al., 2022 ). While our respondents mentioned concepts such as ‘accessibility’ and ‘reuse’, the term FAIR was not explicitly used. Overall, the survey responses evince a commitment to fostering an open, inclusive, and transparent research ecosystem. However, it is worth acknowledging that the focus on open source may be exaggerated in our purposive sample of funders already active in the research software arena, which is strongly oriented towards open source. The theme of building community and collaboration was defined by efforts to enhance community engagement, foster international partnerships, and disseminate best practices. Advancing research software funding was also highlighted as a theme, with priorities including backing new software, strategic financial planning, and fostering collaborations. In these responses, funders emphasized the need for resources, strategic guidance, and joint efforts to enhance software impact. Promoting the visibility and use of existing software also emerged as a priority for research software funders. This included an interest in bolstering the awareness of available software by making it more prominent, cataloging and profiling available software resources, and encouraging software adoption. It has previously been noted that research software visibility can be bolstered through institutions that help to build community and collaboration, such as software sustainability institutes ( Katz et al., 2021 ). A notable gap in the priorities identified by research software funders is the thorny challenge of bolstering recognition of research software contributions in academic hiring, promotion, and tenure ( Jensen & Katz, 2023a ). This may appear to be outside the purview of research software funders, but such ‘people’ aspects are a clear priority for those who produce and maintain research software (e.g., Cohen et al., 2021 ; Lamprecht et al., 2022 ). A recent article summarized ‘ten simple rules’ for addressing this challenge, including ensuring that software contributions are recognized as key scholarly contributions, consistent with open science principles ( Puebla et al., 2024 ). While all of these rules/recommendations focus on the level of research institutions ( Barker et al., 2024 ), research funders can play a pivotal role in nudging the priorities and actions of such institutions. Therefore, research software funders should consider how they could help encourage research institutions to adopt a software-inclusive stance within hiring, promotion and tenure. Much less frequently mentioned themes were innovation in research software, stressing the need to stay ahead of rapidly shifting trends in computing and the need to ensure that research software is secure from threats. Adapting research software good practices to advancements in AI and related developments is a need that has also been highlighted in the literature (e.g., Duarte et al., 2023 ), and it is an ongoing challenge facing the research software field. The theme of security in research software development and use was defined by a strong focus on ensuring data security, enhancing software security, and promoting security awareness training. Conclusion The insights from research software funders reveal a commitment to enhancing the scientific landscape through targeted investments in software sustainability, open science, and community collaboration. Yet, the relative underemphasis on non-technical skills and social infrastructure suggests a need for a more holistic approach. To fully realize the potential of research software, funders must broaden their focus, integrating social and technical priorities to foster a resilient and dynamic research environment. By addressing such gaps, funders can help ensure that research software plays a more efficient, inclusive, sustainable, and impactful role within the scientific ecosystem. Ethics and consent The University of Illinois Urbana-Champaign Institutional Review Board reviewed this research and determined it to be exempt (no. 24374) on September 11, 2023. All participants provided explicit informed written consent to participate in this study at the start of the online form used to gather the survey data. This included consent for data to be used for research purposes and to be published as open data after deidentification. Data availability Underlying data Repository name: Zenodo Title of project: Strategic priorities and challenges in research software funding: Results from an international survey [Dataset]. DOI: https://doi.org/10.5281/zenodo.13852004 ( Jensen, 2024 ) This project contains the following underlying data: • Survey data file: Anonymized responses from the international survey on strategic priorities and challenges in research software funding gathered from representatives of research funding organizations. Details of license: The anonymized survey data are available under the Creative Commons Attribution Non-Commercial No Derivatives 4.0 International license. Extended data Repository name: Zenodo Title of project: Strategic priorities and challenges in research software funding: Results from an international survey. DOI: https://doi.org/10.5281/zenodo.13852004 ( Jensen, 2024 ) This project contains the following extended data: • Consent block from survey: The information and questions used to gather informed consent through the online survey have been uploaded as a document file. • SURVEY DESIGN_Research_software_funder_survey_UIUC (upload to Zenodo).pdf Details of license: The anonymized survey data are available under the Creative Commons Attribution Non-Commercial No Derivatives 4.0 International license. Acknowledgements The Alfred P. Sloan Foundation funded this research via a grant to the National Center for Supercomputing Applications at the University of Illinois Urbana-Champaign for a project entitled “Charting the Course: Policy and Planning for Sustainable Research Software” (G-2022-19344). This project aims to devise strategies for enhancing the durability and sustainability of research software by bolstering the role of policy at various levels within the research ecosystem. The authors would also like to express appreciation for feedback from Professor Caroline Jay (University of Manchester). References Barker M, Chue Hong NP, Katz DS, et al. : Introducing the FAIR principles for research software. Sci. Data. 2022; 9 : Article 622. PubMed Abstract | Publisher Full Text | Free Full Text Barker M, Katz DS: Overview of research software funding landscape. Zenodo. 2022. Publisher Full Text Barker M, Katz DS, Gonzalez-Beltran A: Evidence for the importance of research software. Zenodo. 2020. Publisher Full Text Barker M, Carlin D, Cohen J, et al. : Resources for supporting policy change in research institutions in practice: A report from Subgroup 2 of the ReSA & RDA Policies in Research Organisations for Research Software (PRO4RS) Working Group. Zenodo. 2024. Publisher Full Text Carver JC, Cosden IA, Hill C, et al. : Sustaining research software via research software engineers and professional associations. Proceedings of the 1st International Workshop on the Body of Knowledge for Software Sustainability (BoKSS’21). IEEE; 2021; pp. 69–72. Publisher Full Text Carver JC, Weber N, Ram K, et al. : A survey of the state of the practice for research software in the United States. PeerJ. Comput. Sci. 2022; 8 : e963. PubMed Abstract | Publisher Full Text | Free Full Text Cohen J, Katz DS, Barker M, et al. : The four pillars of research software engineering. IEEE Softw. 2021; 38 (1): 97–105. Publisher Full Text Cosden IA, McHenry K, Katz DS: Research software engineers: Career entry points and training gaps. Comput. Sci. Eng. 2022; 24 (6): 14–21. Publisher Full Text Duarte J, Li H, Roy A, et al. : FAIR AI models in high energy physics. Mach. Learn.: Sci. Technol. 2023; 4 (4): 045062. Publisher Full Text Gruenpeter M, Katz DS, Lamprecht A-L, et al. : Defining research software: A controversial discussion. Zenodo. 2021. Publisher Full Text Hartley K, Barker M: Investing in people: Anticipating the future of research software. Research Software Alliance Blog. 2023, October. Reference Source Hertweck K, Strasser C, Taraborelli D: Insights and impact from five cycles of Essential Open Source Software for Science. Zenodo. 2024. Publisher Full Text Hocquet A, Wieber F, Gramelsberger G, et al. : Software in science is ubiquitous yet overlooked. Nat. Comput. Sci. 2024; 4 : 465–468. PubMed Abstract | Publisher Full Text Howison J: Sustainability in scientific software: Ecosystem complexity and software visibility. Zenodo. 2020. Publisher Full Text Iacovou G: Funding open source science software. Notion. 2024, June. Retrieved November 26, 2024. Reference Source Jay C, Haines R, Katz DS: Software must be recognised as an important output of scholarly research. Int. J. Digit. Curation. 2021; 16 (1). Publisher Full Text Jensen EA: Strategic priorities and challenges in research software funding: Results from an international survey. (Dataset). Zenodo. 2024. Publisher Full Text Jensen EA, Katz DS: From code to tenure: Valuing research software in academia. Commonplace. 2023a. Publisher Full Text Jensen EA, Katz DS: From backstage to spotlight: A call to highlight the critical role of research software. LSE Impact Blog. 2023b. Publisher Full Text Jensen EA, Laurie C: Doing real research: A practical guide to social research. SAGE; 2016. Jensen EA, Wong P, Reed MS: How research data deliver non-academic impacts: A secondary analysis of UK Research Excellence Framework impact case studies. PLoS One. 2022; 17 (3): e0264914. PubMed Abstract | Publisher Full Text | Free Full Text Jiménez RC, Kuzak M, Alhamdoosh M, et al. : Four simple recommendations to encourage best practices in research software. F1000Res. 2017; 6 : 876. PubMed Abstract | Publisher Full Text | Free Full Text Katz DS: Valuing people vs hardware. Daniel S. Katz’s Blog. 2021. Publisher Full Text Katz DS: There’s no such thing as sustainable research software. Daniel S. Katz’s Blog. 2024. Publisher Full Text Katz DS, Carver J, Chue Hong N, et al. : Addressing research software sustainability via institutes. Proceedings of the 1st International Workshop on the Body of Knowledge for Software Sustainability (BoKSS’21). IEEE; 2021; pp. 13–16. Publisher Full Text Knowles R, Mateen BA, Yehudi Y: We need to talk about the lack of investment in digital research infrastructure. Nat. Comput. Sci. 2021; 1 : 169–171. PubMed Abstract | Publisher Full Text Lamprecht A-L, Martinez-Ortiz C, Barker M, et al. : What do we (not) know about research software engineering? Journal of Open Research Software. 2022; 10 (1): Article 11. Publisher Full Text McKiernan EC, Barba LA, Bourne PE, et al. : Policy recommendations to ensure that research software is openly accessible and reusable. PLoS Biol. 2023; 21 (5): e3002204. PubMed Abstract | Publisher Full Text | Free Full Text Puebla I, Ascoli GA, Blume J, et al. : Ten simple rules for recognizing data and software contributions in hiring, promotion, and tenure. PLoS Comput. Biol. 2024; 20 (8): e1012296. PubMed Abstract | Publisher Full Text | Free Full Text Sellanga G, Steinhart E, Tsang N, et al. : 2024 survey of recent open science policy developments. Invest in Open Infrastructure. 2024. Publisher Full Text Sonabend R, Gruson H, Wolansky L, et al. : FAIR-USE4OS: Guidelines for creating impactful open-source software. PLoS Comput. Biol. 2024; 20 (5): e1012045. PubMed Abstract | Publisher Full Text | Free Full Text Strasser C, Hertweck K, Greenberg J, et al. : Ten simple rules for funding scientific open source software. PLoS Comput. Biol. 2022; 18 (11): e1010627. PubMed Abstract | Publisher Full Text | Free Full Text Comments on this article Comments (0) Version 2 VERSION 2 PUBLISHED 29 Nov 2024 ADD YOUR COMMENT Comment Author details Author details 1 National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, IL, USA Eric A. Jensen Roles: Conceptualization, Data Curation, Formal Analysis, Investigation, Methodology, Project Administration, Writing – Original Draft Preparation, Writing – Review & Editing Daniel S. Katz Roles: Conceptualization, Funding Acquisition, Investigation, Project Administration, Resources, Supervision, Writing – Review & Editing Competing interests No competing interests were disclosed. Grant information The Alfred P. Sloan Foundation funded this research via a grant to the National Center for Supercomputing Applications at the University of Illinois Urbana-Champaign for a project entitled “Charting the Course: Policy and Planning for Sustainable Research Software” (G-2022-19344). The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Article Versions (2) version 2 Revised Published: 06 Jan 2025, 13:1447 https://doi.org/10.12688/f1000research.155879.2 version 1 Published: 29 Nov 2024, 13:1447 https://doi.org/10.12688/f1000research.155879.1 Copyright © 2025 Jensen EA and Katz DS. 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. 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 Jensen EA and Katz DS. Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.12688/f1000research.155879.2 ) 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 2 VERSION 2 PUBLISHED 06 Jan 2025 Revised Views 0 Cite How to cite this report: Bakhshi R. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r358849 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-358849 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 Feb 2025 Rena Bakhshi , Netherlands eScience Center, Amsterdam, The Netherlands Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.176306.r358849 The current paper presents the results of a survey among research funders focusing on research software. In particular, the focus of the paper is around funders responses to the question "What are your organization’s top priorities related to research software?” ... Continue reading READ ALL The current paper presents the results of a survey among research funders focusing on research software. In particular, the focus of the paper is around funders responses to the question "What are your organization’s top priorities related to research software?” The authors employ a qualitative research methodology for their analysis, and extract topics/themes from the survey results. While the topic and this empirical study are interesting, the paper is somewhat underwhelming as a "research article". Beyond reporting of the dataset (survey results), it is unclear to me how this paper is addressing the research question posed in the introduction. The paper simply reports on the opinions of the respondents. What is missing is a deeper analysis, for instance, how these opinions relate to the policies of these organizations. For example, the authors write that "in sum, the responses signaled funders’ full-throated commitment to ensuring research software’s long-term viability and continuous improvement " but do not elaborate on relevant programs of those funders. The results section can be summarized in the form of a table to help readability. Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Partly If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Partly Are the conclusions drawn adequately supported by the results? Yes Competing Interests: No competing interests were disclosed. Reviewer Expertise: research software engineering, project management, program management, computer science (formal methods) 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, however I have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Bakhshi R. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r358849 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-358849 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: Kon F. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356589 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-356589 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 05 Feb 2025 Fabio Kon , University of São Paulo, São Paulo, Brazil Approved VIEWS 0 https://doi.org/10.5256/f1000research.176306.r356589 This is an interesting paper showing the priorities of research funders concerning funding research software. The method is sound, and the anonymized data is presented in a public repository. The contribution is small but relevant and can help both funders ... Continue reading READ ALL This is an interesting paper showing the priorities of research funders concerning funding research software. The method is sound, and the anonymized data is presented in a public repository. The contribution is small but relevant and can help both funders engage in RS funding. It can also guide researchers when seeking funding to develop RS. The set of survey respondents is biased because it started with a list from the Research Software Alliance, but this is clearly stated in the paper. Thus, I believe the paper should be indexed in F1000research, but I suggest the following changes before indexing. In the abstract, Results paragraph, the view is overly optimistic. Most funders probably don't value all these things; you got those skewed results because you used the ReSA list of contacts, as you correctly explain in Methods-Sampling. Somehow, this explanation should be reflected in the abstract, too. In the Methods-Survey design, it would be important to emphasize graphically the question "What are your organization.... software?"; e.g., by putting it in a box. In the Results section, you wrote that verbatim data extract in the form of a block quotation is shown. But, in fact, the reader can't see any block quotation, instead, a red text is displayed. I guess you might be referring to the latex command quotation that's obviously not seen by the reader. Probably, a \fbox command would work better. In the Results section, it would be interesting to know how often the topic was mentioned and/or how many respondents mentioned it. "the responses signaled funders' full-throated commitment to...". In fact, this doesn't show they're committed. It shows that they say this is something they look for in projects to be funded. In the discussion, I suggest revising the paragraph about Open Science as there's little connection between the beginning of the paragraph ("the theme of open science") and the example concerning EOSS. Funding OSS is a small part of Open Science in general, which that paragraph does not capture well. Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Yes If applicable, is the statistical analysis and its interpretation appropriate? Yes Are all the source data underlying the results available to ensure full reproducibility? Yes Are the conclusions drawn adequately supported by the results? Yes Competing Interests: No competing interests were disclosed. Reviewer Expertise: Software Engineering, Data Science, Distributed Systems 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 Kon F. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356589 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-356589 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: Jean-Quartier C. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r358851 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-358851 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 25 Jan 2025 Claire Jean-Quartier , Research Data Management, Graz University of Technology, Graz, Austria Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.176306.r358851 Authors present qualitative survey results on research software funding focusing on related priorities by the funders. Research software has and is often neglected in publications, and one would guess that funders do not focus on or require researchers to plan ... Continue reading READ ALL Authors present qualitative survey results on research software funding focusing on related priorities by the funders. Research software has and is often neglected in publications, and one would guess that funders do not focus on or require researchers to plan for software produced and used during research projects to be sustainable. Still, this key aspect remains an open question and is addressed by the herein presented results from a qualitative survey. Though, it would be highly interesting to read about all results from the survey, it makes sense to split the more extensive survey and make use of the subsection regarding funders’ priorities in regard to research software, as has been done by the authors. The presented manuscript could be improved in terms of scientific completeness and comprehensibility, therefore suggesting the following major points: (1) The manuscript seems to lack content in regard to the scientific background. It is recommended to extend the introduction section towards a more wholistic setting describing and reviewing software sustainability factors in general on the one side and general funders' priorities on the other side. (2) The results section could be made more comprehensible, since the so far used structural layout of text only, divided by numerous short paragraphs, does hinder readability. Results could be summarized in a table presenting key aspects, or something similar could be introduced to increase structural clarity and readability! Is the work clearly and accurately presented and does it cite the current literature? Partly Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Yes If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Partly Are the conclusions drawn adequately supported by the results? Yes Competing Interests: No competing interests were disclosed. Reviewer Expertise: research data management, open science, bioinformatics, cancer science 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, however I have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Jean-Quartier C. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r358851 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-358851 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 14 Apr 2025 Eric Jensen , National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA 14 Apr 2025 Author Response We appreciate your suggestion of extending the introduction to provide a more expansive account of the relevant background information. This section has now been significantly expanded. The ... Continue reading We appreciate your suggestion of extending the introduction to provide a more expansive account of the relevant background information. This section has now been significantly expanded. The short paragraph structure is standard for qualitative research results write-ups. However, we appreciate the suggestion of adding a table that presents key aspects of the findings. This has now been added in Version 3 (Table 1). We appreciate your suggestion of extending the introduction to provide a more expansive account of the relevant background information. This section has now been significantly expanded. The short paragraph structure is standard for qualitative research results write-ups. However, we appreciate the suggestion of adding a table that presents key aspects of the findings. This has now been added in Version 3 (Table 1). Competing Interests: No competing interests were disclosed. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 14 Apr 2025 Eric Jensen , National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA 14 Apr 2025 Author Response We appreciate your suggestion of extending the introduction to provide a more expansive account of the relevant background information. This section has now been significantly expanded. The ... Continue reading We appreciate your suggestion of extending the introduction to provide a more expansive account of the relevant background information. This section has now been significantly expanded. The short paragraph structure is standard for qualitative research results write-ups. However, we appreciate the suggestion of adding a table that presents key aspects of the findings. This has now been added in Version 3 (Table 1). We appreciate your suggestion of extending the introduction to provide a more expansive account of the relevant background information. This section has now been significantly expanded. The short paragraph structure is standard for qualitative research results write-ups. However, we appreciate the suggestion of adding a table that presents key aspects of the findings. This has now been added in Version 3 (Table 1). Competing Interests: No competing interests were disclosed. Close Report a concern COMMENT ON THIS REPORT Views 0 Cite How to cite this report: Coccia M. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356373 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-356373 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 22 Jan 2025 Mario Coccia , DSU, National Research Council Department of Engineering ICT and Technology for Energy and Transport, Rome, Lazio, Italy Not Approved VIEWS 0 https://doi.org/10.5256/f1000research.176306.r356373 Authors have partially clarified ... Continue reading READ ALL Authors have partially clarified my questions presented in my first report. Competing Interests: No competing interests were disclosed. Reviewer Expertise: science development and policies I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Coccia M. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356373 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-356373 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: Barnett A. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356372 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-356372 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 07 Jan 2025 Adrian Barnett , Queensland University of Technology, Brisbane, Queensland, Australia Approved VIEWS 0 https://doi.org/10.5256/f1000research.176306.r356372 No ... Continue reading READ ALL No further comments. Competing Interests: No competing interests were disclosed. Reviewer Expertise: Statistics, research funding, meta-research 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 Barnett A. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356372 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v2#referee-response-356372 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 29 Nov 2024 Views 0 Cite How to cite this report: Coccia M. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.171109.r344621 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v1#referee-response-344621 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 13 Dec 2024 Mario Coccia , DSU, National Research Council Department of Engineering ICT and Technology for Energy and Transport, Rome, Lazio, Italy Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.171109.r344621 Strategic priorities and challenges in research software funding: Results from an international survey The topics of this paper are interesting, though well known. The structure and content must be revised, and results have to be better explained ... Continue reading READ ALL Strategic priorities and challenges in research software funding: Results from an international survey The topics of this paper are interesting, though well known. The structure and content must be revised, and results have to be better explained by authors before to be reconsidered. Title has to be shorter and more specific of the fields concerning funding research software. Abstract has to clarify the goal, methods, empirical research and research policies to support funding of software. Introduction has to better clarify the research questions of this study, considering that software is an intangible innovation, clarifying the sources that are problem driven in specific contexts, such as medicine, environmental sciences, etc. Role of metrics that can assess the effectiveness of research software as an open science, such as citations and their association with funding in the diffusion of science, etc. After that they can focus on the topics of this study to provide a correct analysis for fruitful discussion (See suggested readings that must be all read and used in the text). Methods of this study is not clear. The section of Materials and methods must be re-structured with the following three sections: • Sample and data. The sample is not balanced between continents and also respondents and authors have to clarify how this is representative. • Measures of variables under study • Data analysis procedure . Insert a flow chart to specify the study design, with inclusion and exclusion criteria of organizations and respondents under study. The identifications of themes and key aspects can be done with specific quantitative approaches, and not only qualitative, such also as entity linking, etc.... now the analysis is rather vague. Results. The sample can be represented with some figures to be clearer for readers. Authors have to avoid subheadings that create fragmentation and confusion. If necessary, you can use bullet points (same comments for section of results and all sections). Results can be also systematized in some tables to be more effective in communicating results. I suggest using different levels of description results from general to more specific themes, using tables to be more effective. Discussion. First, authors have to synthesize the main results in a simple table to be clear for readers and then show what this study adds compared to other studies sone on these topics. To reiterate, avoiding in the just mentioned sections, sub-headings that create fragmentation of the paper. The results should be better discussed considering the research fields because the sources of research software, their goal, their adopters change according to the research fields, such as biomedical research, environmental sciences, economic sciences, etc....role of research software, funding and citations for diffusion of open science should be useful to decide specific policies. A SWOT matrix with pros and cons can support managerial implications. Conclusion has not to be a summary, but authors have to focus on manifold limitations of this study and based on results, provide best practices of research policies to support the development of research software having practical implications for the diffusion of knowledge (also with citations) and development of science. Overall, then, the paper is interesting, but theoretical framework is weak, and some results, too descriptive, create confusion… structure of the paper has to be improved; study design, discussion and presentation of results have to be clarified using suggested comments. I strongly suggest improving the paper by using all comments (suggested papers included reading and using all) and maybe it can be considered. Suggested readings. Afiaz, A., Ivanov, A.A., Chamberlin, J., ... Leek, J.T., Wright, C. 2024 (Ref -1). Best practices to evaluate the impact of biomedical research software-metric collection beyond citations, Bioinformatics, 40(8), btae469 Sochat, V., May, N., Cosden, I., Martinez-Ortiz, C., Bartholomew, S. 2022 (Ref-2). The Research Software Encyclopedia: A Community Framework to Define Research Software.Journal of Open Research Software, 10(1) Coccia M. 2017. Sources of technological innovation: Radical and incremental innovation problem-driven to support competitive advantage of firms. Technology Analysis & Strategic Management, vol. 29, n. 9, pp. 1048-1061, https://doi.org/10.1080/09537325.2016.1268682\ Cosden, I.A. 2022 (Ref-3). ,The Princeton University Research Software Engineering Group Model: Operational and Organizational Approaches.Computing in Science and Engineering, 24(5), pp. 24–31 Coccia M., Roshani S. 2024 (Ref-4). General laws of funding for scientific citations: how citations change in funded and unfunded research between basic and applied sciences. Journal of Data and Information Science, 9(1), 1–18. https://doi.org/10.2478/jdis-2024-0005 Gomez-Diaz, T., Recio, T. 2022 (Ref-5). Research Software vs. Research Data II: Protocols for Research Data dissemination and evaluation in the Open Science context.F1000Research, 11, 117 Roshani S., Bagheri R., Mosleh M., Coccia M. 2021 (Ref-6). What is the relationship between research funding and citation-based performance? A comparative analysis between critical disciplines. Scientometrics 126, 7859–7874. https://doi.org/10.1007/s11192-021-04077-9 Is the work clearly and accurately presented and does it cite the current literature? Partly Is the study design appropriate and is the work technically sound? Partly Are sufficient details of methods and analysis provided to allow replication by others? Partly If applicable, is the statistical analysis and its interpretation appropriate? Partly Are all the source data underlying the results available to ensure full reproducibility? Partly Are the conclusions drawn adequately supported by the results? Partly References 1. Afiaz A, Ivanov AA, Chamberlin J, Hanauer D, et al.: Best practices to evaluate the impact of biomedical research software-metric collection beyond citations. Bioinformatics . 2024; 40 (8). PubMed Abstract | Publisher Full Text 2. Sochat V, May N, Cosden I, Martinez-Ortiz C, et al.: The Research Software Encyclopedia: A Community Framework to Define Research Software. Journal of Open Research Software . 2022; 10 (1). Publisher Full Text 3. Cosden I: The Princeton University Research Software Engineering Group Model: Operational and Organizational Approaches. Computing in Science & Engineering . 2022; 24 (5): 24-31 Publisher Full Text 4. Coccia M, Roshani S: General laws of funding for scientific citations: how citations change in funded and unfunded research between basic and applied sciences. Journal of Data and Information Science . 2024; 9 (4): 71-89 Publisher Full Text 5. Gomez-Diaz T, Recio T: Research Software vs. Research Data II: Protocols for Research Data dissemination and evaluation in the Open Science context. F1000Res . 2022; 11 : 117 PubMed Abstract | Publisher Full Text 6. Roshani S, Bagherylooieh M, Mosleh M, Coccia M: What is the relationship between research funding and citation-based performance? A comparative analysis between critical disciplines. Scientometrics . 2021; 126 (9): 7859-7874 Publisher Full Text Competing Interests: No competing interests were disclosed. Reviewer Expertise: science development and policies 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, however I have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Coccia M. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.171109.r344621 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v1#referee-response-344621 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 06 Jan 2025 Eric Jensen , National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA 06 Jan 2025 Author Response We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. While we don’t entirely agree with ... Continue reading We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. While we don’t entirely agree with all points presented in this reviewer report, we have taken on board several points and made updates to the manuscript. Reviewer 2: “Title has to be shorter and more specific of the fields concerning funding research software.” Response: The relevant research fields for the participating research funders was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” Because this includes all research fields, it wouldn’t be appropriate to claim a narrower scope in the title. Reviewer 2: The reviewer makes several requests for a wider paper scope, e.g.: “Introduction has to better clarify the research questions of this study, considering that software is an intangible innovation, clarifying the sources that are problem driven in specific contexts, such as medicine, environmental sciences, etc. Role of metrics that can assess the effectiveness of research software as an open science, such as citations and their association with funding in the diffusion of science.” Response: These issues are beyond the scope of the current paper, which focuses on open-ended survey data from research funders. Imposing focus areas that did not emerge from these open-ended responses would be methodologically problematic. The research question currently stated in the manuscript is deliberately broad in line with the qualitative nature of the data that is being presented in the paper: “What are the top priorities of international research funding organizations related to research software?” Reviewer 2: “Methods of this study is not clear. The section of Materials and methods must be re-structured with the following three sections: […] Insert a flow chart to specify the study design, with inclusion and exclusion criteria of organizations and respondents under study. The identifications of themes and key aspects can be done with specific quantitative approaches, and not only qualitative, such also as entity linking, etc.” Response: The current Methods section structure follows the journal guidelines and is appropriate for a qualitative survey study like this. A purely qualitative analysis and reporting of results is permitted by this journal; adding quantitative methods is not required. Reviewer 2: “Authors have to avoid subheadings that create fragmentation and confusion. If necessary, you can use bullet points (same comments for section of results and all sections). Results can be also systematized in some tables to be more effective in communicating results. I suggest using different levels of description results from general to more specific themes, using tables to be more effective.” Response: We appreciate the reviewers ideas about how to present the results. However, the current structure is in line with accepted practices in qualitative research. Each subheading represents a distinct theme, so it would be inappropriate to force them together. Reviewer 2: Raises concerns about the Discussion section structure Response: While the reviewer’s feedback about the Discussion section is noted, it is presented in a manner consistent with the journal guidelines and normal social science practices. Adding a table, for example, would be out of line with typical Discussion section approaches for this kind of paper. Suggested readings: Because none of the suggested readings directly relate the research software funding, these papers have not been added to the citation list despite the reviewer’s insistence on adding citations to the reviewer’s published work. We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. While we don’t entirely agree with all points presented in this reviewer report, we have taken on board several points and made updates to the manuscript. Reviewer 2: “Title has to be shorter and more specific of the fields concerning funding research software.” Response: The relevant research fields for the participating research funders was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” Because this includes all research fields, it wouldn’t be appropriate to claim a narrower scope in the title. Reviewer 2: The reviewer makes several requests for a wider paper scope, e.g.: “Introduction has to better clarify the research questions of this study, considering that software is an intangible innovation, clarifying the sources that are problem driven in specific contexts, such as medicine, environmental sciences, etc. Role of metrics that can assess the effectiveness of research software as an open science, such as citations and their association with funding in the diffusion of science.” Response: These issues are beyond the scope of the current paper, which focuses on open-ended survey data from research funders. Imposing focus areas that did not emerge from these open-ended responses would be methodologically problematic. The research question currently stated in the manuscript is deliberately broad in line with the qualitative nature of the data that is being presented in the paper: “What are the top priorities of international research funding organizations related to research software?” Reviewer 2: “Methods of this study is not clear. The section of Materials and methods must be re-structured with the following three sections: […] Insert a flow chart to specify the study design, with inclusion and exclusion criteria of organizations and respondents under study. The identifications of themes and key aspects can be done with specific quantitative approaches, and not only qualitative, such also as entity linking, etc.” Response: The current Methods section structure follows the journal guidelines and is appropriate for a qualitative survey study like this. A purely qualitative analysis and reporting of results is permitted by this journal; adding quantitative methods is not required. Reviewer 2: “Authors have to avoid subheadings that create fragmentation and confusion. If necessary, you can use bullet points (same comments for section of results and all sections). Results can be also systematized in some tables to be more effective in communicating results. I suggest using different levels of description results from general to more specific themes, using tables to be more effective.” Response: We appreciate the reviewers ideas about how to present the results. However, the current structure is in line with accepted practices in qualitative research. Each subheading represents a distinct theme, so it would be inappropriate to force them together. Reviewer 2: Raises concerns about the Discussion section structure Response: While the reviewer’s feedback about the Discussion section is noted, it is presented in a manner consistent with the journal guidelines and normal social science practices. Adding a table, for example, would be out of line with typical Discussion section approaches for this kind of paper. Suggested readings: Because none of the suggested readings directly relate the research software funding, these papers have not been added to the citation list despite the reviewer’s insistence on adding citations to the reviewer’s published work. Competing Interests: I am the first author of the manuscript that this review report addresses. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 06 Jan 2025 Eric Jensen , National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA 06 Jan 2025 Author Response We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. While we don’t entirely agree with ... Continue reading We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. While we don’t entirely agree with all points presented in this reviewer report, we have taken on board several points and made updates to the manuscript. Reviewer 2: “Title has to be shorter and more specific of the fields concerning funding research software.” Response: The relevant research fields for the participating research funders was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” Because this includes all research fields, it wouldn’t be appropriate to claim a narrower scope in the title. Reviewer 2: The reviewer makes several requests for a wider paper scope, e.g.: “Introduction has to better clarify the research questions of this study, considering that software is an intangible innovation, clarifying the sources that are problem driven in specific contexts, such as medicine, environmental sciences, etc. Role of metrics that can assess the effectiveness of research software as an open science, such as citations and their association with funding in the diffusion of science.” Response: These issues are beyond the scope of the current paper, which focuses on open-ended survey data from research funders. Imposing focus areas that did not emerge from these open-ended responses would be methodologically problematic. The research question currently stated in the manuscript is deliberately broad in line with the qualitative nature of the data that is being presented in the paper: “What are the top priorities of international research funding organizations related to research software?” Reviewer 2: “Methods of this study is not clear. The section of Materials and methods must be re-structured with the following three sections: […] Insert a flow chart to specify the study design, with inclusion and exclusion criteria of organizations and respondents under study. The identifications of themes and key aspects can be done with specific quantitative approaches, and not only qualitative, such also as entity linking, etc.” Response: The current Methods section structure follows the journal guidelines and is appropriate for a qualitative survey study like this. A purely qualitative analysis and reporting of results is permitted by this journal; adding quantitative methods is not required. Reviewer 2: “Authors have to avoid subheadings that create fragmentation and confusion. If necessary, you can use bullet points (same comments for section of results and all sections). Results can be also systematized in some tables to be more effective in communicating results. I suggest using different levels of description results from general to more specific themes, using tables to be more effective.” Response: We appreciate the reviewers ideas about how to present the results. However, the current structure is in line with accepted practices in qualitative research. Each subheading represents a distinct theme, so it would be inappropriate to force them together. Reviewer 2: Raises concerns about the Discussion section structure Response: While the reviewer’s feedback about the Discussion section is noted, it is presented in a manner consistent with the journal guidelines and normal social science practices. Adding a table, for example, would be out of line with typical Discussion section approaches for this kind of paper. Suggested readings: Because none of the suggested readings directly relate the research software funding, these papers have not been added to the citation list despite the reviewer’s insistence on adding citations to the reviewer’s published work. We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. While we don’t entirely agree with all points presented in this reviewer report, we have taken on board several points and made updates to the manuscript. Reviewer 2: “Title has to be shorter and more specific of the fields concerning funding research software.” Response: The relevant research fields for the participating research funders was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” Because this includes all research fields, it wouldn’t be appropriate to claim a narrower scope in the title. Reviewer 2: The reviewer makes several requests for a wider paper scope, e.g.: “Introduction has to better clarify the research questions of this study, considering that software is an intangible innovation, clarifying the sources that are problem driven in specific contexts, such as medicine, environmental sciences, etc. Role of metrics that can assess the effectiveness of research software as an open science, such as citations and their association with funding in the diffusion of science.” Response: These issues are beyond the scope of the current paper, which focuses on open-ended survey data from research funders. Imposing focus areas that did not emerge from these open-ended responses would be methodologically problematic. The research question currently stated in the manuscript is deliberately broad in line with the qualitative nature of the data that is being presented in the paper: “What are the top priorities of international research funding organizations related to research software?” Reviewer 2: “Methods of this study is not clear. The section of Materials and methods must be re-structured with the following three sections: […] Insert a flow chart to specify the study design, with inclusion and exclusion criteria of organizations and respondents under study. The identifications of themes and key aspects can be done with specific quantitative approaches, and not only qualitative, such also as entity linking, etc.” Response: The current Methods section structure follows the journal guidelines and is appropriate for a qualitative survey study like this. A purely qualitative analysis and reporting of results is permitted by this journal; adding quantitative methods is not required. Reviewer 2: “Authors have to avoid subheadings that create fragmentation and confusion. If necessary, you can use bullet points (same comments for section of results and all sections). Results can be also systematized in some tables to be more effective in communicating results. I suggest using different levels of description results from general to more specific themes, using tables to be more effective.” Response: We appreciate the reviewers ideas about how to present the results. However, the current structure is in line with accepted practices in qualitative research. Each subheading represents a distinct theme, so it would be inappropriate to force them together. Reviewer 2: Raises concerns about the Discussion section structure Response: While the reviewer’s feedback about the Discussion section is noted, it is presented in a manner consistent with the journal guidelines and normal social science practices. Adding a table, for example, would be out of line with typical Discussion section approaches for this kind of paper. Suggested readings: Because none of the suggested readings directly relate the research software funding, these papers have not been added to the citation list despite the reviewer’s insistence on adding citations to the reviewer’s published work. Competing Interests: I am the first author of the manuscript that this review report addresses. Close Report a concern COMMENT ON THIS REPORT Views 0 Cite How to cite this report: Barnett A. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.171109.r344615 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v1#referee-response-344615 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 13 Dec 2024 Adrian Barnett , Queensland University of Technology, Brisbane, Queensland, Australia Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.171109.r344615 The paper examines funding for software. Software must compete against other priorities, e.g., equipment. It also must compete against other more “exciting” ideas, and hence may be neglected despite its importance to research. As an example, here’s a relevant and ... Continue reading READ ALL The paper examines funding for software. Software must compete against other priorities, e.g., equipment. It also must compete against other more “exciting” ideas, and hence may be neglected despite its importance to research. As an example, here’s a relevant and recent skeet from the software goliath Hadley Wickham (27 November 2024): “I had zero luck with grants. People really didn’t get why what I did was important and never figured out how to explain it to them.” https://bsky.app/profile/hadleywickham.bsky.social/post/3lbumdqcmcc2r And an interesting reply to Hadley’s skeet: “lol thinking about you burying the tidyverse into a corner of aim 3 for an NIH grant on some very specific cardiovascular outcome, which is how most infrastructure work gets funded” https://bsky.app/profile/travisgerke.bsky.social/post/3lca7rkqv222z I don’t usually quote skeets or tweets in peer reviews, but these are good anecdotal examples of how software can miss out to other priorities. It also highlights how software is often funded as an add-on rather than the main idea. Without breaking confidentiality, some more summary details on the funders would be useful to contextualise their answers and assess the generalisability of the results. Are the funders predominantly in science, engineering, or health and medicine? Or do they cover all these areas. What’s the total funding awarded per year? How many scientists per year do they support? The sampling frame could be biased towards funders with a greater interest in software as: “participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors.” This should be discussed as a limitation. It would also be useful to describe who ReSA are. The questions asked the funders about priorities, but did not ask for actual financial support. Funders can have many priorities, but with strong competition for funding they might not all get funded. Money spent on software would be the best measure of support. I realise this can’t be collected now, but some discussion of this would be useful. The quotes from funders were generally very positive and I expected to see something in the results on the challenges of funding software. This prompted my previous question on wanting to know more about the funders, as I wondered if they were an atypical group of funders with a particular interest in software. Perhaps the funders were not prompted for their negative experiences? I was surprised that there was nothing on partnering with industry. In Australia the funding schemes that require partnerships with industry (or government) have a much higher success rate than standard schemes. Given the potential commercial benefits of software, partnerships would be an option for many software applications. Minor comments: Sampling section (and elsewhere): “87.8%” – no need for a decimal place, see: Cole T. Too many digits: the presentation of numerical data, DOI: 10.1136/archdischild-2014-307149 The key question “What are your organization’s top priorities related to research software?” has no time frame. So I presume it was current priorities only? Although the question: “Has your organization established any policies, initiatives or programs aimed at supporting research software?” covers all times. A consistent time frame may have been better, for example, “in the last 5 years”. Discussion: I agree that funders have a part to play in increasing the recognition of software. Funders can be influential in how science is recognised and rewarded. The COARA initiative is likely relevant here, as it discusses needing to recognise the “diversity of contributions” which includes those scientists who create valuable software ( https://coara.eu/agreement/the-commitments/ ). Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? No If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Yes Are the conclusions drawn adequately supported by the results? Partly References 1. Cole TJ: Too many digits: the presentation of numerical data. Arch Dis Child . 2015; 100 (7): 608-9 PubMed Abstract | Publisher Full Text Competing Interests: No competing interests were disclosed. Reviewer Expertise: Statistics, research funding, meta-research 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, however I have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Barnett A. Reviewer Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.171109.r344615 ) The direct URL for this report is: https://f1000research.com/articles/13-1447/v1#referee-response-344615 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 06 Jan 2025 Eric Jensen , National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA 06 Jan 2025 Author Response We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. The details for how these points ... Continue reading We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. The details for how these points have been addressed in the new version of the manuscript are presented below: Reviewer 1: “Without breaking confidentiality, some more summary details on the funders would be useful to contextualise their answers and assess the generalisability of the results. [a] Are the funders predominantly in science, engineering, or health and medicine? Or do they cover all these areas. [b] What’s the total funding awarded per year? How many scientists per year do they support?” Response: [a] This information was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” [b] this information was not collected in the survey. Reviewer 1: “The sampling frame could be biased towards funders with a greater interest in software as: “participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors.” This should be discussed as a limitation. It would also be useful to describe who ReSA are.” Response: This is already discussed as a limitation. However, more limitations content has now been added to the methods section: “ReSA is an international organization involving research policymakers, funders and organizations that recognize software’s importance in their work. This means that a ReSA-focused sample is likely to over-represent research funders who already view research software as important. For this reason, this paper does not claim that its findings generalize to the global population of research funders; rather, the claims focus on current patterns in research software funding.” Reviewer 1: “The questions asked the funders about priorities, but did not ask for actual financial support. […] Money spent on software would be the best measure of support. I realise this can’t be collected now, but some discussion of this would be useful.” Response: This point is now addressed in the survey design subsection of the Methods section: “Clearly, potentially relevant variables were not included in the survey design for this exploratory study. These include details on the exact amount of funding spent on research software and other details about which many research funders would be unable to readily report either because the information is not actively tracked or relevant data do not currently exist.” Reviewer 1: “I was surprised that there was nothing on partnering with industry. In Australia the funding schemes that require partnerships with industry (or government) have a much higher success rate than standard schemes. Given the potential commercial benefits of software, partnerships would be an option for many software applications.” Response: There is an important distinction between research software and software for more general use. Research software, per se, often attracts less industry interest than some other software domains due to its tendency to have a narrower market/commercial potential. We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. The details for how these points have been addressed in the new version of the manuscript are presented below: Reviewer 1: “Without breaking confidentiality, some more summary details on the funders would be useful to contextualise their answers and assess the generalisability of the results. [a] Are the funders predominantly in science, engineering, or health and medicine? Or do they cover all these areas. [b] What’s the total funding awarded per year? How many scientists per year do they support?” Response: [a] This information was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” [b] this information was not collected in the survey. Reviewer 1: “The sampling frame could be biased towards funders with a greater interest in software as: “participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors.” This should be discussed as a limitation. It would also be useful to describe who ReSA are.” Response: This is already discussed as a limitation. However, more limitations content has now been added to the methods section: “ReSA is an international organization involving research policymakers, funders and organizations that recognize software’s importance in their work. This means that a ReSA-focused sample is likely to over-represent research funders who already view research software as important. For this reason, this paper does not claim that its findings generalize to the global population of research funders; rather, the claims focus on current patterns in research software funding.” Reviewer 1: “The questions asked the funders about priorities, but did not ask for actual financial support. […] Money spent on software would be the best measure of support. I realise this can’t be collected now, but some discussion of this would be useful.” Response: This point is now addressed in the survey design subsection of the Methods section: “Clearly, potentially relevant variables were not included in the survey design for this exploratory study. These include details on the exact amount of funding spent on research software and other details about which many research funders would be unable to readily report either because the information is not actively tracked or relevant data do not currently exist.” Reviewer 1: “I was surprised that there was nothing on partnering with industry. In Australia the funding schemes that require partnerships with industry (or government) have a much higher success rate than standard schemes. Given the potential commercial benefits of software, partnerships would be an option for many software applications.” Response: There is an important distinction between research software and software for more general use. Research software, per se, often attracts less industry interest than some other software domains due to its tendency to have a narrower market/commercial potential. Competing Interests: I am the first author for the original manuscript submission. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 06 Jan 2025 Eric Jensen , National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA 06 Jan 2025 Author Response We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. The details for how these points ... Continue reading We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. The details for how these points have been addressed in the new version of the manuscript are presented below: Reviewer 1: “Without breaking confidentiality, some more summary details on the funders would be useful to contextualise their answers and assess the generalisability of the results. [a] Are the funders predominantly in science, engineering, or health and medicine? Or do they cover all these areas. [b] What’s the total funding awarded per year? How many scientists per year do they support?” Response: [a] This information was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” [b] this information was not collected in the survey. Reviewer 1: “The sampling frame could be biased towards funders with a greater interest in software as: “participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors.” This should be discussed as a limitation. It would also be useful to describe who ReSA are.” Response: This is already discussed as a limitation. However, more limitations content has now been added to the methods section: “ReSA is an international organization involving research policymakers, funders and organizations that recognize software’s importance in their work. This means that a ReSA-focused sample is likely to over-represent research funders who already view research software as important. For this reason, this paper does not claim that its findings generalize to the global population of research funders; rather, the claims focus on current patterns in research software funding.” Reviewer 1: “The questions asked the funders about priorities, but did not ask for actual financial support. […] Money spent on software would be the best measure of support. I realise this can’t be collected now, but some discussion of this would be useful.” Response: This point is now addressed in the survey design subsection of the Methods section: “Clearly, potentially relevant variables were not included in the survey design for this exploratory study. These include details on the exact amount of funding spent on research software and other details about which many research funders would be unable to readily report either because the information is not actively tracked or relevant data do not currently exist.” Reviewer 1: “I was surprised that there was nothing on partnering with industry. In Australia the funding schemes that require partnerships with industry (or government) have a much higher success rate than standard schemes. Given the potential commercial benefits of software, partnerships would be an option for many software applications.” Response: There is an important distinction between research software and software for more general use. Research software, per se, often attracts less industry interest than some other software domains due to its tendency to have a narrower market/commercial potential. We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. The details for how these points have been addressed in the new version of the manuscript are presented below: Reviewer 1: “Without breaking confidentiality, some more summary details on the funders would be useful to contextualise their answers and assess the generalisability of the results. [a] Are the funders predominantly in science, engineering, or health and medicine? Or do they cover all these areas. [b] What’s the total funding awarded per year? How many scientists per year do they support?” Response: [a] This information was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” [b] this information was not collected in the survey. Reviewer 1: “The sampling frame could be biased towards funders with a greater interest in software as: “participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors.” This should be discussed as a limitation. It would also be useful to describe who ReSA are.” Response: This is already discussed as a limitation. However, more limitations content has now been added to the methods section: “ReSA is an international organization involving research policymakers, funders and organizations that recognize software’s importance in their work. This means that a ReSA-focused sample is likely to over-represent research funders who already view research software as important. For this reason, this paper does not claim that its findings generalize to the global population of research funders; rather, the claims focus on current patterns in research software funding.” Reviewer 1: “The questions asked the funders about priorities, but did not ask for actual financial support. […] Money spent on software would be the best measure of support. I realise this can’t be collected now, but some discussion of this would be useful.” Response: This point is now addressed in the survey design subsection of the Methods section: “Clearly, potentially relevant variables were not included in the survey design for this exploratory study. These include details on the exact amount of funding spent on research software and other details about which many research funders would be unable to readily report either because the information is not actively tracked or relevant data do not currently exist.” Reviewer 1: “I was surprised that there was nothing on partnering with industry. In Australia the funding schemes that require partnerships with industry (or government) have a much higher success rate than standard schemes. Given the potential commercial benefits of software, partnerships would be an option for many software applications.” Response: There is an important distinction between research software and software for more general use. Research software, per se, often attracts less industry interest than some other software domains due to its tendency to have a narrower market/commercial potential. Competing Interests: I am the first author for the original manuscript submission. Close Report a concern COMMENT ON THIS REPORT Comments on this article Comments (0) Version 2 VERSION 2 PUBLISHED 29 Nov 2024 ADD YOUR COMMENT Comment 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 4 5 Version 2 (revision) 06 Jan 25 read read read read read Version 1 29 Nov 24 read read Adrian Barnett , Queensland University of Technology, Brisbane, Australia Mario Coccia , National Research Council Department of Engineering ICT and Technology for Energy and Transport, Rome, Italy Claire Jean-Quartier , Graz University of Technology, Graz, Austria Fabio Kon , University of São Paulo, São Paulo, Brazil Rena Bakhshi , Netherlands eScience Center, Amsterdam, The Netherlands Comments on this article All Comments (0) 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 © 2025 Bakhshi R. 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 Feb 2025 | for Version 2 Rena Bakhshi , Netherlands eScience Center, Amsterdam, The Netherlands 0 Views copyright © 2025 Bakhshi R. 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 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 The current paper presents the results of a survey among research funders focusing on research software. In particular, the focus of the paper is around funders responses to the question "What are your organization’s top priorities related to research software?” The authors employ a qualitative research methodology for their analysis, and extract topics/themes from the survey results. While the topic and this empirical study are interesting, the paper is somewhat underwhelming as a "research article". Beyond reporting of the dataset (survey results), it is unclear to me how this paper is addressing the research question posed in the introduction. The paper simply reports on the opinions of the respondents. What is missing is a deeper analysis, for instance, how these opinions relate to the policies of these organizations. For example, the authors write that "in sum, the responses signaled funders’ full-throated commitment to ensuring research software’s long-term viability and continuous improvement " but do not elaborate on relevant programs of those funders. The results section can be summarized in the form of a table to help readability. Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Partly If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Partly Are the conclusions drawn adequately supported by the results? Yes Competing Interests No competing interests were disclosed. Reviewer Expertise research software engineering, project management, program management, computer science (formal methods) 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, however I have significant reservations, as outlined above. reply Respond to this report Responses (0) Bakhshi R. Peer Review Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r358849) 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/13-1447/v2#referee-response-358849 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2025 Kon F. 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. 05 Feb 2025 | for Version 2 Fabio Kon , University of São Paulo, São Paulo, Brazil 0 Views copyright © 2025 Kon F. 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 This is an interesting paper showing the priorities of research funders concerning funding research software. The method is sound, and the anonymized data is presented in a public repository. The contribution is small but relevant and can help both funders engage in RS funding. It can also guide researchers when seeking funding to develop RS. The set of survey respondents is biased because it started with a list from the Research Software Alliance, but this is clearly stated in the paper. Thus, I believe the paper should be indexed in F1000research, but I suggest the following changes before indexing. In the abstract, Results paragraph, the view is overly optimistic. Most funders probably don't value all these things; you got those skewed results because you used the ReSA list of contacts, as you correctly explain in Methods-Sampling. Somehow, this explanation should be reflected in the abstract, too. In the Methods-Survey design, it would be important to emphasize graphically the question "What are your organization.... software?"; e.g., by putting it in a box. In the Results section, you wrote that verbatim data extract in the form of a block quotation is shown. But, in fact, the reader can't see any block quotation, instead, a red text is displayed. I guess you might be referring to the latex command quotation that's obviously not seen by the reader. Probably, a \fbox command would work better. In the Results section, it would be interesting to know how often the topic was mentioned and/or how many respondents mentioned it. "the responses signaled funders' full-throated commitment to...". In fact, this doesn't show they're committed. It shows that they say this is something they look for in projects to be funded. In the discussion, I suggest revising the paragraph about Open Science as there's little connection between the beginning of the paragraph ("the theme of open science") and the example concerning EOSS. Funding OSS is a small part of Open Science in general, which that paragraph does not capture well. Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Yes If applicable, is the statistical analysis and its interpretation appropriate? Yes Are all the source data underlying the results available to ensure full reproducibility? Yes Are the conclusions drawn adequately supported by the results? Yes Competing Interests No competing interests were disclosed. Reviewer Expertise Software Engineering, Data Science, Distributed Systems 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) Kon F. Peer Review Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356589) 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/13-1447/v2#referee-response-356589 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2025 Jean-Quartier C. 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. 25 Jan 2025 | for Version 2 Claire Jean-Quartier , Research Data Management, Graz University of Technology, Graz, Austria 0 Views copyright © 2025 Jean-Quartier C. 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 Authors present qualitative survey results on research software funding focusing on related priorities by the funders. Research software has and is often neglected in publications, and one would guess that funders do not focus on or require researchers to plan for software produced and used during research projects to be sustainable. Still, this key aspect remains an open question and is addressed by the herein presented results from a qualitative survey. Though, it would be highly interesting to read about all results from the survey, it makes sense to split the more extensive survey and make use of the subsection regarding funders’ priorities in regard to research software, as has been done by the authors. The presented manuscript could be improved in terms of scientific completeness and comprehensibility, therefore suggesting the following major points: (1) The manuscript seems to lack content in regard to the scientific background. It is recommended to extend the introduction section towards a more wholistic setting describing and reviewing software sustainability factors in general on the one side and general funders' priorities on the other side. (2) The results section could be made more comprehensible, since the so far used structural layout of text only, divided by numerous short paragraphs, does hinder readability. Results could be summarized in a table presenting key aspects, or something similar could be introduced to increase structural clarity and readability! Is the work clearly and accurately presented and does it cite the current literature? Partly Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? Yes If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Partly Are the conclusions drawn adequately supported by the results? Yes Competing Interests No competing interests were disclosed. Reviewer Expertise research data management, open science, bioinformatics, cancer science 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, however I have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 14 Apr 2025 Eric Jensen, National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA We appreciate your suggestion of extending the introduction to provide a more expansive account of the relevant background information. This section has now been significantly expanded. The short paragraph structure is standard for qualitative research results write-ups. However, we appreciate the suggestion of adding a table that presents key aspects of the findings. This has now been added in Version 3 (Table 1). View more View less Competing Interests No competing interests were disclosed. reply Respond Report a concern Jean-Quartier C. Peer Review Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r358851) 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/13-1447/v2#referee-response-358851 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2025 Coccia 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. 22 Jan 2025 | for Version 2 Mario Coccia , DSU, National Research Council Department of Engineering ICT and Technology for Energy and Transport, Rome, Lazio, Italy 0 Views copyright © 2025 Coccia 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) Not 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 Authors have partially clarified my questions presented in my first report. Competing Interests No competing interests were disclosed. Reviewer Expertise science development and policies I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above. reply Respond to this report Responses (0) Coccia M. Peer Review Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356373) 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/13-1447/v2#referee-response-356373 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2025 Barnett A. 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. 07 Jan 2025 | for Version 2 Adrian Barnett , Queensland University of Technology, Brisbane, Queensland, Australia 0 Views copyright © 2025 Barnett A. 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 No further comments. Competing Interests No competing interests were disclosed. Reviewer Expertise Statistics, research funding, meta-research 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) Barnett A. Peer Review Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.176306.r356372) 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/13-1447/v2#referee-response-356372 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2024 Coccia 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. 13 Dec 2024 | for Version 1 Mario Coccia , DSU, National Research Council Department of Engineering ICT and Technology for Energy and Transport, Rome, Lazio, Italy 0 Views copyright © 2024 Coccia 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 (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 Strategic priorities and challenges in research software funding: Results from an international survey The topics of this paper are interesting, though well known. The structure and content must be revised, and results have to be better explained by authors before to be reconsidered. Title has to be shorter and more specific of the fields concerning funding research software. Abstract has to clarify the goal, methods, empirical research and research policies to support funding of software. Introduction has to better clarify the research questions of this study, considering that software is an intangible innovation, clarifying the sources that are problem driven in specific contexts, such as medicine, environmental sciences, etc. Role of metrics that can assess the effectiveness of research software as an open science, such as citations and their association with funding in the diffusion of science, etc. After that they can focus on the topics of this study to provide a correct analysis for fruitful discussion (See suggested readings that must be all read and used in the text). Methods of this study is not clear. The section of Materials and methods must be re-structured with the following three sections: • Sample and data. The sample is not balanced between continents and also respondents and authors have to clarify how this is representative. • Measures of variables under study • Data analysis procedure . Insert a flow chart to specify the study design, with inclusion and exclusion criteria of organizations and respondents under study. The identifications of themes and key aspects can be done with specific quantitative approaches, and not only qualitative, such also as entity linking, etc.... now the analysis is rather vague. Results. The sample can be represented with some figures to be clearer for readers. Authors have to avoid subheadings that create fragmentation and confusion. If necessary, you can use bullet points (same comments for section of results and all sections). Results can be also systematized in some tables to be more effective in communicating results. I suggest using different levels of description results from general to more specific themes, using tables to be more effective. Discussion. First, authors have to synthesize the main results in a simple table to be clear for readers and then show what this study adds compared to other studies sone on these topics. To reiterate, avoiding in the just mentioned sections, sub-headings that create fragmentation of the paper. The results should be better discussed considering the research fields because the sources of research software, their goal, their adopters change according to the research fields, such as biomedical research, environmental sciences, economic sciences, etc....role of research software, funding and citations for diffusion of open science should be useful to decide specific policies. A SWOT matrix with pros and cons can support managerial implications. Conclusion has not to be a summary, but authors have to focus on manifold limitations of this study and based on results, provide best practices of research policies to support the development of research software having practical implications for the diffusion of knowledge (also with citations) and development of science. Overall, then, the paper is interesting, but theoretical framework is weak, and some results, too descriptive, create confusion… structure of the paper has to be improved; study design, discussion and presentation of results have to be clarified using suggested comments. I strongly suggest improving the paper by using all comments (suggested papers included reading and using all) and maybe it can be considered. Suggested readings. Afiaz, A., Ivanov, A.A., Chamberlin, J., ... Leek, J.T., Wright, C. 2024 (Ref -1). Best practices to evaluate the impact of biomedical research software-metric collection beyond citations, Bioinformatics, 40(8), btae469 Sochat, V., May, N., Cosden, I., Martinez-Ortiz, C., Bartholomew, S. 2022 (Ref-2). The Research Software Encyclopedia: A Community Framework to Define Research Software.Journal of Open Research Software, 10(1) Coccia M. 2017. Sources of technological innovation: Radical and incremental innovation problem-driven to support competitive advantage of firms. Technology Analysis & Strategic Management, vol. 29, n. 9, pp. 1048-1061, https://doi.org/10.1080/09537325.2016.1268682\ Cosden, I.A. 2022 (Ref-3). ,The Princeton University Research Software Engineering Group Model: Operational and Organizational Approaches.Computing in Science and Engineering, 24(5), pp. 24–31 Coccia M., Roshani S. 2024 (Ref-4). General laws of funding for scientific citations: how citations change in funded and unfunded research between basic and applied sciences. Journal of Data and Information Science, 9(1), 1–18. https://doi.org/10.2478/jdis-2024-0005 Gomez-Diaz, T., Recio, T. 2022 (Ref-5). Research Software vs. Research Data II: Protocols for Research Data dissemination and evaluation in the Open Science context.F1000Research, 11, 117 Roshani S., Bagheri R., Mosleh M., Coccia M. 2021 (Ref-6). What is the relationship between research funding and citation-based performance? A comparative analysis between critical disciplines. Scientometrics 126, 7859–7874. https://doi.org/10.1007/s11192-021-04077-9 Is the work clearly and accurately presented and does it cite the current literature? Partly Is the study design appropriate and is the work technically sound? Partly Are sufficient details of methods and analysis provided to allow replication by others? Partly If applicable, is the statistical analysis and its interpretation appropriate? Partly Are all the source data underlying the results available to ensure full reproducibility? Partly Are the conclusions drawn adequately supported by the results? Partly References 1. Afiaz A, Ivanov AA, Chamberlin J, Hanauer D, et al.: Best practices to evaluate the impact of biomedical research software-metric collection beyond citations. Bioinformatics . 2024; 40 (8). PubMed Abstract | Publisher Full Text 2. Sochat V, May N, Cosden I, Martinez-Ortiz C, et al.: The Research Software Encyclopedia: A Community Framework to Define Research Software. Journal of Open Research Software . 2022; 10 (1). Publisher Full Text 3. Cosden I: The Princeton University Research Software Engineering Group Model: Operational and Organizational Approaches. Computing in Science & Engineering . 2022; 24 (5): 24-31 Publisher Full Text 4. Coccia M, Roshani S: General laws of funding for scientific citations: how citations change in funded and unfunded research between basic and applied sciences. Journal of Data and Information Science . 2024; 9 (4): 71-89 Publisher Full Text 5. Gomez-Diaz T, Recio T: Research Software vs. Research Data II: Protocols for Research Data dissemination and evaluation in the Open Science context. F1000Res . 2022; 11 : 117 PubMed Abstract | Publisher Full Text 6. Roshani S, Bagherylooieh M, Mosleh M, Coccia M: What is the relationship between research funding and citation-based performance? A comparative analysis between critical disciplines. Scientometrics . 2021; 126 (9): 7859-7874 Publisher Full Text Competing Interests No competing interests were disclosed. Reviewer Expertise science development and policies 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, however I have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 06 Jan 2025 Eric Jensen, National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. While we don’t entirely agree with all points presented in this reviewer report, we have taken on board several points and made updates to the manuscript. Reviewer 2: “Title has to be shorter and more specific of the fields concerning funding research software.” Response: The relevant research fields for the participating research funders was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” Because this includes all research fields, it wouldn’t be appropriate to claim a narrower scope in the title. Reviewer 2: The reviewer makes several requests for a wider paper scope, e.g.: “Introduction has to better clarify the research questions of this study, considering that software is an intangible innovation, clarifying the sources that are problem driven in specific contexts, such as medicine, environmental sciences, etc. Role of metrics that can assess the effectiveness of research software as an open science, such as citations and their association with funding in the diffusion of science.” Response: These issues are beyond the scope of the current paper, which focuses on open-ended survey data from research funders. Imposing focus areas that did not emerge from these open-ended responses would be methodologically problematic. The research question currently stated in the manuscript is deliberately broad in line with the qualitative nature of the data that is being presented in the paper: “What are the top priorities of international research funding organizations related to research software?” Reviewer 2: “Methods of this study is not clear. The section of Materials and methods must be re-structured with the following three sections: […] Insert a flow chart to specify the study design, with inclusion and exclusion criteria of organizations and respondents under study. The identifications of themes and key aspects can be done with specific quantitative approaches, and not only qualitative, such also as entity linking, etc.” Response: The current Methods section structure follows the journal guidelines and is appropriate for a qualitative survey study like this. A purely qualitative analysis and reporting of results is permitted by this journal; adding quantitative methods is not required. Reviewer 2: “Authors have to avoid subheadings that create fragmentation and confusion. If necessary, you can use bullet points (same comments for section of results and all sections). Results can be also systematized in some tables to be more effective in communicating results. I suggest using different levels of description results from general to more specific themes, using tables to be more effective.” Response: We appreciate the reviewers ideas about how to present the results. However, the current structure is in line with accepted practices in qualitative research. Each subheading represents a distinct theme, so it would be inappropriate to force them together. Reviewer 2: Raises concerns about the Discussion section structure Response: While the reviewer’s feedback about the Discussion section is noted, it is presented in a manner consistent with the journal guidelines and normal social science practices. Adding a table, for example, would be out of line with typical Discussion section approaches for this kind of paper. Suggested readings: Because none of the suggested readings directly relate the research software funding, these papers have not been added to the citation list despite the reviewer’s insistence on adding citations to the reviewer’s published work. View more View less Competing Interests I am the first author of the manuscript that this review report addresses. reply Respond Report a concern Coccia M. Peer Review Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.171109.r344621) 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/13-1447/v1#referee-response-344621 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2024 Barnett A. 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. 13 Dec 2024 | for Version 1 Adrian Barnett , Queensland University of Technology, Brisbane, Queensland, Australia 0 Views copyright © 2024 Barnett A. 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 The paper examines funding for software. Software must compete against other priorities, e.g., equipment. It also must compete against other more “exciting” ideas, and hence may be neglected despite its importance to research. As an example, here’s a relevant and recent skeet from the software goliath Hadley Wickham (27 November 2024): “I had zero luck with grants. People really didn’t get why what I did was important and never figured out how to explain it to them.” https://bsky.app/profile/hadleywickham.bsky.social/post/3lbumdqcmcc2r And an interesting reply to Hadley’s skeet: “lol thinking about you burying the tidyverse into a corner of aim 3 for an NIH grant on some very specific cardiovascular outcome, which is how most infrastructure work gets funded” https://bsky.app/profile/travisgerke.bsky.social/post/3lca7rkqv222z I don’t usually quote skeets or tweets in peer reviews, but these are good anecdotal examples of how software can miss out to other priorities. It also highlights how software is often funded as an add-on rather than the main idea. Without breaking confidentiality, some more summary details on the funders would be useful to contextualise their answers and assess the generalisability of the results. Are the funders predominantly in science, engineering, or health and medicine? Or do they cover all these areas. What’s the total funding awarded per year? How many scientists per year do they support? The sampling frame could be biased towards funders with a greater interest in software as: “participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors.” This should be discussed as a limitation. It would also be useful to describe who ReSA are. The questions asked the funders about priorities, but did not ask for actual financial support. Funders can have many priorities, but with strong competition for funding they might not all get funded. Money spent on software would be the best measure of support. I realise this can’t be collected now, but some discussion of this would be useful. The quotes from funders were generally very positive and I expected to see something in the results on the challenges of funding software. This prompted my previous question on wanting to know more about the funders, as I wondered if they were an atypical group of funders with a particular interest in software. Perhaps the funders were not prompted for their negative experiences? I was surprised that there was nothing on partnering with industry. In Australia the funding schemes that require partnerships with industry (or government) have a much higher success rate than standard schemes. Given the potential commercial benefits of software, partnerships would be an option for many software applications. Minor comments: Sampling section (and elsewhere): “87.8%” – no need for a decimal place, see: Cole T. Too many digits: the presentation of numerical data, DOI: 10.1136/archdischild-2014-307149 The key question “What are your organization’s top priorities related to research software?” has no time frame. So I presume it was current priorities only? Although the question: “Has your organization established any policies, initiatives or programs aimed at supporting research software?” covers all times. A consistent time frame may have been better, for example, “in the last 5 years”. Discussion: I agree that funders have a part to play in increasing the recognition of software. Funders can be influential in how science is recognised and rewarded. The COARA initiative is likely relevant here, as it discusses needing to recognise the “diversity of contributions” which includes those scientists who create valuable software ( https://coara.eu/agreement/the-commitments/ ). Is the work clearly and accurately presented and does it cite the current literature? Yes Is the study design appropriate and is the work technically sound? Yes Are sufficient details of methods and analysis provided to allow replication by others? No If applicable, is the statistical analysis and its interpretation appropriate? Not applicable Are all the source data underlying the results available to ensure full reproducibility? Yes Are the conclusions drawn adequately supported by the results? Partly References 1. Cole TJ: Too many digits: the presentation of numerical data. Arch Dis Child . 2015; 100 (7): 608-9 PubMed Abstract | Publisher Full Text Competing Interests No competing interests were disclosed. Reviewer Expertise Statistics, research funding, meta-research 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, however I have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 06 Jan 2025 Eric Jensen, National Center for Supercomputing Applications (NCSA), University of Illinois Urbana-Champaign, Urbana, USA We are grateful for this report's helpful and constructive reviewer comments. The reviewer report requests some additional information and raises some points for discussion. The details for how these points have been addressed in the new version of the manuscript are presented below: Reviewer 1: “Without breaking confidentiality, some more summary details on the funders would be useful to contextualise their answers and assess the generalisability of the results. [a] Are the funders predominantly in science, engineering, or health and medicine? Or do they cover all these areas. [b] What’s the total funding awarded per year? How many scientists per year do they support?” Response: [a] This information was already presented in the ‘sampling subsection’ of the methods section: “Some participating funders cover a broad spectrum of disciplines, while others focus on a particular domain such as social science, health, environment, physical sciences or humanities.” [b] this information was not collected in the survey. Reviewer 1: “The sampling frame could be biased towards funders with a greater interest in software as: “participation in the Research Software Association (ReSA) and responsibility for research software funding known to the authors.” This should be discussed as a limitation. It would also be useful to describe who ReSA are.” Response: This is already discussed as a limitation. However, more limitations content has now been added to the methods section: “ReSA is an international organization involving research policymakers, funders and organizations that recognize software’s importance in their work. This means that a ReSA-focused sample is likely to over-represent research funders who already view research software as important. For this reason, this paper does not claim that its findings generalize to the global population of research funders; rather, the claims focus on current patterns in research software funding.” Reviewer 1: “The questions asked the funders about priorities, but did not ask for actual financial support. […] Money spent on software would be the best measure of support. I realise this can’t be collected now, but some discussion of this would be useful.” Response: This point is now addressed in the survey design subsection of the Methods section: “Clearly, potentially relevant variables were not included in the survey design for this exploratory study. These include details on the exact amount of funding spent on research software and other details about which many research funders would be unable to readily report either because the information is not actively tracked or relevant data do not currently exist.” Reviewer 1: “I was surprised that there was nothing on partnering with industry. In Australia the funding schemes that require partnerships with industry (or government) have a much higher success rate than standard schemes. Given the potential commercial benefits of software, partnerships would be an option for many software applications.” Response: There is an important distinction between research software and software for more general use. Research software, per se, often attracts less industry interest than some other software domains due to its tendency to have a narrower market/commercial potential. View more View less Competing Interests I am the first author for the original manuscript submission. reply Respond Report a concern Barnett A. Peer Review Report For: Strategic priorities and challenges in research software funding: Results from an international survey [version 2; peer review: 2 approved, 2 approved with reservations, 1 not approved] . F1000Research 2025, 13 :1447 ( https://doi.org/10.5256/f1000research.171109.r344615) 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/13-1447/v1#referee-response-344615 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 = "Strategic priorities and challenges in research...".replace("'", ''); var linkedInUrl = "http://www.linkedin.com/shareArticle?url=https://f1000research.com/articles/13-1447/v2" + "&title=" + encodeURIComponent(lTitle) + "&summary=" + encodeURIComponent('Read the article by '); var deliciousUrl = "https://del.icio.us/post?url=https://f1000research.com/articles/13-1447/v2&title=" + encodeURIComponent(lTitle); var redditUrl = "http://reddit.com/submit?url=https://f1000research.com/articles/13-1447/v2" + "&title=" + encodeURIComponent(lTitle); linkedInUrl += encodeURIComponent('Jensen EA and Katz DS'); 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/13-1447/v2/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/13-1447", templates : { twitter : "Strategic priorities and challenges in research software funding:.... Jensen EA and Katz DS, published by " + "@F1000Research" + ", https://f1000research.com/articles/13-1447/v2" } }; 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/155879/176306") new F1000.Clipboard(); new F1000.ThesaurusTermsDisplay("articles", "article", "176306"); $(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 = { "358853": 0, "358852": 0, "358855": 0, "358854": 0, "356550": 0, "358849": 13, "358851": 17, "358850": 0, "358857": 0, "358856": 0, "358858": 0, "356373": 25, "356372": 12, "360668": 0, "344613": 0, "344612": 0, "344615": 21, "344614": 0, "356589": 15, "344621": 43, "356588": 0, "344620": 0, "356591": 0, "356590": 0, "344617": 0, "344616": 0, "356587": 0, "344619": 0, "356586": 0, "344618": 0, "356593": 0, "356592": 0, }; $(".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 = "f4cea328-55a5-4992-a40a-a7150b49acef"; 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(",","/")); } }); });