Tip: Getting data into Impactstory but not your ORCID profile

I use Impactstory to track altmetrics for my publications. I believe they did the right thing by not asking me to maintain yet another online profile and instead building upon existing infrastructure. I also use figshare to publish open datasets and wanted to get Impactstory to track these too.

As is often the case, configuring the complex software infrastructure to do what I wanted was nontrivial. Because Impactstory does not maintain a separate user profile, the only way to get data into Impactstory is to add it to your ORCID profile. This took me much longer to figure out than it should have due to misleading, outdated documentation. In fact, I would not have succeeded without the help from Martin Fenner, who taught me about the missing piece of the puzzle, which is DataCite. Once you know what to do, it is reasonably simple: from your ORCID profile, you choose to add and link works from DataCite, where a simple search should find all your datasets in figshare. Afterwards, you have to change the privacy settings for them in your ORCID profile, and they will show up in Impactstory.

This still left me with one challenge, though. Uploading a dataset on figshare can result in numerous DOIs, since both the dataset per se and the individual files are assigned DOIs, each with and without a version number in the DOI. Since I cannot control which DOIs people cite, I must associate all of them with my ORCID to get accurate tracking in Impactstory. However, doing so will pollute the list of works on my public ORCID profile with hundreds of partially redundant DOIs of data files. This is problematic because my ORCID profile also serves as an online curriculum vitae, with the list of works being the publication list.

It turns out that there is a small inaccuracy in the Impactstory documentation: when they write that you must change the privacy setting to “public”, they mean “public” or “trusted parties”. Therein lies the solution to my problem: I set privacy to “public” for the works that I want shown on my ORCID profile and “trusted parties” for the works that I only want tracked in Impactstory. That allows me to get all the data into Impactstory via ORCID but at the same time have a clean, non-redundant publication list on my ORCID profile.

Update: I fear the trick described in the last paragraph does not work afterall. Since writing this blog post, works with privacy set to “trusted parties” have disappeared from my Impactstory profile. We really need a solution to this. For now I prioritize having a clean, non-redundant publication list on my ORCID profile over having accurate statistics on Impactstory.

Announcement: NetBioSIG call for abstracts

Two days before the main ISMB 2016 conference in Florida, the Network Biology Special Interests Group (NetBioSIG) meeting will take place. It is a great opportunity to meet up with experts in the field, so I hope to see you there. This years NetBioSIG will have four keynotes given by Olga Troyanskaya, Franca Fraternali, Nataša Pržulj, and yours sincerely.

There is of course also a chance for you to present your own work. However, please note that the abstract submission deadline is Friday, April 29. Please see the NetBioSIG website for more details.

Job: Postdoc in computational analysis of animal disease models

In collaboration with Jan Gorodkin at the Center for non-coding RNA in Technology and Health at University of Copenhagen, I will be starting up a project on cross-species network and pathway analysis of animal disease models. We have secured funding for the project and are now searching for the right person to fill a postdoc position.

The application deadline is February 27, 2016. For further details, including how to apply, please refer to the official job announcement.

Resource: Cytoscape App for STRING

The STRING database of known and predicted protein–protein interactions is a heavily used resource by bioinformaticians and non-bioinformaticians alike. The former generally use STRING via its web interface, whereas the latter typically download the complete network and analyze it locally. However, we lacked a good way for non-bioinformaticians to work with networks that are just too large for the web interface. A typical example of this would be users, who wish to visualize the results of a proteomics or transcriptomics study as a STRING network.

To address this, I have worked with John “Scooter” Morris to develop a new Cytoscape app for STRING. The app allows you to quickly retrieve much larger networks than is possible via the web interface and gives you the powerful layout and analysis features of Cytoscape. At the same time, it retains the “glass ball” look that many people associate with a STRING network (shown here with a small example network):

cytoscape1

When retrieving network, the app also includes node attributes from the COMPARTMENTS and TISSUES databases. This allows users to easily, for example, color the nodes based on the confidence with which each protein is localized to a certain cellular compartment or expressed in a certain tissue. The app also includes node attributes for drug targets classification of human proteins, which are obtained from the Pharos web resource. Finally, since it is Cytoscape, you can obviously import your own attributes table.

cytoscape2

Although it is not yet feature complete, version 0.9 of the app is already available from the Cytoscape App Store under the name stringApp. Please note that it requires Cytoscape 3.3 to work.

Tip: Making the “back” button work with AJAX

About a month ago, I received an email from an otherwise happy user of COMPARTMENTS, who wished there was a way to return to the search results after having clicked a protein. I was just about the send her an email explaining how the lack of “back” button functionality was an inherent drawback of using AJAX, when I thought that it would be wise to do a quick Google search first.

The result was a healthy serving of humble pie from Stack Overflow. It turns out that you can make it work fairly easily by using the history.pushState() method to manipulate the browser history. Because my search page already allowed the query to be specified as a URL parameter, one extra line of JavaScript code for the “Search” button was all it took to fix the “back” button behavior.

So there you have it. AJAX is no excuse for the “back” button not working as it should.

Update: The BuzzCloud for 2015

Having just downloaded the new Medline baseline, it is time to update the BuzzCloud and see what has changed since last year:

buzzcloud2015

Comparing the cloud to that of last year, one new notable term is medical proteomics, which I believe is indeed something we will see become reality over the next years. The term precision medicine keeps going strong and has spawned a related term, namely precision oncology. Also related to this topic, wearable electronics receive increasing attention in the biomedical literature.