All Posts

Almost a year ago we announced the launch of the new Re-evaluation program for Scopus content. This program was created as an incentive for journals to maintain their high content quality. When a journal is originally suggested for Scopus, it must undergo a rigorous evaluation and selection process to ensure it meets all the high-quality title selection criteria required for acceptance into Scopus. However, journals must also demonstrate the ability to maintain their quality status year over year.

An additional focus for the first year of the re-evaluation program was to ensure all journals met the same baseline of quality standards. When Scopus launched in 2004, content originally came from different sources with different levels of evaluation.  Over time, evaluation criteria for new titles has evolved to become stricter and standardized.

A few weeks ago, we posted on the importance of A/B testing and how it allows us to make better data-driven decisions about how to improve Scopus. In part two, we will focus on improvements to Scopus search that will start this coming week. This work will enable us to move forward with improvements to the search experience. For example, due to timing differences during processing, citation count values may appear to be different from (e.g. between search results and citation overview). This asynchronicity will be resolved once the changes are complete.

During this time, below are some of the things you may notice:

• Search results: You might observe slight changes in the number of results returned. Or the ordering of results for the same search at different times (but not during a single session) could be different. Two different users at the same institution, or one person using multiple computers such as at home vs. at work, may see differences in search results.
• Alerts and saved

How are changes to Scopus determined, and how does your use of Scopus impact the development process? This post is the first of a two-part series in which we discuss A/B testing and how data analysis is

ScopusABtesting.gif

There are multiple ways the Scopus team works to identify potential product changes, with a focus to bring you the best experience and provide information faster and with deeper insights. From listening to user feedback to investigating new technology and trends, the product team continuously works to both iterate on existing features and functionality and develop new enhancements.

For an A&I database like Scopus, which serves researchers, institutions, and corporations from all over the world with timely information from over 5000 publishers, there is not a single “typical” user. Each individual user has a specific need and an ideal way they would like the product to work.