Feeds

Stob latest: IEEE flags dodgy paper

Cleaning up after peer review

  • alert
  • submit to reddit

Top 5 reasons to deploy VMware with Tegile

After a series of emails with IEEE board member and the institute's director of products and services, Evan Butterworth, we received this statement:

First, after a review of IEEE publication policies and procedures, we've determined that it would be appropriate to flag the article in our database. We are currently addressing that, and the flag should appear the next time we do a download of articles into the database - some time within the next 5 to 10 days. The flag will clearly alert researchers that the content of the article may not be reliable. I've appended the full text of the flag below my signature.

Second, it is our practice to regularly review and revise our policy manual, and we intend to consider what we have learned from this situation as part of that process.

Again, thank you for your diligence in bringing this situation more broadly to our attention. The IEEE is committed to ensuring the integrity of our scholarly publishing process, and the soundness of our research database.

And here's the new text appended to the Madanmohan and De' paper:

Notice of Violation of IEEE Publication Principles

“Open Source Reuse in Commercial Firms” by T.R. Madanmohan and Rahul De in IEEE Software, Vol. 21, Issue 6, November/December 2004, pp. 62-69

After careful and considered review of the content and authorship of this paper by a duly constituted expert committee, this paper has been found to be in violation of IEEE's Publication Principles.

This paper contains portions of original text from the sources cited below. Text from Paper 1) was reused without attribution. Text from Paper 2) was reused with attribution but without being clearly delineated from the above authors’ own text.

1) "Open-Source CMS: Prohibitively Fractured?" by Tony Byrne in CMS Watch, http://www.cmswatch.com/Feature/89-Open-Src 14 May 2003, pp 94-99

2) “The Amos Project: An Approach to Reusing Open Source Code” by Manuel Carro, Germán Puebla and Carlo Daffara in Presente y futuro de la ingeniería del software libre URJC, Madrid, May 21, 2003

As Verity noted, the paper continues to be widely cited.

Stay tuned - there's much more to follow. ®

Providing a secure and efficient Helpdesk

More from The Register

next story
Google+ goes TITSUP. But WHO knew? How long? Anyone ... Hello ...
Wobbly Gmail, Contacts, Calendar on the other hand ...
Preview redux: Microsoft ships new Windows 10 build with 7,000 changes
Latest bleeding-edge bits borrow Action Center from Windows Phone
Microsoft promises Windows 10 will mean two-factor auth for all
Sneak peek at security features Redmond's baking into new OS
UNIX greybeards threaten Debian fork over systemd plan
'Veteran Unix Admins' fear desktop emphasis is betraying open source
Google opens Inbox – email for people too stupid to use email
Print this article out and give it to someone techy if you get stuck
DEATH by PowerPoint: Microsoft warns of 0-day attack hidden in slides
Might put out patch in update, might chuck it out sooner
Redmond top man Satya Nadella: 'Microsoft LOVES Linux'
Open-source 'love' fairly runneth over at cloud event
prev story

Whitepapers

Cloud and hybrid-cloud data protection for VMware
Learn how quick and easy it is to configure backups and perform restores for VMware environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
Three 1TB solid state scorchers up for grabs
Big SSDs can be expensive but think big and think free because you could be the lucky winner of one of three 1TB Samsung SSD 840 EVO drives that we’re giving away worth over £300 apiece.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.