2020-05-26

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-03-24. Since then we have worked (remotely) on Sprints 12 to 16 (current).

The ABM services at KTH are operational and the “old” ABM has been taken off-line. The team has now made an update (data and UX improvements) and is building capacity for the operational / maintenance phase.

Agenda

  • Progress - What is new since last meeting?

  • A short demo of the ABM app

  • Our questions to you

  • Your feedback and your suggestions and comments to us

  • Future directions

What is new?

  • The “old” ABM / ÅBU has been retired and outreach communications was made about the new “ABM” on the KTH Intranet

  • We have spent time on capacity building for operations phase (KTHB + ITA)

  • Updated data and data quality improvements (-> better WoS coverage for KTH) and preparations for using Scopus data

  • We have also worked on integrating data from KTH APIs and style elements from KTHs graphical style

  • The main focus has been on UX / UI / Layout fixes in the user interface, based on feedback from Demo-3 with a complete list of changes here

Updated content

DiVA data

New screening of probable KTH publications in Web of Science, and update of DiVA-data.

  • Manual controls by DiVA team at library
  • Overall coverage of KTH 72.8% –> 77.6% (at school level 3 - 8% increase)
    (can currently be compared between production and reference servers)
  • Open Access data and associated Altmetric data has also been updated

Scopus addition

  • Data related to KTH-publications will be purchased from Elsevier, with updates the coming years
  • Use in relation to coming RAE 2021
  • To complement WoS-data
  • Will require additional quality control of DiVA data
    (from now towards summer)

New components integrated in ABM

NB: These new R packages (kthapi and ktheme) can be used for data integrations and KTH styling also in a wider context (not ABM-specific) by researchers at KTH.

Data integrations

  • Development and integration of kthapi R package and integration of data (for example mapping DiVA -> KTH Directory/Profile APIs -> Altmetric data)

KTH styling

  • Development and integration of ktheme R package for thematic styling of visuals using KTH style

UX improvements

A Trello board was used to capture feedback from the Demo-3-meeting in the area of UX improvements

Live demo

Demo of Dashboard / Shiny App

Feedback and next steps

Recap from Demo-3

At the Demo-3 meeting we suggested that we would work on adding an about tab, more comprehensive co-publication information and ways for researchers to discover collaboration networks.

The feedback from Demo-3 instead suggested we should work on UX and data improvements and look into how to add Scopus as a data source.

Next steps for ABM

Going forward, we suggest that we focus on these areas of improvements:

  • Extending the ABM services with more functionality, such as more comprehensive co-publication information
  • Add an app for exploring research collaboration networks
  • More work to improve UX
  • Continue work to integrate Scopus as a data source
  • Continue work to develop a presentation at the division level

Please think about what would be most useful to you in the short run?

Questions and feedback

  • Does the implemented UX improvements in general solve your reported issues?
  • Does the in-dashboard notes simplify interpreting indicators?
    Context help as tooltips, understanding of intervals for “Good / Moderate / Poor” etc.
  • Future UX work - should we add more interactivity to the dashboard sections (plots etc)?
    Other presentation issues to highlight?
  • What additional functionality would be most useful?
  • In which specific tasks could this type of data be useful to you?