Hi Everyone,
We have received this email from Elsevier about a problem with Scopus records. They expect it to be resolved by the end of the week.
James.
Dear Librarian,
In the past two weeks, as a part of our initiative of loading pre-1996 articles to enrich Scopus content, a large number of articles from Elsevier journals were loaded erroneously into Scopus with incorrect publication year and incomplete source title information.As a result of this, an incorrect publishing year of 2007 and 2008 has been assigned to these records and only limited source information is available, namely journal title and page numbers. Because of the incomplete information, the mechanism that is used to remove duplicate articles hasn't worked properly either. As a consequence, the records are incorrectly appearing in your search alerts as well.A solution to resolve this issue is already in place and we expect the records with the incorrect information to be removed from Scopus by the end of next week. We apologise for the inconvenience caused.
Regards,
The Scopus Team
Subscribe to:
Post Comments (Atom)
2 comments:
Hi Again,
We've received the following update about the Scopus record problem.
James.
At the end of January, we informed you about a situation with recently loaded Scopus records. A large number of articles from Elsevier journals were erroneously loaded into Scopus with incorrect publication year and incomplete source title information. Click here to read the original message from January 29, 2008.
According to our initial estimate this situation should have been resolved by the end of last week, but despite our best efforts, not all erroneous records have been removed yet. We are confident that this will be finalised by February 20th at the latest.
To make sure all Scopus users are aware of this situation, a message has been added to www.scopus.com (in the grey bar at the top) which we will update when the situation is resolved.
Hi All,
I received an email while I was away letting us know that this Scopus problem has been resolved.
Thanks,
James.
Post a Comment