Scientific Announcements Don’t Get Noticed Where They Should
December 8th, 2011 § Leave a Comment
Wouldn’t it be nice if the event you are trying to promote needed to be posted only once? What if there was a central repository for dissemination of announcements that was accessible and permanently up-to-date? Wouldn’t it be great if your blog or website could show relevant professional announcements without having to enter them?
Unfortunately, people around the world are still trapped in the paper-based office paradigm when wanting to disseminate announcement information. Again and again they post their announcement to different places knowing that it will only reach a partial share of all potentially interested readers. They add data and clog online databases as no centralized repository is available for posting or getting information. Despite the great number of hours of work lost by millions of people trying to post, scientific organizations have been extremely slow to embrace community-shared announcement curation.
We (Rafael Jimenez and I) are promoting the creation of a community of organizations and people to lead iAnn, a centralized collaboration platform that coordinates curation efforts among scientific organizations. iAnn increases access to announcements through its dissemination tools, which have been designed specifically to integrate posts across many different websites with minimal effort. iAnn allows you to post your event, course, piece of news only once to a central repository, which is then disseminated seamlessly to relevant scientific organizations or websites according to keywords, dates or geographical location.
If you think iAnn is of interest to you please contact me (see contact information on the right) or wait for future developments that are about to come in Manuel Corpas’ Blog. Currently we are in a development phase for the project and would like to hear from potential users or scientific organizations if they have any thoughts or suggestions on the matter. Our aim is to change the way anyone posts and finds relevant information about any given professional field. iAnn promises to help many users keep up-to-date with relevant announcements more effortlessly. Perhaps from now on websites will be better able to have most of the events, courses, seminars, news, etc. that users would expect to find in them.
A Warning Sign for Biomedical Databases
May 25th, 2011 § 9 Comments
Users of the highy popular OMIM database (On-Line Mendelian Inheritance in Human) [1] may have noticed that NCBI [2] is not providing further funds to sustain OMIM’s development. One of the reasons for halting the funding may have to do with curation work not deemed worthy of funds. Funding agencies might have thus started a trend to not willing to dedicate funds for curation of database entries.
The flip side of this is the nascent trend to outsource database annotation to the general public. Databases like Rfam [3] or Pfam [4], two popular RNA and protein family databases, have adopted the strategy of outsourcing their annotation to Wikipedia. Realizing that it is impossible to keep up with the literature, an attempt was made by Rfam to seed Wikipedia with database-specific information. They then developed a system to collect Wikipedia text from created entries periodically to repopulate back the corresponding RNA entry. The price they had to pay was losing control on what gets entered into the Wikipedia entry. However, benefits seem to outstrip this loss of control, including ready access to an army of casual annotators and a dramatically increased exposure of the database itself (Wikipedia consistently ranks top of the list for most RNA family searches in Google). This means that their chances of having up-to-date content is increased, as well as better awareness of the resource, justifying future cycles of funding.
Something that started as an experiment in Rfam seems to be spreading to other databases as they begin to assess how to address their annotation bottleneck. It seems that outsourcing annotation of Biomedical databases to Wikipedia is a solution worth considering as curation practices continue evolving to cope with current fund shortages. Generalized lack of funding for research and the establishment of community wiki-style annotation practices may mean that funding agencies may be ever more reluctant to provide funding for database curation. Perhaps this is the time to start rethinking future plans for those of us who care about biological databases and their contents. Is now the time ripe for embracing Wikipedia to the full?
[1] http://www.ncbi.nlm.nih.gov/omim
[2] http://www.ncbi.nlm.nih.gov/
[3] http://rfam.sanger.ac.uk/
[4] http://pfam.sanger.ac.uk/
[5] http://www.wikipedia.org/
Biomedical Community-Wide Annotation Using Wikipedia
June 3rd, 2010 § 9 Comments
The pace of data generation is leaving far behind our ability to convert this data into usable knowledge. Even well funded biomedical databases find it increasingly difficult to keep up to speed. In order to tackle this problem, some databases have opted for increasing automation in the way data is deposited, reducing the time needed for interpreting results. The problem with this approach is that generated knowledge as a result is less accurate than manually annotated entries and of lower quality. Another potential solution has been to engage leading experts, creating a sort of consortium where they give some of their time to curate data entries that match their specialties. Unfortunately, engaging world experts in curating biomedical resources has not had a lot of success, with a few contributing a lot and many hardly ever dedicating any time to curation no matter how much they were fetched.
A new revolutionary idea has come from Alex Bateman‘s group to engage not just the community of experts but the whole of the Internet, using Wikipedia. One of his group’s databases, Rfam, which characterises RNA families, is now providing all of its annotation via Wikipedia. Wikipedia is already the leader reference resource for all kinds of information. It possesses the know-how and capability to mediate the curation of database entries as well as managing to have extremely resounding success in terms of gathering reasonably high quality knowledge.
After having a persuasive discussion with Alex, I decided to give it a try myself and add my very first entry to Wikipedia, which I thought it could potentially help the database I develop outsource its public/non-sensitive data annotation part.
I copied, edited and formatted parts of a non-sensitive entry (a Syndrome description) to Wikipedia. I learnt –contrary to what I expected- that as long as one has an account and no entry exists on the topic, a page can be added on the fly. So I added a page and started editing, copying and pasting.
It took me a bit of time to get used to some of the conventions and formatting tags used by Wikipedia but very early on I had help from Wikipedia ‘agents’. It really surprised me how quickly these agents picked up my entry and immediately made me know the criteria for making sure this Wikipedia entry achieves a high standard.
I learnt about important concepts in the Wikipedia context such as Notability and Conflicts of Interests. Apparently one cannot write about oneself for example, and personal opinions or articles are not accepted. So far this was OK for me although problems came when one of this agents pointed at some copywriting issues: I was trying to copy an entry of a website/database.
Blatant copy of public content from another website is considered a copyright violation unless a correct license is put in place and one ‘owns’ the data. In our case, the Creative Commons License, which is the one we hold, was not OK because although it lets public use of the information, it does not allow alteration. This means that people would not be able to edit my Wikipedia entry.
I must admit I felt intimidated at this point. Despite that, I was extremely impressed with the efficacy with which agents acted as well as how quickly they responded to my queries. I can understand why they have to be so tough so that they prevent abuse.
Overall I feel quite satisfied with what I have learnt in the process and I am extremely eager to keep exploring the use of Wikipedia for database curation. Of course this is just a try and our adopted solution for keeping up with current annotation may be something different in the end. However, it is worth a try.