Social Network: a Cytoscape app for visualizing co-authorship networks

Social Network: a Cytoscape app for visualizing... | 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/4-481" }, "headline": "Social Network: a Cytoscape app for visualizing co-authorship networks", "datePublished": "2015-08-05T15:38:00", "dateModified": "2015-12-23T14:31:00", "author": [ { "@type": "Person", "name": "Victor Kofia" }, { "@type": "Person", "name": "Ruth Isserlin" }, { "@type": "Person", "name": "Alison M.J. Buchan" }, { "@type": "Person", "name": "Gary D. Bader" } ], "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": "Networks that represent connections between individuals can be valuable analytic tools. The Social Network Cytoscape app is capable of creating a visual summary of connected individuals automatically. It does this by representing relationships as networks where each node denotes an individual and an edge linking two individuals represents a connection. The app focuses on creating visual summaries of individuals connected by co-authorship links in academia, created from bibliographic databases like PubMed, Scopus and InCites. The resulting co-authorship networks can be visualized and analyzed to better understand collaborative research networks or to communicate the extent of collaboration and publication productivity among a group of researchers, like in a grant application or departmental review report. It can also be useful as a research tool to identify important research topics, researchers and papers in a subject area." } { "@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/4-481/v3", "name": "Social Network: a Cytoscape app for visualizing co-authorship networks" } } ] } Home Browse Social Network: a Cytoscape app for visualizing co-authorship networks ALL Metrics - Views Downloads Get PDF Get XML Cite How to cite this article Kofia V, Isserlin R, Buchan AMJ and Bader GD. Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.12688/f1000research.6804.3 ) NOTE: If applicable, it is important to ensure the information in square brackets after the title is included in all citations of this article. Close Copy Citation Details Export Export Citation Sciwheel EndNote Ref. Manager Bibtex ProCite Sente EXPORT Select a format first Track Share ▬ ✚ Software Tool Article Revised Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] Victor Kofia 1 , Ruth Isserlin https://orcid.org/0000-0002-6805-2080 1 , Alison M.J. Buchan 2 , Gary D. Bader https://orcid.org/0000-0003-0185-8861 1 Victor Kofia 1 , Ruth Isserlin https://orcid.org/0000-0002-6805-2080 1 , Alison M.J. Buchan 2 , Gary D. Bader https://orcid.org/0000-0003-0185-8861 1 PUBLISHED 23 Dec 2015 Author details Author details 1 The Donnelly Centre, University of Toronto, Toronto, ON, M5S 1A8, Canada 2 Faculty of Medicine, University of Toronto, Toronto, ON, M5S 1A8, Canada OPEN PEER REVIEW DETAILS REVIEWER STATUS This article is included in the Bioinformatics gateway. This article is included in the Cytoscape gateway. Abstract Networks that represent connections between individuals can be valuable analytic tools. The Social Network Cytoscape app is capable of creating a visual summary of connected individuals automatically. It does this by representing relationships as networks where each node denotes an individual and an edge linking two individuals represents a connection. The app focuses on creating visual summaries of individuals connected by co-authorship links in academia, created from bibliographic databases like PubMed, Scopus and InCites. The resulting co-authorship networks can be visualized and analyzed to better understand collaborative research networks or to communicate the extent of collaboration and publication productivity among a group of researchers, like in a grant application or departmental review report. It can also be useful as a research tool to identify important research topics, researchers and papers in a subject area. READ ALL READ LESS Keywords social network analysis, data visualization, collaborative networks, co-publication networks Corresponding Author(s) Gary D. Bader ( [email protected] ) Close Corresponding author: Gary D. Bader Competing interests: No competing interests were disclosed. Grant information: Financial support was provided by the Faculty of Medicine at the University of Toronto. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Copyright: © 2015 Kofia V et al . 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: Kofia V, Isserlin R, Buchan AMJ and Bader GD. Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.12688/f1000research.6804.3 ) First published: 05 Aug 2015, 4 :481 ( https://doi.org/10.12688/f1000research.6804.1 ) Latest published: 23 Dec 2015, 4 :481 ( https://doi.org/10.12688/f1000research.6804.3 ) Revised Amendments from Version 2 We have corrected the description of the eUtils query download limit as noted by reviewer 2. We have corrected the description of the eUtils query download limit as noted by reviewer 2. See the authors' detailed response to the review by Michael Bales and Terrie Wheeler See the authors' detailed response to the review by Jiang Bian See the authors' detailed response to the review by Shahadat Uddin READ REVIEWER RESPONSES Introduction A scientist’s research output and collaborative tendencies - at least those that can be measured based on publications - can be visually summarized as a network where each node denotes an author and edges link authors who have co-published. Such a network facilitates determining who publishes with whom and in what topics, and identifying key individuals and organizations within collaborative research networks. It is useful to create and visualize a network showing a broad overview of collaborative research publications to communicate the extent of collaboration and impact of publications. As another example, creating a collaboration network from a set of publications for a specific topic, for example “Alzheimer’s”, can help highlight experts in the field and could be useful as a research tool to help identify important topics, researchers and papers. Previously, creating co-authorship networks required users to manually retrieve the relevant data and transform it into either a formatted text file or an excel workbook that defined all the individual nodes and connections. Users would then have to import the text file or workbook into Cytoscape or another network visualization tool. To streamline this workflow, we developed the Social Network app, a Cytoscape 3 app that is capable of automatically generating visual summaries of individuals connected in academia. In the simplest mode of interaction, the user supplies the first initial and last name of the individual whose network they would like to visualize, and a co-authorship network is generated automatically from one of three currently supported bibliographic databases: PubMed, Scopus and Web of Science (via InCites). Users can also provide more complex and larger sets of publications, for example using the PubMed query system. Methods and implementation User interface The Social Network App supports both text and file-based inputs. As Figure 1 (1–4) shows, co-authorship networks can be created in four ways. With the search box, users can run queries against PubMed. A co-authorship network is automatically generated from any results that are retrieved. Alternatively, users can go directly to PubMed, Scopus or InCites web sites, search for publications, export them to a specified file format and visualize them using the app. See the user guide for detailed instructions on how to do each of these tasks ( http://baderlab.org/UserguideSocialNetworkApp ); Figure 1. Snapshot of the Social Network user interface. Co-authorship networks can be generated in four ways: (1) By entering a query into the PubMed search box. (2) Loading an InCites report (XLSX format). (3) Loading a PubMed XML file containing query results retrieved from the PubMed web interface. (4) Loading a Scopus CSV file. (5) Users can also set the maximum # of authors allowed for a publication to filter out very large author lists that may clutter the network. (6) Users can specify a time interval for the co-authorships, which can optionally be visualized as bar charts on each author node showing number of publications plotted against publication year. (7) Extra information associated with each network is displayed in the network summary panel. Often when running queries with common names (e.g. “Smith J”), the query returns publications that contain more than 500 authors. Visualizing networks containing these types of publications is challenging because generating n · ( n - 1)/2 edges for each publication ( n refers to the # of authors in the publication) is resource intensive and the large clusters created are difficult to visualize and interpret. To avoid this issue, the user panel includes a maximum author per publication field that allows users to specify the author number threshold at which publications are excluded. By default the threshold is set to 500. A co-authorship network summary panel is also included in the user panel ( Figure 1 (7)). For PubMed and Scopus networks, the panel displays the total number of publications parsed and the number of excluded publications (publications are excluded if the number of authors they have exceeds the threshold). For direct PubMed queries the panel also includes the query translation automatically performed by PubMed. Scopus and InCites networks contain institutional affiliations for all the authors of a given publication. For InCites networks, charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API ( https://developers.google.com/chart/ ). Implementation Social Network is written in the Java programming language as an app for Cytoscape 3 1 and is based on the Cytoscape 3-supported OSGi (Open Services Gateway Initiative) software architecture. To facilitate development, we developed a set of coding guidelines and defined them as Eclipse templates. The Eclipse templates and instructions on how to import them into an existing workspace are available at ( http://baderlab.org/Software/SocialNetworkApp/Development ). We also used the Maven project management tool ( https://maven.apache.org/ ) to retrieve and organize the dependencies required by the app. An outline of the required dependencies is provided in a pom file that is located in the project source code ( https://github.com/BaderLab/SocialNetworkApp ). The design of the app followed Object Oriented Principles (OOP), reflected in the following class hierarchy; To facilitate future support for other social network types, we defined a set of flexible data structures, namely: AbstractNode, AbstractEdge and SocialNetwork. These data structures are used to represent networks and conveniently associated data created by the app in a general form. They are also specialized for each network type (e.g. PubMed, InCites). We also implemented the PubMed search feature generally to support future social network sources. Implementation details are provided in the source code ( https://github.com/BaderLab/SocialNetworkApp ). Networks built from different bibliographic databases require their own unique visual styles. We implemented a standard visual style that all other visual styles extend. The standard visual style describes styles for attributes that all social networks share (e.g. name, label ) and it is used for PubMed and Scopus networks but not InCites networks. InCites networks require their own specialized visual style because they contain additional attributes ( location ) that PubMed and Scopus networks typically do not possess. We implemented a new InCites visual style by extending the standard visual style and adding new style descriptions for the locations of authors. See the source code for implementation details. Database evaluation and implementation Multiple bibliographic databases were evaluated for support by the app: PubMed, Scopus, Web of Science/InCites, and Google Scholar. Evaluation was based on application program interface (API) availability, data export capabilities, coverage, citations and update frequency (see Table 1 ). PubMed is developed and maintained by the National Center for Biotechnology Information (NCBI) as part of the U.S. National Library of Medicine and is accessible through the Entrez query system ( http://www.ncbi.nlm.nih.gov/pubmed/ ). Web of Science is a literature citation index created by Thomson Reuters containing over 90,000,000 records from all fields of science ( http://wokinfo.com/citationconnection/realfacts/ ). Web of Science data is also accessible via the Thomson Reuters InCites web-based search engine, which facilitates access to additional information, such as author institution ( http://researchanalytics.thomsonreuters.com/incites/ ). Scopus contains over 57,000,000 records, 27 million of which are patent records and 6.8 million of which are conference papers or proceedings ( http://www.elsevier.com/solutions/scopus/content ) and date back as far as 1823 ( http://www.elsevier.com/__data/assets/pdf_file/0007/69451/sc_content-coverage-guide_july-2014.pdf ). Table 1. Coverage of various bibliographic databases. Scopus temporal coverage was retrieved here http://www.elsevier.com/__data/assets/pdf_file/0007/69451/sc_content-coverage-guide_july-2014.pdf . Database Indexed Citations Temporal Coverage PubMed over 24 million 1946-present Web of Science over 90 million 1900-present Scopus over 57 million 1823-present Google Scholar 100 million–160 million 2 , 3 1700-present 3 Scopus contains author profiles that include, among other things, the institutional affiliations of an author. These profiles are helpful when disambiguating authors with very similar or identical names. Web of Science, InCites and Scopus access requires a paid subscription, which large academic institutions often provide. Google Scholar is a freely available and automatically updated database of citations with associated author pages ( https://scholar.google.com/intl/en/scholar/about.html ). Database content was evaluated by selecting a specific publication and comparing its citation counts among the different databases. Update frequency was determined by checking whether a newly published paper (published on January 1st 2015 or later) had been indexed by the database and by examining citation counts and verifying that newer citations had been captured. Prior to app development, data from PubMed, Web of Science and Scopus was available for an internal project. Thus, development was oriented towards supporting content from these three databases. Aside from Google Scholar, every database we examined had an API. Developers can access the APIs provided by both Scopus and Web of Science but a subscription is required. On the other hand, PubMed content and API access is free, easing implementation. Although both Scopus and Web of Science require paid subscriptions to view their data over the web, often large institutions have licenses to query this data which makes it accessible to many users. Scopus and Web of Science also both provide an intuitive web-based user interface that enables users to export the data to file formats that are recognizable by our app (CSV for Scopus and XLSX for Web of Science). Based on our evaluation, we chose to support PubMed (via file export and API), Scopus and Web of Science (via file export). We would have supported Google Scholar if a public API or file export was available. PubMed is the default search engine used by the app because of the accessibility of its content and the straightforward nature of its associated retrieval mechanisms: its web-based interface and the Entrez Programming Utilities (eUtils) API. Eutils enables URL-based (non-RESTful) programmatic access to data contained in PubMed as well as any other databases linked to Entrez ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ). Standard PubMed queries, for example “LastName First Initial”[Au], including recognized PubMed search tags ( http://www.nlm.nih.gov/bsd/mms/medlineelements.html ), can be entered into the PubMed search field in the app, which retrieves XML results using the eUtils web service. The results are parsed using the SAX (Simple API for XML) API included in the Java standard library and are transformed into a co-authorship network using the Cytoscape API. Nodes in the network represent authors, edges represent co-authorship and how frequently authors collaborate is indicated by the thickness of an edge. Because data is retrieved from the NCBI servers through POST calls there is no restriction on the length of queries passed to PubMed through the app ( http://www.ncbi.nlm.nih.gov/books/NBK25499/ ). Users can also construct networks from XML files exported directly from PubMed. Instructions for this workflow are provided in the app user guide: http://baderlab.org/UserguideSocialNetworkApp#PubMed . XML results obtained through eUtils differ slightly from XML results directly exported from PubMed. In particular, XML results exported from PubMed do not contain citations, whereas XML results retrieved by eUtils do. To correct this, the app retrieves this information using eUtils. Since the citation counts ultimately come from the same source regardless of how the initial data was obtained (PubMed or eUtils), networks generated via either method are equivalent. There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 100,000 publications be retrieved from a single eUtils query ( http://www.ncbi.nlm.nih.gov/books/NBK25499 ). Large data sets consisting of more than 100,000 records can be retrieved incrementally (i.e. 100,000 records at a time). There is also a limit set on the frequency of eUtils requests. A maximum of three requests is allowed per second ( http://www.ncbi.nlm.nih.gov/books/NBK25497/ ). Violating these suggested limits may result in NCBI blocking the IP address of the offender. Scopus and Web of Science (via InCites) are supported via file import. A user must manually export query results via the respective web interface. Scopus CSV exports are supported by the app. InCites reports must be saved in Excel 2007 (XLSX) format to be input into the app. The app can recognize InCites spreadsheets with exactly six columns in the following order (from left to right): times cited, expected citations, publication year, subject area, all authors and document title . Instructions on how to export results from InCites to this format are provided at http://baderlab.org/UserguideSocialNetworkApp#InCites . Results and discussion Use cases We demonstrate the app using an example from the Hughes et al. study 6 in which social network analysis was used to determine whether Alzheimer Disease Centers (ADCs) based in the United States foster collaborative research. As part of the analysis, the study authors constructed multiple co-authorship networks using publication data collected from PubMed. In the original publication, the authors created Ruby scripts to query PubMed for co-authorships for a set of over 2000 researchers affiliated with ADCs. The simplest way to interact with the app is to create either an individual researcher’s publication network or a co-authorship network for an individual organization. Using an individual author from a single ADC, Rush University Medical Center, Figure 2 shows an individual’s publication network. We created the co-authorship network by entering the researcher’s name (last name first initial, as expected by Pubmed) into the PubMed search bar (see Figure 1 ) and clicking on the ’Create Network’ button. In order to generate the co-authorship network the app parses the results returned from the query. We assumed that all the authors with the specified last name and first initial in the results correspond to a single author. However, we made no attempt at name disambiguation, thus authors with common last names may be associated with inflated numbers of publications. For an individual author the same process can be performed on the Scopus or Incites websites to retrieve output files that can be loaded by the app. Conflicting author names may still be present although having institution affiliations available – as is the case for Scopus and InCites exported data – can help in disambiguating authors. Until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. The main difference between networks generated by PubMed, Scopus and Incites is the number of citations attributed to each author. PubMed counts paper citations only for articles found in the freely available PubMed Central literature archive whereas Scopus and Incites use a much larger set of publications stored in their databases. Thus, Scopus and Incites provide more accurate citation counts. Figure 2. Publication network for an individual researcher at Rush University Medical Center. Each node represents a co-author of the original query author (the highlighted yellow node). The network was created by entering the author’s last name and first initial into the PubMed query bar within the Social Network App. The network was then automatically created. The yFiles Organic layout was applied to better visualize the network. Node size represents the cumulative number of the author’s publication citation counts as automatically retrieved from PubMed based on the set of publications associated with the node (the count only includes citations of publications that are in PubMed Central). Thickness of the edges connecting the nodes represents the number of publications the two authors have published together. Extending the simple use case, using all authors from a single institution, such as Rush University Medical Center, as a query, Figure 3A shows the resulting co-authorship network (searching PubMed for publications that have at least two Rush University ADC researchers). Figure 3B shows the co-authorship network for only the Rush University ADC researchers. The length of the query depends on the number of researchers in the query set and would have the following format: Example Department PubMed Query ( ( "LastName1 FirstInitial1"[Au] AND "LastName2 FirstInitial2"[Au] ) OR ( "LastName1 FirstInitial1"[Au] AND "LastName3 FirstInitial3"[Au] ) OR ( "LastName1 FirstInitial1"[Au] AND "LastName4 FirstInitial4"[Au] ) OR ( "LastName2 FirstInitial2"[Au] AND "LastName3 FirstInitial3"[Au] ) OR ( "LastName2 FirstInitial2"[Au] AND "LastName4 FirstInitial4"[Au] ) OR ... ) AND "Rush University Medical Center" Figure 3. Co-authorship networks for ADC researchers at Rush University Medical Center. ( A ) Each node represents an author from the set of publications that have at least one Rush ADC researcher. Orange nodes are Rush ADC researchers and red nodes are non-Rush ADC researchers. Rush ADC researchers were selected manually and their node fill color was modified using the style bypass option and set to orange. This can also be achieved by importing a node attribute mapping only to the query authors and using the imported attribute to select the nodes. Node size represents the cumulative number of the author’s publication citation counts as automatically retrieved from PubMed based on the set of publications associated with the node (the count only includes citations of publications that are in PubMed Central). Edge thickness represents the number of publications the two authors have published together. ( B ) Subset of the network in ( A ) containing only the ADC researchers. Author names are not shown to reduce visual clutter and to protect anonymity. Large cliques represent many-author publications. A university department, faculty or a collaborative group typically desires to visualize and analyze all publications from the organizational unit over a period of time to help evaluate research productivity and effectiveness. Also, users may be interested in visualizing all of the publications and their topics in a particular research area. To demonstrate how the app can be used for a more sophisticated use case that also highlights how Cytoscape features can be used as part of a workflow, a simple comparison to the original broad analysis Hughes et al. was performed. We queried PubMed for the same set of researchers as used in the Hughes et al. study. Each author was queried along with their institution to reduce false positives and the entire query was limited to publications containing “alzheimer”. The set of authors was large, leading to the creation of a large PubMed query, thus the PubMed web interface was used to execute the query. Both the Scopus and InCites web interfaces were unable to process the query and it was too long to pass to eUtils. Limiting the query to papers published in 2010 returned a set of 382 publications. Using the PubMed XML file downloaded from the PubMed website, we constructed a co-authorship network. By using Cytoscape’s filtering capabilities, we reduced the network to just the authors used in the original query (see Figure 4 ). With Cytoscape’s Styles, we colored nodes by institution as specified in the original dataset. To summarize this network we used a feature in the Enrichment Map App 7 that makes use of two other Cytoscape apps (clusterMaker 4 and WordCloud 5 ) to automatically cluster and annotate the network based on the word summaries of a given attribute. Each cluster was annotated using frequent words found in the titles of publications within each cluster. This automatically highlights the collaborative research topics included in the network. The network can be further reduced by creating groups associated with each cluster. By collapsing the groups to an individual node the complexity in the network would be substantially reduced and the resulting network would highlight research themes found in this set of publications. Figure 4. Co-authorship network for all ADC researchers from Alzheimer’s publications in 2010. Each node represents an ADC researcher and its color represents their institution (as specified in the original dataset). Node colors were automatically generated in the visual style for the ‘original institution’ attribute that was available for this author set and loaded onto the co-authorship network after its creation. Node size represents the cumulative number of the author’s publication citation counts as automatically retrieved from PubMed based on the set of publications associated with the node (the count only includes citations of publications that are in PubMed Central). Thickness of the edges connecting the nodes represents the number of publications the two authors have published together. Each cluster of authors, as calculated by the clusterMaker app 4 , is annotated with an additional circle around its members. Cluster labels aim to summarize the group with the two most frequent words in the author’s set of publication titles as computed by the WordCloud App 5 ). This workflow also illustrates the challenges of working with large co-authorship networks and large networks in general. There are many Cytoscape features and apps that can be used to reduce complexity of the network and help summarize the results. Given the limits of searching in PubMed, Scopus and Incites, a broad global analysis similar to the one conducted by Hughes et al. likely requires multiple queries, possibly automated by scripts to retrieve different data from the databases along with a process to collate and filter the results to generate the final set of publications to be analyzed. This is currently beyond the scope of this app, but more complex and automated query functionality could be added in the future. Conclusions Users interested in creating visual summaries of individuals connected via co-authorship links in academia will benefit from the Social Network App. The app aids users unfamiliar with Cytoscape by providing an intuitive and navigable user interface to query multiple bibliographic databases. Advanced users who wish to analyze large networks can take advantage of many powerful Cytoscape features. In the future we plan to expand the Social Network App to enable the creation of co-authorship networks made from multiple PubMed queries or files as well as support for Cytoscape commands which would enable scripted access to the app. We also plan to implement a system that will help disambiguate authors with common names and add support to visualize connections formed by Twitter, LinkedIn and Facebook users. Software availability Software available from http://apps.cytoscape.org/apps/socialnetworkapp Latest source code https://github.com/BaderLab/SocialNetworkApp Source code as at the time of publication https://github.com/F1000Research/SocialNetworkApp Archived source code as at time of publication http://dx.doi.org/10.5281/zenodo.19825 8 License: Lesser GNU Public License 2.1 https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html Tutorials http://baderlab.org/UserguideSocialNetworkApp Author contributions VK drafted the manuscript with assistance from RI. Both VK and RI designed and developed the software. The project was initiated by GDB and AMJB. GDB supervised the project. All authors have read and approved the final manuscript. Competing interests No competing interests were disclosed. Grant information Financial support was provided by the Faculty of Medicine at the University of Toronto. I confirm that the funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Acknowledgements We thank the authors of the Hughes et al. paper for sharing their social network data for analysis. Faculty Opinions recommended References 1. Shannon P, Markiel A, Ozier O, et al. : Cytoscape: a software environment for integrated models of biomolecular interaction networks. Genome Res. 2003; 13 (11): 2498–2504. PubMed Abstract | Publisher Full Text | Free Full Text 2. Khabsa M, Giles CL: The number of scholarly documents on the public web. PLoS One. 2014; 9 (5): e93949. PubMed Abstract | Publisher Full Text | Free Full Text 3. Orduña-Malea E, Ayllón JM, Martín-Martín A, et al. : About the size of Google Scholar: playing the numbers. arXiv preprint arXiv: 1407.6239, 2014. Reference Source 4. Morris JH, Apeltsin L, Newman AM, et al. : clusterMaker : a multi-algorithm clustering plugin for Cytoscape. BMC Bioinformatics. 2011; 12 (1): 436. PubMed Abstract | Publisher Full Text | Free Full Text 5. Oesper L, Merico D, Isserlin R, et al. : WordCloud: a Cytoscape plugin to create a visual semantic summary of networks. Source Code Biol Med. 2011; 6 (1): 7. PubMed Abstract | Publisher Full Text | Free Full Text 6. Hughes ME, Peeler J, Hogenesch JB, et al. : The growth and impact of alzheimer disease centers as measured by social network analysis. JAMA Neurol. 2014; 71 (4): 412–420. PubMed Abstract | Publisher Full Text | Free Full Text 7. Merico D, Isserlin R, Stueker O, et al. : Enrichment map: a network-based method for gene-set enrichment visualization and interpretation. PLoS One. 2010; 5 (11): e13984. PubMed Abstract | Publisher Full Text | Free Full Text 8. Kofia V, Isserlin R, Buchan AMJ, et al. : F1000Research/SocialNetworkApp. Zenodo. 2015. Data Source Comments on this article Comments (0) Version 3 VERSION 3 PUBLISHED 05 Aug 2015 ADD YOUR COMMENT Comment Author details Author details 1 The Donnelly Centre, University of Toronto, Toronto, ON, M5S 1A8, Canada 2 Faculty of Medicine, University of Toronto, Toronto, ON, M5S 1A8, Canada Competing interests No competing interests were disclosed. Grant information Financial support was provided by the Faculty of Medicine at the University of Toronto. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Article Versions (3) version 3 Revised Published: 23 Dec 2015, 4:481 https://doi.org/10.12688/f1000research.6804.3 version 2 Revised Published: 08 Oct 2015, 4:481 https://doi.org/10.12688/f1000research.6804.2 version 1 Published: 05 Aug 2015, 4:481 https://doi.org/10.12688/f1000research.6804.1 Copyright © 2015 Kofia V et al . 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 Kofia V, Isserlin R, Buchan AMJ and Bader GD. Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.12688/f1000research.6804.3 ) NOTE: If applicable, it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS track receive updates on this article Track an article to receive email alerts on any updates to this article. TRACK THIS ARTICLE Share Open Peer Review Current Reviewer Status: ? Key to Reviewer Statuses VIEW HIDE Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions Version 3 VERSION 3 PUBLISHED 23 Dec 2015 Revised Views 0 Cite How to cite this report: Uddin S. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.8161.r12522 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v3#referee-response-12522 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 18 Feb 2016 Shahadat Uddin , Faculty of Engineering & Information Technology, University of Sydney, Sydney, NSW, Australia Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.8161.r12522 The authors need to clearly articulate the contribution of the paper. In its present form, it seems that it is a paper that describes an app for co-authorship analysis with some examples of this kind of analysis. If this is the ... Continue reading READ ALL The authors need to clearly articulate the contribution of the paper. In its present form, it seems that it is a paper that describes an app for co-authorship analysis with some examples of this kind of analysis. If this is the main aim then the authors do not need the methods section. Competing Interests: No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Uddin S. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.8161.r12522 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v3#referee-response-12522 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 23 Feb 2016 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 23 Feb 2016 Author Response Thanks for your review. Yes, the main aim of this paper is to describe the app and its use. This is part of an F1000Research Channel on Cytoscape apps (see ... Continue reading Thanks for your review. Yes, the main aim of this paper is to describe the app and its use. This is part of an F1000Research Channel on Cytoscape apps (see http://f1000research.com/channels/cytoscapeapps ) and the methods section is part of the required format for this type of submission. Thanks for your review. Yes, the main aim of this paper is to describe the app and its use. This is part of an F1000Research Channel on Cytoscape apps (see http://f1000research.com/channels/cytoscapeapps ) and the methods section is part of the required format for this type of submission. Competing Interests: No competing interests were disclosed. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 23 Feb 2016 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 23 Feb 2016 Author Response Thanks for your review. Yes, the main aim of this paper is to describe the app and its use. This is part of an F1000Research Channel on Cytoscape apps (see ... Continue reading Thanks for your review. Yes, the main aim of this paper is to describe the app and its use. This is part of an F1000Research Channel on Cytoscape apps (see http://f1000research.com/channels/cytoscapeapps ) and the methods section is part of the required format for this type of submission. Thanks for your review. Yes, the main aim of this paper is to describe the app and its use. This is part of an F1000Research Channel on Cytoscape apps (see http://f1000research.com/channels/cytoscapeapps ) and the methods section is part of the required format for this type of submission. Competing Interests: No competing interests were disclosed. Close Report a concern COMMENT ON THIS REPORT Views 0 Cite How to cite this report: Bales M and Wheeler T. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.8161.r11782 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v3#referee-response-11782 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 04 Jan 2016 Michael Bales , Weill Cornell Medical College, New York, NY, USA Terrie Wheeler , Weill Cornell Medical College, New York, NY, USA Approved VIEWS 0 https://doi.org/10.5256/f1000research.8161.r11782 The authors have ... Continue reading READ ALL The authors have fully addressed our comments. Competing Interests: No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Bales M and Wheeler T. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.8161.r11782 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v3#referee-response-11782 NOTE: it is important to ensure the information in square brackets after the title is included in all citations of this article. COPY CITATION DETAILS Report a concern Respond or Comment COMMENT ON THIS REPORT Version 2 VERSION 2 PUBLISHED 08 Oct 2015 Revised Views 0 Cite How to cite this report: Bales M and Wheeler T. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7716.r10730 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v2#referee-response-10730 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 15 Oct 2015 Michael Bales , Weill Cornell Medical College, New York, NY, USA Terrie Wheeler , Weill Cornell Medical College, New York, NY, USA Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.7716.r10730 Thank you for responding to our comments. We just have one concern remaining, in reference to the following discussion: In our initial review we wrote, "On a related note, later in the sixth paragraph of the 'Database evaluation and implementation' section, ... Continue reading READ ALL Thank you for responding to our comments. We just have one concern remaining, in reference to the following discussion: In our initial review we wrote, "On a related note, later in the sixth paragraph of the 'Database evaluation and implementation' section, the authors state that 'There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query'. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. You responded: "Our apologies for the wrong citation. In “Building Customized Data Pipelines Using The Entrez Programming Utilities” ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ) under the “Handling Large Datasets” subheading, it is stated that large lists should be split into smaller batches of around 500 records. We have updated the manuscript to reflect this change." However, the new citation you provided refers to uploading UIDs, not downloading retrieved data. While it may be necessary when using Scopus, it is not necessary when using eUtils to modify queries so as to retrieve records in small batches. The actual maximum number of records that can be retrieved by a single query is 100,000, as indicated at http://www.ncbi.nlm.nih.gov/books/NBK25499/ : "Increasing retmax allows more of the retrieved UIDs to be included in the XML output, up to a maximum of 100,000 records." One of us (M.B.) has used eUtils within the last year to download many thousands of records at a time, and can personally confirm that this is indeed possible. Competing Interests: No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however we have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Bales M and Wheeler T. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7716.r10730 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v2#referee-response-10730 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 23 Dec 2015 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 23 Dec 2015 Author Response Thanks for pointing out this documentation page. Our app uses esearch for UID retrieval and esummary for document summaries which we use to gather detailed information for the app. These ... Continue reading Thanks for pointing out this documentation page. Our app uses esearch for UID retrieval and esummary for document summaries which we use to gather detailed information for the app. These have retmax limits of 100,000 and 10,000, respectively and we also confirmed these. We have switched the reference link to http://www.ncbi.nlm.nih.gov/books/NBK25499/ and updated our manuscript in this regard. Thanks for pointing out this documentation page. Our app uses esearch for UID retrieval and esummary for document summaries which we use to gather detailed information for the app. These have retmax limits of 100,000 and 10,000, respectively and we also confirmed these. We have switched the reference link to http://www.ncbi.nlm.nih.gov/books/NBK25499/ and updated our manuscript in this regard. Competing Interests: No competing interests. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 23 Dec 2015 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 23 Dec 2015 Author Response Thanks for pointing out this documentation page. Our app uses esearch for UID retrieval and esummary for document summaries which we use to gather detailed information for the app. These ... Continue reading Thanks for pointing out this documentation page. Our app uses esearch for UID retrieval and esummary for document summaries which we use to gather detailed information for the app. These have retmax limits of 100,000 and 10,000, respectively and we also confirmed these. We have switched the reference link to http://www.ncbi.nlm.nih.gov/books/NBK25499/ and updated our manuscript in this regard. Thanks for pointing out this documentation page. Our app uses esearch for UID retrieval and esummary for document summaries which we use to gather detailed information for the app. These have retmax limits of 100,000 and 10,000, respectively and we also confirmed these. We have switched the reference link to http://www.ncbi.nlm.nih.gov/books/NBK25499/ and updated our manuscript in this regard. Competing Interests: No competing interests. Close Report a concern COMMENT ON THIS REPORT Version 1 VERSION 1 PUBLISHED 05 Aug 2015 Views 0 Cite How to cite this report: Bian J. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7315.r9866 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v1#referee-response-9866 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 21 Aug 2015 Jiang Bian , Department of Health Outcomes & Policy, University of Florida, Gainesville, FL, USA Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.7315.r9866 The article describes a software as an extension of the Cytoscape that can automatically query popular citation databases (PubMed only) and derive co-authorship networks based on the query results. It's a laudable goal, and will be a welcomed tool for ... Continue reading READ ALL The article describes a software as an extension of the Cytoscape that can automatically query popular citation databases (PubMed only) and derive co-authorship networks based on the query results. It's a laudable goal, and will be a welcomed tool for researches on collaboration networks. Especially, the tool is disseminated as a open-source tool. However, there are a number of concerns. The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to a specific author when creating the author profile. However, it is not very accurate either at the beginning for common names. For studying social networks, getting accurate information is important, especially for studying Ego networks that focus on a specific person. It is not very user friendly in terms of gathering data. Only for Pubmed, users can enter queries through the tool. With other citation databases (InCites and Scopus), users will need to query the databases directly and then export the results. It is understandable that this is due to InCites and Scopus only provide paid API services. However, it is unclear whether the authors have implemented such integration for users who have paid those API services. Further, even for Pubmed search, the software relies on the users to understand Pubmed query syntax. It would be useful if the authors could provide (in addition to text Pubmed query) guided search (see Pubmed Advanced search) for common use cases in studying collaboration networks. It would be very useful, if the authors could allow users to use the same guided search interface to three all citation databases. Competing Interests: No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Bian J. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7315.r9866 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v1#referee-response-9866 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 08 Oct 2015 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 08 Oct 2015 Author Response The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to ... Continue reading The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to a specific author when creating the author profile. However, it is not very accurate either at the beginning for common names. For studying social networks, getting accurate information is important, especially for studying Ego networks that focus on a specific person. Thank you for the comment. We agree that name disambiguation is a key concern with co-authorship networks. This is something we hope to address in the app in the future. In the meantime we have added to the paper some tips to minimize this issue. As noted in response to referee 1, until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. It is not very user friendly in terms of gathering data. Only for Pubmed, users can enter queries through the tool. With other citation databases (InCites and Scopus), users will need to query the databases directly and then export the results. It is understandable that this is due to InCites and Scopus only provide paid API services. However, it is unclear whether the authors have implemented such integration for users who have paid those API services. Our apologies for the lack of clarity. Right now the app does not support API querying for users who have paid services, but we have added this to a list of planned features in our github issue tracker at https://github.com/BaderLab/SocialNetworkApp/issues Further, even for Pubmed search, the software relies on the users to understand Pubmed query syntax. It would be useful if the authors could provide (in addition to text Pubmed query) guided search (see Pubmed Advanced search) for common use cases in studying collaboration networks. It would be very useful, if the authors could allow users to use the same guided search interface to three all citation databases. Thanks for the comment. We have improved the user interface of the app and included a link to the PubMed query syntax. We have added a feature request to our issue tracker to develop a user friendly interface to assist users who may not be familiar with PubMed query syntax. For now we have included in the manuscript links to the relevant PubMed tutorials. The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to a specific author when creating the author profile. However, it is not very accurate either at the beginning for common names. For studying social networks, getting accurate information is important, especially for studying Ego networks that focus on a specific person. Thank you for the comment. We agree that name disambiguation is a key concern with co-authorship networks. This is something we hope to address in the app in the future. In the meantime we have added to the paper some tips to minimize this issue. As noted in response to referee 1, until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. It is not very user friendly in terms of gathering data. Only for Pubmed, users can enter queries through the tool. With other citation databases (InCites and Scopus), users will need to query the databases directly and then export the results. It is understandable that this is due to InCites and Scopus only provide paid API services. However, it is unclear whether the authors have implemented such integration for users who have paid those API services. Our apologies for the lack of clarity. Right now the app does not support API querying for users who have paid services, but we have added this to a list of planned features in our github issue tracker at https://github.com/BaderLab/SocialNetworkApp/issues Further, even for Pubmed search, the software relies on the users to understand Pubmed query syntax. It would be useful if the authors could provide (in addition to text Pubmed query) guided search (see Pubmed Advanced search) for common use cases in studying collaboration networks. It would be very useful, if the authors could allow users to use the same guided search interface to three all citation databases. Thanks for the comment. We have improved the user interface of the app and included a link to the PubMed query syntax. We have added a feature request to our issue tracker to develop a user friendly interface to assist users who may not be familiar with PubMed query syntax. For now we have included in the manuscript links to the relevant PubMed tutorials. Competing Interests: No competing interests. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 08 Oct 2015 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 08 Oct 2015 Author Response The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to ... Continue reading The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to a specific author when creating the author profile. However, it is not very accurate either at the beginning for common names. For studying social networks, getting accurate information is important, especially for studying Ego networks that focus on a specific person. Thank you for the comment. We agree that name disambiguation is a key concern with co-authorship networks. This is something we hope to address in the app in the future. In the meantime we have added to the paper some tips to minimize this issue. As noted in response to referee 1, until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. It is not very user friendly in terms of gathering data. Only for Pubmed, users can enter queries through the tool. With other citation databases (InCites and Scopus), users will need to query the databases directly and then export the results. It is understandable that this is due to InCites and Scopus only provide paid API services. However, it is unclear whether the authors have implemented such integration for users who have paid those API services. Our apologies for the lack of clarity. Right now the app does not support API querying for users who have paid services, but we have added this to a list of planned features in our github issue tracker at https://github.com/BaderLab/SocialNetworkApp/issues Further, even for Pubmed search, the software relies on the users to understand Pubmed query syntax. It would be useful if the authors could provide (in addition to text Pubmed query) guided search (see Pubmed Advanced search) for common use cases in studying collaboration networks. It would be very useful, if the authors could allow users to use the same guided search interface to three all citation databases. Thanks for the comment. We have improved the user interface of the app and included a link to the PubMed query syntax. We have added a feature request to our issue tracker to develop a user friendly interface to assist users who may not be familiar with PubMed query syntax. For now we have included in the manuscript links to the relevant PubMed tutorials. The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to a specific author when creating the author profile. However, it is not very accurate either at the beginning for common names. For studying social networks, getting accurate information is important, especially for studying Ego networks that focus on a specific person. Thank you for the comment. We agree that name disambiguation is a key concern with co-authorship networks. This is something we hope to address in the app in the future. In the meantime we have added to the paper some tips to minimize this issue. As noted in response to referee 1, until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. It is not very user friendly in terms of gathering data. Only for Pubmed, users can enter queries through the tool. With other citation databases (InCites and Scopus), users will need to query the databases directly and then export the results. It is understandable that this is due to InCites and Scopus only provide paid API services. However, it is unclear whether the authors have implemented such integration for users who have paid those API services. Our apologies for the lack of clarity. Right now the app does not support API querying for users who have paid services, but we have added this to a list of planned features in our github issue tracker at https://github.com/BaderLab/SocialNetworkApp/issues Further, even for Pubmed search, the software relies on the users to understand Pubmed query syntax. It would be useful if the authors could provide (in addition to text Pubmed query) guided search (see Pubmed Advanced search) for common use cases in studying collaboration networks. It would be very useful, if the authors could allow users to use the same guided search interface to three all citation databases. Thanks for the comment. We have improved the user interface of the app and included a link to the PubMed query syntax. We have added a feature request to our issue tracker to develop a user friendly interface to assist users who may not be familiar with PubMed query syntax. For now we have included in the manuscript links to the relevant PubMed tutorials. Competing Interests: No competing interests. Close Report a concern COMMENT ON THIS REPORT Views 0 Cite How to cite this report: Bales M and Wheeler T. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7315.r9859 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v1#referee-response-9859 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 14 Aug 2015 Michael Bales , Weill Cornell Medical College, New York, NY, USA Terrie Wheeler , Weill Cornell Medical College, New York, NY, USA Approved with Reservations VIEWS 0 https://doi.org/10.5256/f1000research.7315.r9859 The authors describe a tool that allows users to create co-authorship network diagrams within the Cytoscape application. This tool simplifies the network production process into as few as two steps: users can enter a PubMed query and then click the ... Continue reading READ ALL The authors describe a tool that allows users to create co-authorship network diagrams within the Cytoscape application. This tool simplifies the network production process into as few as two steps: users can enter a PubMed query and then click the “search” button. A co-authorship network is generated automatically and displayed in Cytoscape; users can then use features available within Cytoscape to carry out additional tasks, such as adjusting visual properties and measuring topological measures of network structure. The system also supports searches to Scopus and Web of Science (via InCites). The authors illustrate the system’s design and functions, describe how to use it, and present a use case in which they use the tool to replicate a search carried out in a study by Hughes et al . In so doing they highlight several challenges that may occur when working with large co-authorship networks. The authors contend that co-authorship network visualization can be useful for understanding collaborative research networks or for “communicating the extent of collaboration and publication productivity among a group of researchers”. In this paper the authors do not conceive of a method to evaluate their app, for example to assess satisfaction with the app among system users, or to see whether system users are able to integrate the app into meaningful workflows. The authors report that they plan to continue developing the app, for example, by extending it so that it can display data from Facebook, Twitter, and LinkedIn. The availability of the software is a welcome addition to existing tools for co-authorship network production. Its automated features and relatively seamless integration into Cytoscape will (we expect) make it an appealing option for analysts; to the extent possible it takes care of tedious steps that analysts may be accustomed to carrying out manually. We have identified several minor points for the authors to take into consideration. First, in the sixth paragraph of the “Database evaluation and implementation” section, the authors mention that E-utilities queries are limited to several hundred characters. While this may be the case for standard E-utilities queries, it is possible by using an HTTP Post call to make significantly longer queries. From Sayers E. The E-Utilities In-Depth: Parameters, Syntax, and More, http://www.ncbi.nlm.nih.gov/books/NBK25499/ : “For very long queries (more than several hundred characters long), consider using an HTTP POST call.” In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and it was successful. In any case we would like to request clarification, as it appears that the current version of the system may be capable of longer queries, possibly by doing an HTTP Post request. On a related note, later in the sixth paragraph of the “Database evaluation and implementation” section, the authors state that “There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query”. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. It is true, as the authors also point out, that requests should be limited to a maximum of three per second. Additionally, large jobs are to be limited to nights and weekends Eastern time ( http://www.ncbi.nlm.nih.gov/books/NBK25497/ ). However, if there is a stated recommendation that no more than 500 publications be retrieved from a single eUtils query, we request that the authors identify a different source in which this is indicated in writing. In the fourth paragraph of the “Database evaluation and implementation” section the authors mention that “Scopus and Web of Science APIs require paid subscriptions”. It is our understanding that Web of Science has an API that is free to subscribers, in addition to a paid API with more data fields. We would like clarification on whether the authors were referring to the API that is free to subscribers. In the second paragraph of the “Results and discussion” section the authors state, “We created the co-publication network by entering the researcher’s name (last name first initial, as expected by PubMed) … and clicking on the search button”. Due to the problem of ambiguous names in PubMed, it should be noted that this approach, without an attempt at name disambiguation, may result in many false drops, leading to invalid networks. In the third paragraph of the “Methods and implementation” section the authors mention that the user panel includes a co-publication network summary panel. Later in this paragraph they mention “charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API.” We have thus far been unable to locate the network summary panel or the links to the charts, so further detail would be helpful here to describe the circumstances under which these features may be used, and/or how to activate and find them. We also have some minor editorial suggestions. First, we wanted to point out that “co-authorship” networks is far more common in the literature than “co-publication” networks, so the authors may wish to switch to this term if desired. Second, in the third paragraph of the “Methods and Implementation” section the authors point out that “Because InCites networks contain institutional affiliations for all the authors of a given publication, they have richer summaries.” It may also be worth pointing out here that Scopus does this as well. Third, the sixth paragraph of the “Database evaluation and implementation” section contains a broken link ( http://baderlab.org/Software/SocialNetworkApp#PubMed ). We applaud the authors for making this app available for use within a freely available tool that has an active user base and community of users, and are hopeful that the authors will continue with active development of this tool, so that they may be responsive to user suggestions that may further improve the user experience and integration into workflows. Competing Interests: No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however we have significant reservations, as outlined above. Close READ LESS CITE CITE HOW TO CITE THIS REPORT Bales M and Wheeler T. Reviewer Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7315.r9859 ) The direct URL for this report is: https://f1000research.com/articles/4-481/v1#referee-response-9859 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 08 Oct 2015 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 08 Oct 2015 Author Response In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and ... Continue reading In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and it was successful. In any case we would like to request clarification, as it appears that the current version of the system may be capable of longer queries, possibly by doing an HTTP Post request. Thanks for pointing this out. We have now modified the app to use POST for all queries, which will be part of the next release. On a related note, later in the sixth paragraph of the “Database evaluation and implementation” section, the authors state that “There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query”. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. Our apologies for the wrong citation. In “Building Customized Data Pipelines Using The Entrez Programming Utilities” ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ) under the “Handling Large Datasets” subheading, it is stated that large lists should be split into smaller batches of around 500 records. We have updated the manuscript to reflect this change. In the fourth paragraph of the “Database evaluation and implementation” section the authors mention that “Scopus and Web of Science APIs require paid subscriptions”. It is our understanding that Web of Science has an API that is free to subscribers, in addition to a paid API with more data fields. We would like clarification on whether the authors were referring to the API that is free to subscribers. We were referring to both APIs. Since users have to be subscribed to Web of Science to access the ‘free’ API we classified it as ‘requiring a paid subscription’. We have clarified this point in the revision. In the second paragraph of the “Results and discussion” section the authors state, “We created the co-publication network by entering the researcher’s name (last name first initial, as expected by PubMed) … and clicking on the search button”. Due to the problem of ambiguous names in PubMed, it should be noted that this approach, without an attempt at name disambiguation, may result in many false drops, leading to invalid networks. We agree with the reviewer. Name disambiguation is definitely a problem when constructing co-authorship networks in this way. And it is a problem that affects all databases. We have updated the text to reflect this as it is something that all readers should be aware of. Until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. In the third paragraph of the “Methods and implementation” section the authors mention that the user panel includes a co-publication network summary panel. Later in this paragraph they mention “charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API.” We have thus far been unable to locate the network summary panel or the links to the charts, so further detail would be helpful here to describe the circumstances under which these features may be used, and/or how to activate and find them. The network summary panel is located at the bottom of the user panel. Instead of a figure that only shows the top half of the panel we have included a new figure that contains the entire panel as this will enable readers to view the sections we are referring to. If no network summary panel exists in your setup and the problem persists then it may be a bug, in which case we would appreciate it being filed as a bug report on GitHub (https://github.com/BaderLab/SocialNetworkApp/issues) or emailed to us so we can fix it. Also note that even with the network summary panel being visible, links to the charts will only appear after an InCites network has been created. No charts are available for Scopus and PubMed networks at the moment. So please verify that you are using an InCites document to build the network. An example InCites document is provided in the user guide: http://baderlab.org/Software/SocialNetworkApp. We have made this clearer in the text. We also have some minor editorial suggestions. First, we wanted to point out that “co-authorship” networks is far more common in the literature than “co-publication” networks, so the authors may wish to switch to this term if desired. Thank you for pointing this out. We have switched to using the more common “co-authorship” term throughout the manuscript. Second, in the third paragraph of the “Methods and Implementation” section the authors point out that “Because InCites networks contain institutional affiliations for all the authors of a given publication, they have richer summaries.” It may also be worth pointing out here that Scopus does this as well. It is indeed true that Scopus provides institutional affiliations. The default setting for exporting files from Scopus is “Citation Information Only” which does not include the institutional affiliations of the co-authors. We have extended the functionality so that the app is capable of parsing Scopus reports that contain additional information (like institutional affiliations). We have made a note of this in the online manual. Third, the sixth paragraph of the “Database evaluation and implementation” section contains a broken link ( http://baderlab.org/Software/SocialNetworkApp#PubMed ). Thanks for noticing this. We have updated the manuscript to include the correct link: http://baderlab.org/UserguideSocialNetworkApp#PubMed We applaud the authors for making this app available for use within a freely available tool that has an active user base and community of users, and are hopeful that the authors will continue with active development of this tool, so that they may be responsive to user suggestions that may further improve the user experience and integration into workflows. Thank you for taking the time to review our app. In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and it was successful. In any case we would like to request clarification, as it appears that the current version of the system may be capable of longer queries, possibly by doing an HTTP Post request. Thanks for pointing this out. We have now modified the app to use POST for all queries, which will be part of the next release. On a related note, later in the sixth paragraph of the “Database evaluation and implementation” section, the authors state that “There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query”. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. Our apologies for the wrong citation. In “Building Customized Data Pipelines Using The Entrez Programming Utilities” ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ) under the “Handling Large Datasets” subheading, it is stated that large lists should be split into smaller batches of around 500 records. We have updated the manuscript to reflect this change. In the fourth paragraph of the “Database evaluation and implementation” section the authors mention that “Scopus and Web of Science APIs require paid subscriptions”. It is our understanding that Web of Science has an API that is free to subscribers, in addition to a paid API with more data fields. We would like clarification on whether the authors were referring to the API that is free to subscribers. We were referring to both APIs. Since users have to be subscribed to Web of Science to access the ‘free’ API we classified it as ‘requiring a paid subscription’. We have clarified this point in the revision. In the second paragraph of the “Results and discussion” section the authors state, “We created the co-publication network by entering the researcher’s name (last name first initial, as expected by PubMed) … and clicking on the search button”. Due to the problem of ambiguous names in PubMed, it should be noted that this approach, without an attempt at name disambiguation, may result in many false drops, leading to invalid networks. We agree with the reviewer. Name disambiguation is definitely a problem when constructing co-authorship networks in this way. And it is a problem that affects all databases. We have updated the text to reflect this as it is something that all readers should be aware of. Until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. In the third paragraph of the “Methods and implementation” section the authors mention that the user panel includes a co-publication network summary panel. Later in this paragraph they mention “charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API.” We have thus far been unable to locate the network summary panel or the links to the charts, so further detail would be helpful here to describe the circumstances under which these features may be used, and/or how to activate and find them. The network summary panel is located at the bottom of the user panel. Instead of a figure that only shows the top half of the panel we have included a new figure that contains the entire panel as this will enable readers to view the sections we are referring to. If no network summary panel exists in your setup and the problem persists then it may be a bug, in which case we would appreciate it being filed as a bug report on GitHub (https://github.com/BaderLab/SocialNetworkApp/issues) or emailed to us so we can fix it. Also note that even with the network summary panel being visible, links to the charts will only appear after an InCites network has been created. No charts are available for Scopus and PubMed networks at the moment. So please verify that you are using an InCites document to build the network. An example InCites document is provided in the user guide: http://baderlab.org/Software/SocialNetworkApp. We have made this clearer in the text. We also have some minor editorial suggestions. First, we wanted to point out that “co-authorship” networks is far more common in the literature than “co-publication” networks, so the authors may wish to switch to this term if desired. Thank you for pointing this out. We have switched to using the more common “co-authorship” term throughout the manuscript. Second, in the third paragraph of the “Methods and Implementation” section the authors point out that “Because InCites networks contain institutional affiliations for all the authors of a given publication, they have richer summaries.” It may also be worth pointing out here that Scopus does this as well. It is indeed true that Scopus provides institutional affiliations. The default setting for exporting files from Scopus is “Citation Information Only” which does not include the institutional affiliations of the co-authors. We have extended the functionality so that the app is capable of parsing Scopus reports that contain additional information (like institutional affiliations). We have made a note of this in the online manual. Third, the sixth paragraph of the “Database evaluation and implementation” section contains a broken link ( http://baderlab.org/Software/SocialNetworkApp#PubMed ). Thanks for noticing this. We have updated the manuscript to include the correct link: http://baderlab.org/UserguideSocialNetworkApp#PubMed We applaud the authors for making this app available for use within a freely available tool that has an active user base and community of users, and are hopeful that the authors will continue with active development of this tool, so that they may be responsive to user suggestions that may further improve the user experience and integration into workflows. Thank you for taking the time to review our app. Competing Interests: No competing interests were disclosed. Close Report a concern Respond or Comment COMMENTS ON THIS REPORT Author Response 08 Oct 2015 Victor Kofia , The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada 08 Oct 2015 Author Response In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and ... Continue reading In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and it was successful. In any case we would like to request clarification, as it appears that the current version of the system may be capable of longer queries, possibly by doing an HTTP Post request. Thanks for pointing this out. We have now modified the app to use POST for all queries, which will be part of the next release. On a related note, later in the sixth paragraph of the “Database evaluation and implementation” section, the authors state that “There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query”. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. Our apologies for the wrong citation. In “Building Customized Data Pipelines Using The Entrez Programming Utilities” ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ) under the “Handling Large Datasets” subheading, it is stated that large lists should be split into smaller batches of around 500 records. We have updated the manuscript to reflect this change. In the fourth paragraph of the “Database evaluation and implementation” section the authors mention that “Scopus and Web of Science APIs require paid subscriptions”. It is our understanding that Web of Science has an API that is free to subscribers, in addition to a paid API with more data fields. We would like clarification on whether the authors were referring to the API that is free to subscribers. We were referring to both APIs. Since users have to be subscribed to Web of Science to access the ‘free’ API we classified it as ‘requiring a paid subscription’. We have clarified this point in the revision. In the second paragraph of the “Results and discussion” section the authors state, “We created the co-publication network by entering the researcher’s name (last name first initial, as expected by PubMed) … and clicking on the search button”. Due to the problem of ambiguous names in PubMed, it should be noted that this approach, without an attempt at name disambiguation, may result in many false drops, leading to invalid networks. We agree with the reviewer. Name disambiguation is definitely a problem when constructing co-authorship networks in this way. And it is a problem that affects all databases. We have updated the text to reflect this as it is something that all readers should be aware of. Until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. In the third paragraph of the “Methods and implementation” section the authors mention that the user panel includes a co-publication network summary panel. Later in this paragraph they mention “charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API.” We have thus far been unable to locate the network summary panel or the links to the charts, so further detail would be helpful here to describe the circumstances under which these features may be used, and/or how to activate and find them. The network summary panel is located at the bottom of the user panel. Instead of a figure that only shows the top half of the panel we have included a new figure that contains the entire panel as this will enable readers to view the sections we are referring to. If no network summary panel exists in your setup and the problem persists then it may be a bug, in which case we would appreciate it being filed as a bug report on GitHub (https://github.com/BaderLab/SocialNetworkApp/issues) or emailed to us so we can fix it. Also note that even with the network summary panel being visible, links to the charts will only appear after an InCites network has been created. No charts are available for Scopus and PubMed networks at the moment. So please verify that you are using an InCites document to build the network. An example InCites document is provided in the user guide: http://baderlab.org/Software/SocialNetworkApp. We have made this clearer in the text. We also have some minor editorial suggestions. First, we wanted to point out that “co-authorship” networks is far more common in the literature than “co-publication” networks, so the authors may wish to switch to this term if desired. Thank you for pointing this out. We have switched to using the more common “co-authorship” term throughout the manuscript. Second, in the third paragraph of the “Methods and Implementation” section the authors point out that “Because InCites networks contain institutional affiliations for all the authors of a given publication, they have richer summaries.” It may also be worth pointing out here that Scopus does this as well. It is indeed true that Scopus provides institutional affiliations. The default setting for exporting files from Scopus is “Citation Information Only” which does not include the institutional affiliations of the co-authors. We have extended the functionality so that the app is capable of parsing Scopus reports that contain additional information (like institutional affiliations). We have made a note of this in the online manual. Third, the sixth paragraph of the “Database evaluation and implementation” section contains a broken link ( http://baderlab.org/Software/SocialNetworkApp#PubMed ). Thanks for noticing this. We have updated the manuscript to include the correct link: http://baderlab.org/UserguideSocialNetworkApp#PubMed We applaud the authors for making this app available for use within a freely available tool that has an active user base and community of users, and are hopeful that the authors will continue with active development of this tool, so that they may be responsive to user suggestions that may further improve the user experience and integration into workflows. Thank you for taking the time to review our app. In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and it was successful. In any case we would like to request clarification, as it appears that the current version of the system may be capable of longer queries, possibly by doing an HTTP Post request. Thanks for pointing this out. We have now modified the app to use POST for all queries, which will be part of the next release. On a related note, later in the sixth paragraph of the “Database evaluation and implementation” section, the authors state that “There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query”. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. Our apologies for the wrong citation. In “Building Customized Data Pipelines Using The Entrez Programming Utilities” ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ) under the “Handling Large Datasets” subheading, it is stated that large lists should be split into smaller batches of around 500 records. We have updated the manuscript to reflect this change. In the fourth paragraph of the “Database evaluation and implementation” section the authors mention that “Scopus and Web of Science APIs require paid subscriptions”. It is our understanding that Web of Science has an API that is free to subscribers, in addition to a paid API with more data fields. We would like clarification on whether the authors were referring to the API that is free to subscribers. We were referring to both APIs. Since users have to be subscribed to Web of Science to access the ‘free’ API we classified it as ‘requiring a paid subscription’. We have clarified this point in the revision. In the second paragraph of the “Results and discussion” section the authors state, “We created the co-publication network by entering the researcher’s name (last name first initial, as expected by PubMed) … and clicking on the search button”. Due to the problem of ambiguous names in PubMed, it should be noted that this approach, without an attempt at name disambiguation, may result in many false drops, leading to invalid networks. We agree with the reviewer. Name disambiguation is definitely a problem when constructing co-authorship networks in this way. And it is a problem that affects all databases. We have updated the text to reflect this as it is something that all readers should be aware of. Until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. In the third paragraph of the “Methods and implementation” section the authors mention that the user panel includes a co-publication network summary panel. Later in this paragraph they mention “charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API.” We have thus far been unable to locate the network summary panel or the links to the charts, so further detail would be helpful here to describe the circumstances under which these features may be used, and/or how to activate and find them. The network summary panel is located at the bottom of the user panel. Instead of a figure that only shows the top half of the panel we have included a new figure that contains the entire panel as this will enable readers to view the sections we are referring to. If no network summary panel exists in your setup and the problem persists then it may be a bug, in which case we would appreciate it being filed as a bug report on GitHub (https://github.com/BaderLab/SocialNetworkApp/issues) or emailed to us so we can fix it. Also note that even with the network summary panel being visible, links to the charts will only appear after an InCites network has been created. No charts are available for Scopus and PubMed networks at the moment. So please verify that you are using an InCites document to build the network. An example InCites document is provided in the user guide: http://baderlab.org/Software/SocialNetworkApp. We have made this clearer in the text. We also have some minor editorial suggestions. First, we wanted to point out that “co-authorship” networks is far more common in the literature than “co-publication” networks, so the authors may wish to switch to this term if desired. Thank you for pointing this out. We have switched to using the more common “co-authorship” term throughout the manuscript. Second, in the third paragraph of the “Methods and Implementation” section the authors point out that “Because InCites networks contain institutional affiliations for all the authors of a given publication, they have richer summaries.” It may also be worth pointing out here that Scopus does this as well. It is indeed true that Scopus provides institutional affiliations. The default setting for exporting files from Scopus is “Citation Information Only” which does not include the institutional affiliations of the co-authors. We have extended the functionality so that the app is capable of parsing Scopus reports that contain additional information (like institutional affiliations). We have made a note of this in the online manual. Third, the sixth paragraph of the “Database evaluation and implementation” section contains a broken link ( http://baderlab.org/Software/SocialNetworkApp#PubMed ). Thanks for noticing this. We have updated the manuscript to include the correct link: http://baderlab.org/UserguideSocialNetworkApp#PubMed We applaud the authors for making this app available for use within a freely available tool that has an active user base and community of users, and are hopeful that the authors will continue with active development of this tool, so that they may be responsive to user suggestions that may further improve the user experience and integration into workflows. Thank you for taking the time to review our app. Competing Interests: No competing interests were disclosed. Close Report a concern COMMENT ON THIS REPORT Comments on this article Comments (0) Version 3 VERSION 3 PUBLISHED 05 Aug 2015 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 Version 3 (revision) 23 Dec 15 read read Version 2 (revision) 08 Oct 15 read Version 1 05 Aug 15 read read Michael Bales , Weill Cornell Medical College, New York, USA Terrie Wheeler , Weill Cornell Medical College, New York, USA Jiang Bian , University of Florida, Gainesville, USA Shahadat Uddin , University of Sydney, Sydney, Australia 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 © 2016 Uddin S. 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. 18 Feb 2016 | for Version 3 Shahadat Uddin , Faculty of Engineering & Information Technology, University of Sydney, Sydney, NSW, Australia 0 Views copyright © 2016 Uddin S. 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 authors need to clearly articulate the contribution of the paper. In its present form, it seems that it is a paper that describes an app for co-authorship analysis with some examples of this kind of analysis. If this is the main aim then the authors do not need the methods section. Competing Interests No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 23 Feb 2016 Victor Kofia, The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada Thanks for your review. Yes, the main aim of this paper is to describe the app and its use. This is part of an F1000Research Channel on Cytoscape apps (see http://f1000research.com/channels/cytoscapeapps ) and the methods section is part of the required format for this type of submission. View more View less Competing Interests No competing interests were disclosed. reply Respond Report a concern Uddin S. Peer Review Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.8161.r12522) 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/4-481/v3#referee-response-12522 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2016 Bales M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 04 Jan 2016 | for Version 3 Michael Bales , Weill Cornell Medical College, New York, NY, USA Terrie Wheeler , Weill Cornell Medical College, New York, NY, USA 0 Views copyright © 2016 Bales M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (0) Approved info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions The authors have fully addressed our comments. Competing Interests No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard. reply Respond to this report Responses (0) Bales M and Wheeler T. Peer Review Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.8161.r11782) 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/4-481/v3#referee-response-11782 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2015 Bales M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 15 Oct 2015 | for Version 2 Michael Bales , Weill Cornell Medical College, New York, NY, USA Terrie Wheeler , Weill Cornell Medical College, New York, NY, USA 0 Views copyright © 2015 Bales M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (1) Approved With Reservations info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions Thank you for responding to our comments. We just have one concern remaining, in reference to the following discussion: In our initial review we wrote, "On a related note, later in the sixth paragraph of the 'Database evaluation and implementation' section, the authors state that 'There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query'. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. You responded: "Our apologies for the wrong citation. In “Building Customized Data Pipelines Using The Entrez Programming Utilities” ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ) under the “Handling Large Datasets” subheading, it is stated that large lists should be split into smaller batches of around 500 records. We have updated the manuscript to reflect this change." However, the new citation you provided refers to uploading UIDs, not downloading retrieved data. While it may be necessary when using Scopus, it is not necessary when using eUtils to modify queries so as to retrieve records in small batches. The actual maximum number of records that can be retrieved by a single query is 100,000, as indicated at http://www.ncbi.nlm.nih.gov/books/NBK25499/ : "Increasing retmax allows more of the retrieved UIDs to be included in the XML output, up to a maximum of 100,000 records." One of us (M.B.) has used eUtils within the last year to download many thousands of records at a time, and can personally confirm that this is indeed possible. Competing Interests No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however we have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 23 Dec 2015 Victor Kofia, The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada Thanks for pointing out this documentation page. Our app uses esearch for UID retrieval and esummary for document summaries which we use to gather detailed information for the app. These have retmax limits of 100,000 and 10,000, respectively and we also confirmed these. We have switched the reference link to http://www.ncbi.nlm.nih.gov/books/NBK25499/ and updated our manuscript in this regard. View more View less Competing Interests No competing interests. reply Respond Report a concern Bales M and Wheeler T. Peer Review Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7716.r10730) 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/4-481/v2#referee-response-10730 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2015 Bian J. 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. 21 Aug 2015 | for Version 1 Jiang Bian , Department of Health Outcomes & Policy, University of Florida, Gainesville, FL, USA 0 Views copyright © 2015 Bian J. 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 article describes a software as an extension of the Cytoscape that can automatically query popular citation databases (PubMed only) and derive co-authorship networks based on the query results. It's a laudable goal, and will be a welcomed tool for researches on collaboration networks. Especially, the tool is disseminated as a open-source tool. However, there are a number of concerns. The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to a specific author when creating the author profile. However, it is not very accurate either at the beginning for common names. For studying social networks, getting accurate information is important, especially for studying Ego networks that focus on a specific person. It is not very user friendly in terms of gathering data. Only for Pubmed, users can enter queries through the tool. With other citation databases (InCites and Scopus), users will need to query the databases directly and then export the results. It is understandable that this is due to InCites and Scopus only provide paid API services. However, it is unclear whether the authors have implemented such integration for users who have paid those API services. Further, even for Pubmed search, the software relies on the users to understand Pubmed query syntax. It would be useful if the authors could provide (in addition to text Pubmed query) guided search (see Pubmed Advanced search) for common use cases in studying collaboration networks. It would be very useful, if the authors could allow users to use the same guided search interface to three all citation databases. Competing Interests No competing interests were disclosed. I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 08 Oct 2015 Victor Kofia, The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada The software does not have any process for disambiguation. This is problematic. In general, citation databases do not provide disambiguation services. Google Scholar attempts to "learn" which publications belong to a specific author when creating the author profile. However, it is not very accurate either at the beginning for common names. For studying social networks, getting accurate information is important, especially for studying Ego networks that focus on a specific person. Thank you for the comment. We agree that name disambiguation is a key concern with co-authorship networks. This is something we hope to address in the app in the future. In the meantime we have added to the paper some tips to minimize this issue. As noted in response to referee 1, until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. It is not very user friendly in terms of gathering data. Only for Pubmed, users can enter queries through the tool. With other citation databases (InCites and Scopus), users will need to query the databases directly and then export the results. It is understandable that this is due to InCites and Scopus only provide paid API services. However, it is unclear whether the authors have implemented such integration for users who have paid those API services. Our apologies for the lack of clarity. Right now the app does not support API querying for users who have paid services, but we have added this to a list of planned features in our github issue tracker at https://github.com/BaderLab/SocialNetworkApp/issues Further, even for Pubmed search, the software relies on the users to understand Pubmed query syntax. It would be useful if the authors could provide (in addition to text Pubmed query) guided search (see Pubmed Advanced search) for common use cases in studying collaboration networks. It would be very useful, if the authors could allow users to use the same guided search interface to three all citation databases. Thanks for the comment. We have improved the user interface of the app and included a link to the PubMed query syntax. We have added a feature request to our issue tracker to develop a user friendly interface to assist users who may not be familiar with PubMed query syntax. For now we have included in the manuscript links to the relevant PubMed tutorials. View more View less Competing Interests No competing interests. reply Respond Report a concern Bian J. Peer Review Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7315.r9866) 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/4-481/v1#referee-response-9866 keyboard_arrow_left Back to all reports Reviewer Report 0 Views copyright © 2015 Bales M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. 14 Aug 2015 | for Version 1 Michael Bales , Weill Cornell Medical College, New York, NY, USA Terrie Wheeler , Weill Cornell Medical College, New York, NY, USA 0 Views copyright © 2015 Bales M et al. This is an open access peer review report distributed under the terms of the Creative Commons Attribution License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. format_quote Cite this report speaker_notes Responses (1) Approved With Reservations info_outline Alongside their report, reviewers assign a status to the article: Approved The paper is scientifically sound in its current form and only minor, if any, improvements are suggested Approved with reservations A number of small changes, sometimes more significant revisions are required to address specific details and improve the papers academic merit. Not approved Fundamental flaws in the paper seriously undermine the findings and conclusions The authors describe a tool that allows users to create co-authorship network diagrams within the Cytoscape application. This tool simplifies the network production process into as few as two steps: users can enter a PubMed query and then click the “search” button. A co-authorship network is generated automatically and displayed in Cytoscape; users can then use features available within Cytoscape to carry out additional tasks, such as adjusting visual properties and measuring topological measures of network structure. The system also supports searches to Scopus and Web of Science (via InCites). The authors illustrate the system’s design and functions, describe how to use it, and present a use case in which they use the tool to replicate a search carried out in a study by Hughes et al . In so doing they highlight several challenges that may occur when working with large co-authorship networks. The authors contend that co-authorship network visualization can be useful for understanding collaborative research networks or for “communicating the extent of collaboration and publication productivity among a group of researchers”. In this paper the authors do not conceive of a method to evaluate their app, for example to assess satisfaction with the app among system users, or to see whether system users are able to integrate the app into meaningful workflows. The authors report that they plan to continue developing the app, for example, by extending it so that it can display data from Facebook, Twitter, and LinkedIn. The availability of the software is a welcome addition to existing tools for co-authorship network production. Its automated features and relatively seamless integration into Cytoscape will (we expect) make it an appealing option for analysts; to the extent possible it takes care of tedious steps that analysts may be accustomed to carrying out manually. We have identified several minor points for the authors to take into consideration. First, in the sixth paragraph of the “Database evaluation and implementation” section, the authors mention that E-utilities queries are limited to several hundred characters. While this may be the case for standard E-utilities queries, it is possible by using an HTTP Post call to make significantly longer queries. From Sayers E. The E-Utilities In-Depth: Parameters, Syntax, and More, http://www.ncbi.nlm.nih.gov/books/NBK25499/ : “For very long queries (more than several hundred characters long), consider using an HTTP POST call.” In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and it was successful. In any case we would like to request clarification, as it appears that the current version of the system may be capable of longer queries, possibly by doing an HTTP Post request. On a related note, later in the sixth paragraph of the “Database evaluation and implementation” section, the authors state that “There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query”. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. It is true, as the authors also point out, that requests should be limited to a maximum of three per second. Additionally, large jobs are to be limited to nights and weekends Eastern time ( http://www.ncbi.nlm.nih.gov/books/NBK25497/ ). However, if there is a stated recommendation that no more than 500 publications be retrieved from a single eUtils query, we request that the authors identify a different source in which this is indicated in writing. In the fourth paragraph of the “Database evaluation and implementation” section the authors mention that “Scopus and Web of Science APIs require paid subscriptions”. It is our understanding that Web of Science has an API that is free to subscribers, in addition to a paid API with more data fields. We would like clarification on whether the authors were referring to the API that is free to subscribers. In the second paragraph of the “Results and discussion” section the authors state, “We created the co-publication network by entering the researcher’s name (last name first initial, as expected by PubMed) … and clicking on the search button”. Due to the problem of ambiguous names in PubMed, it should be noted that this approach, without an attempt at name disambiguation, may result in many false drops, leading to invalid networks. In the third paragraph of the “Methods and implementation” section the authors mention that the user panel includes a co-publication network summary panel. Later in this paragraph they mention “charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API.” We have thus far been unable to locate the network summary panel or the links to the charts, so further detail would be helpful here to describe the circumstances under which these features may be used, and/or how to activate and find them. We also have some minor editorial suggestions. First, we wanted to point out that “co-authorship” networks is far more common in the literature than “co-publication” networks, so the authors may wish to switch to this term if desired. Second, in the third paragraph of the “Methods and Implementation” section the authors point out that “Because InCites networks contain institutional affiliations for all the authors of a given publication, they have richer summaries.” It may also be worth pointing out here that Scopus does this as well. Third, the sixth paragraph of the “Database evaluation and implementation” section contains a broken link ( http://baderlab.org/Software/SocialNetworkApp#PubMed ). We applaud the authors for making this app available for use within a freely available tool that has an active user base and community of users, and are hopeful that the authors will continue with active development of this tool, so that they may be responsive to user suggestions that may further improve the user experience and integration into workflows. Competing Interests No competing interests were disclosed. We confirm that we have read this submission and believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however we have significant reservations, as outlined above. reply Respond to this report Responses (1) Author Response 08 Oct 2015 Victor Kofia, The Donnelly Centre, University of Toronto, Toronto, M5S 1A8, Canada In the version of the Social Network that was current as of the time of this review, one of us (M.B.) attempted a query containing more than 1,000 characters and it was successful. In any case we would like to request clarification, as it appears that the current version of the system may be capable of longer queries, possibly by doing an HTTP Post request. Thanks for pointing this out. We have now modified the app to use POST for all queries, which will be part of the next release. On a related note, later in the sixth paragraph of the “Database evaluation and implementation” section, the authors state that “There is also a limit on the amount of data that can be retrieved at one time from eUtils. NCBI recommends that no more than 500 publications be retrieved from a single eUtils query”. The citation given is http://www.ncbi.nlm.nih.gov/books/NBK25498/ . However, this citation does not directly support this assertion. Our apologies for the wrong citation. In “Building Customized Data Pipelines Using The Entrez Programming Utilities” ( http://www.ncbi.nlm.nih.gov/books/NBK1058/ ) under the “Handling Large Datasets” subheading, it is stated that large lists should be split into smaller batches of around 500 records. We have updated the manuscript to reflect this change. In the fourth paragraph of the “Database evaluation and implementation” section the authors mention that “Scopus and Web of Science APIs require paid subscriptions”. It is our understanding that Web of Science has an API that is free to subscribers, in addition to a paid API with more data fields. We would like clarification on whether the authors were referring to the API that is free to subscribers. We were referring to both APIs. Since users have to be subscribed to Web of Science to access the ‘free’ API we classified it as ‘requiring a paid subscription’. We have clarified this point in the revision. In the second paragraph of the “Results and discussion” section the authors state, “We created the co-publication network by entering the researcher’s name (last name first initial, as expected by PubMed) … and clicking on the search button”. Due to the problem of ambiguous names in PubMed, it should be noted that this approach, without an attempt at name disambiguation, may result in many false drops, leading to invalid networks. We agree with the reviewer. Name disambiguation is definitely a problem when constructing co-authorship networks in this way. And it is a problem that affects all databases. We have updated the text to reflect this as it is something that all readers should be aware of. Until such time that databases become cleaner or reliable automatic name disambiguation services become available, we recommend that users manually clean their data to resolve errors and name ambiguities before relying on co-authorship network results to support important decisions. In the third paragraph of the “Methods and implementation” section the authors mention that the user panel includes a co-publication network summary panel. Later in this paragraph they mention “charts that summarize the total number of publications and citations by location can be viewed by clicking on links in the panel that navigate to summary charts created with the Google Chart API.” We have thus far been unable to locate the network summary panel or the links to the charts, so further detail would be helpful here to describe the circumstances under which these features may be used, and/or how to activate and find them. The network summary panel is located at the bottom of the user panel. Instead of a figure that only shows the top half of the panel we have included a new figure that contains the entire panel as this will enable readers to view the sections we are referring to. If no network summary panel exists in your setup and the problem persists then it may be a bug, in which case we would appreciate it being filed as a bug report on GitHub (https://github.com/BaderLab/SocialNetworkApp/issues) or emailed to us so we can fix it. Also note that even with the network summary panel being visible, links to the charts will only appear after an InCites network has been created. No charts are available for Scopus and PubMed networks at the moment. So please verify that you are using an InCites document to build the network. An example InCites document is provided in the user guide: http://baderlab.org/Software/SocialNetworkApp. We have made this clearer in the text. We also have some minor editorial suggestions. First, we wanted to point out that “co-authorship” networks is far more common in the literature than “co-publication” networks, so the authors may wish to switch to this term if desired. Thank you for pointing this out. We have switched to using the more common “co-authorship” term throughout the manuscript. Second, in the third paragraph of the “Methods and Implementation” section the authors point out that “Because InCites networks contain institutional affiliations for all the authors of a given publication, they have richer summaries.” It may also be worth pointing out here that Scopus does this as well. It is indeed true that Scopus provides institutional affiliations. The default setting for exporting files from Scopus is “Citation Information Only” which does not include the institutional affiliations of the co-authors. We have extended the functionality so that the app is capable of parsing Scopus reports that contain additional information (like institutional affiliations). We have made a note of this in the online manual. Third, the sixth paragraph of the “Database evaluation and implementation” section contains a broken link ( http://baderlab.org/Software/SocialNetworkApp#PubMed ). Thanks for noticing this. We have updated the manuscript to include the correct link: http://baderlab.org/UserguideSocialNetworkApp#PubMed We applaud the authors for making this app available for use within a freely available tool that has an active user base and community of users, and are hopeful that the authors will continue with active development of this tool, so that they may be responsive to user suggestions that may further improve the user experience and integration into workflows. Thank you for taking the time to review our app. View more View less Competing Interests No competing interests were disclosed. reply Respond Report a concern Bales M and Wheeler T. Peer Review Report For: Social Network: a Cytoscape app for visualizing co-authorship networks [version 3; peer review: 1 approved, 2 approved with reservations] . F1000Research 2015, 4 :481 ( https://doi.org/10.5256/f1000research.7315.r9859) 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/4-481/v1#referee-response-9859 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 = "Social Network: a Cytoscape app for visualizing...".replace("'", ''); var linkedInUrl = "http://www.linkedin.com/shareArticle?url=https://f1000research.com/articles/4-481/v3" + "&title=" + encodeURIComponent(lTitle) + "&summary=" + encodeURIComponent('Read the article by '); var deliciousUrl = "https://del.icio.us/post?url=https://f1000research.com/articles/4-481/v3&title=" + encodeURIComponent(lTitle); var redditUrl = "http://reddit.com/submit?url=https://f1000research.com/articles/4-481/v3" + "&title=" + encodeURIComponent(lTitle); linkedInUrl += encodeURIComponent('Kofia V et al.'); 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/4-481/v3/mendeley", icon:"/img/icon/at_mendeley.svg" }, { name: "Reddit", url: redditUrl, icon:"/img/icon/at_reddit.svg" }, ] }; var addthis_share = { url: "https://f1000research.com/articles/4-481", templates : { twitter : "Social Network: a Cytoscape app for visualizing co-authorship.... Kofia V et al., published by " + "@F1000Research" + ", https://f1000research.com/articles/4-481/v3" } }; if (typeof(addthis) != "undefined"){ addthis.addEventListener('addthis.ready', checkCount); addthis.addEventListener('addthis.menu.share', checkCount); } $(".f1r-shares-twitter").attr("href", "https://twitter.com/intent/tweet?text=" + addthis_share.templates.twitter); $(".f1r-shares-facebook").attr("href", "https://www.facebook.com/sharer/sharer.php?u=" + addthis_share.url); $(".f1r-shares-linkedin").attr("href", addthis_config.services_custom[0].url); $(".f1r-shares-reddit").attr("href", addthis_config.services_custom[2].url); $(".f1r-shares-mendelay").attr("href", addthis_config.services_custom[1].url); function checkCount(){ setTimeout(function(){ $(".addthis_button_expanded").each(function(){ var count = $(this).text(); if (count !== "" && count != "0") $(this).removeClass("is-hidden"); else $(this).addClass("is-hidden"); }); }, 1000); } close How to cite this report {{reportCitation}} Cancel Copy Citation Details $(function(){R.ui.buttonDropdowns('.dropdown-for-downloads');}); $(function(){R.ui.toolbarDropdowns('.toolbar-dropdown-for-downloads');}); $.get("/articles/acj/6804/8161") new F1000.Clipboard(); new F1000.ThesaurusTermsDisplay("articles", "article", "8161"); $(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 = { "11200": 0, "11201": 0, "9859": 53, "9860": 0, "9861": 0, "11782": 31, "9862": 0, "11783": 0, "9863": 0, "9864": 0, "9865": 0, "9866": 47, "12299": 0, "9867": 0, "12300": 0, "12301": 0, "12302": 0, "12303": 0, "12522": 29, "10730": 40, "10731": 0, "12028": 0, "12029": 0, "12030": 0, "12031": 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 = "55f39e1b-7607-40a5-8a53-3cdb85c0c2c7"; 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(",","/")); } }); });