2020-11-10

Background

Goal:

Replace the previous ABM i.e. Annual Bibliometric Monitoring / Årlig Bibliometrisk Uppföljning at KTH

Summary:

Our previous demo meeting was held 2020-05-26. After summer vacations we have worked on Sprints 17 to 23 (current).

The ABM services at KTH have been operational since the last demo meeting, with some maintenance and updates during autumn, for example involving server upgrades and rotation of certificates.

Agenda

  • Progress - What is new since last meeting?

  • A short demo of the current work

  • Update about Scopus data integration

  • Update about other efforts (other data integration, APIs etc)

  • Your questions and feedback, suggestions for future directions

What is new?

  • During the autumn, we have primarily focused on a proof of concept for author based reporting showing results at divisional level, based on currently employed researcher and their publication outputs.

  • Data integration work has been initiated with regards to using Scopus data from Elsevier in order to complement the WoS data.

Demo

  • Introduction to current ABM for new attendees
  • Background for new author based POC (Proof Of Concept)
  • Demonstration of author based reporting for KTH divisions
    • Examples
      • A few divisions (sv. avdelningar)
      • A few departments (sv. institutioner) versus current ABM
    • Some observations and explanations of differences

Author based selection of publications

  • Organization based = organizational affiliation when publication was written
    • Usually used for reporting etc
    • Publications directly tied to organizational unit
  • Author based = publications made by currently employed researchers at the unit
    • Usually used for prospective analysis, current “brain power”
  • Aim in this case is still reporting for KTH publications
    • Fetch employees from HR system / KTH APIs and collect their publications
    • Can be strongly influenced by staff turnover, and interact with staff groups

Author-based: Divisions

Author-based: Departments

Author-based: Department summary

Author-based: Plan forward

  • Classify which are research “divisions”
  • Evaluate differences between models
    • Trends across time
    • Staff categories and staff turnover
    • Interaction with length of author lists
  • Better understand HR/UG data
  • Can people (and therefore publications) become ‘’lost’’ in administative subunits?

Scopus data integration

  • Web of Science data (Clarivate) used for ABM/Ã…BU

  • Scopus data (Elsevier) has been acquired

    • Better coverage of conference proceedings
    • Comparison of coverage Scopus vs WoS (2012–2019); download here
    • Plans to integrate in existing ABM app as complement to WoS

Scopus coverage gain: publication types

  • Coverage by publication type for all KTH peer-reviewed publications

Scopus coverage gain: KTH departments

  • Distribution of KTH departments by coverage gain for peer-reviewed publications (all publication types)

    \(\scriptstyle \text{coverage gain } = \text{ Scopus coverage } - \text{ WoS coverage}\)

Scopus coverage gain: example

  • Department of Computer Science

Other efforts

Operations and maintenance

  • we have separated operational ABM services from other KTHB Bibliometrics services and have allowed external users without KTH accounts to log in via the use of https://auth0.com

  • we have initiated a migration away from Travis - a continuous integration service provider - to using GitHub Actions.

  • we have upgraded the software stack and server environment (and rotated certificates and API keys)

  • we have continued to work with the KTH Web team on aligning with the KTH style for web applications

Questions and feedback

Questions and Answers

Please provide your input!

  • Questions from the Zoom chat
  • Suggestions and comments
  • Future directions

Thank you for attending!