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
helping us improve Scopus.
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.