ORCID – Open Researcher and Contributor ID

Today I participated in ORCID meeting, where the current progress of the initiative and further steps have been discussed. ORCID represents a community effort to establish an open, independent registry that is adopted and embraced as the industry’s de facto standard. Their mission is to resolve the systemic name ambiguity, by means of assigning unique identifiers linkable to an individual’s research output, to enhance the scientific discovery process and improve the efficiency of funding and collaboration (from http://orcid.org/aboutus.php).

ORCID seems to be very related to LiquidPub, because they deal with research profiles, i.e. info about name, affiliation, role at primary institution, homepage, publication record, areas of expertise, collaborators, projects, awards, etc. of a researcher. Some features (e.g. selecting publications of a researcher for the individual’s publication record) sounded extremely familiar, since they were also planned in LiquidPub, and in particular, in our collaboration with ICST. Also, the IDs of researchers used for micro-credit attribution (not only for recognizing authorship in a paper, but also for a Wikipedia entry, or for a blogpost) can be a great help for defining novel metrics in ResEval tool, developed by LiquidPub.

A funny thing is that the discussion about board membership (whether it should be individual or institutional) was the longest, while there were almost no comments on technical issues (real work?:)).

The first prototype is going to be ready for this summer, and we might test the public API in LiquidPub.
If you are looking for more info – it is on ORCID private wiki (you should request the membership at http://orcid.org/memberorg-form/index.php). Alternatively, this paper provides a nice high-level overview: Credit where credit is due .


Some thoughts about theoretical (and not only) computer science

In his blog post, Mark C. Wilson very nicely summarizes some concerns about (theoretical, but applied also to general) computer science:

– why people tend to produce too many publications with too few results?

– very weak link between theory and practice

– not much linkage between different areas of CS research

…and so on.

A note on the publication culture in computing research

In his article on Revisiting the publication culture in computing research Moshe Vardi, further elaborating on “why conferences in computer science are even more important than journals?” tries to answer the question “Why computer science journals are slow in reviewing” and concludes that it is because CS researchers who run those journals are slow. Why they are slow? Because they do not take editor’s job as seriously as conference chair job. So, taking into account the suggestion from the readers (in order to increase importance of the journals, they must be faster in reviewing), we face a typical chicken-or-egg problem: journals are slow, therefore less important, and they are slow because conferences are more important, which are more important because the journals are slow. Are you following?;)