Who is the typical user of SONAR?

           · ·

An important task of the SONAR project is to conceive a user-friendly interface. We decided to structure this process according to the five elements of J.J. Garrett1. Firstly, define the strategy of your product, and then its scope, its structure, its skeleton and finally its surface.

Defining the typical user of SONAR is part of the element scope (user needs). To this aim, we adopted a method based on personas.

What is a persona?

The persona is a well-known concept in the interaction design community. It was introduced 1999 by Alan Cooper2, who defines it as follows:

We make up pretend users and design for them. We call these pretend users personas and they are the necessary foundation of good interaction design. Personas are not real people, but they represent them throughout the design process. They are hypothetical archetypes of actual users. Although they are imaginary, they are defined with significant rigor and precision. Actually, we don’t so much “make up” our personas as discover them as a byproduct of the investigation process. We do, however, make up their names and personal details.

The 3 main SONAR personas

Each persona is presented below with an image, a name, some minimal context information and the tasks he/she performs on SONAR. Some institutions are mentioned, but only as examples, to make the personas more concrete. The tasks are listed for both services: the shared and the dedicated portals (as described in the Service section).

Population persona
Fabrice
Student (University of Kinshasa)
Shared or dedicated portal
  • access full text of publications for free so that I can keep up to date with scientific news
  • access publication metadata so that I can include references in my own publications
  • search publications using various criteria (author, project, institution, document type, etc.)
Researcher persona
Gordana
Post-doctoral researcher (University of Fribourg - with dedicated SONAR portal)
Shared portal
  • publicly display a list of all my Swiss OA publications so that I can show my scholarly records
  • … plus the same tasks as Fabrice
Dedicated portal
  • publicly display a list of all my publications (OA or not) related to my institution so that I can show my scholarly records
  • upload full-texts of my pre-prints and post-prints so that I comply with the OA policy of my institution
  • enter and edit metadata about my publications so that they are searchable
  • export a list of all my publications (OA or not) related to my institution or to a specific project so that I can reuse the data
  • link my profile to standard identifiers (ORCID) so that my publications’ metadata is more accurate
  • import metadata from other platforms (ORCID, Google Scholar, etc.) so that I don’t have to enter it manually
  • edit my personal profile
  • … plus the same tasks as Fabrice
Librarian persona
Gabriele
Librarian (Università della Svizzera italiana - with dedicated SONAR portal)
Shared portal
  • export metadata of publications according to various criteria (author, project, institution, document type, etc.) so that I can reuse the data (showcase, report, FNS, etc.)
Dedicated portal
  • upload PDF of pre-prints and post-prints (OA or not) of my institution’s researchers so that they comply with the OA policy
  • indicate for each full-text the OA status (incl. embargo periods) so that they are publicly available or not accordingly.
  • enter metadata about publications (typology, rights, access, etc.) so that they are searchable
  • create user accounts for researchers, with specific rights
  • import metadata from other platforms (ORCID, Google Scholar, etc.) so that I don’t have to enter it manually
  • validate full-text inputs of the researchers so that they comply with legal restrictions
  • validate and ev. complete metadata entered by researchers so that it complies with standards
  • export metadata of publications according to various criteria (author, project, institution, document type, …) so that I can reuse the data (showcase, report, etc.)
  • request or harvest publications according to various criteria (author, project, institution, document type, …) so that I can integrate them into other platforms (website, etc.)
  • ensure data integrity, readability and access so that we can access it in the long term

3 other personas, not detailed in this blog post, complete the scope of user needs:

And now what?

This work is still in progress and we are improving iteratively the personas. Based on this, we defined the functional specifications, with various detailed scenarios for each persona. We are currently working on the structure of the portal and conceiving the mockups of the interface.

We are also using this approach for the sister project RERO ILS.

References

Icons made by Freepik from Flaticon, licensed by CC-BY 3.0, modified by SONAR team


  1. GARRETT, Jesse James. The elements of user experience: user-centered design for the web. Berkeley CA : New Riders, 2003. ISBN 978-0-7357-1202-7. [return]
  2. COOPER, Alan. The inmates are running the asylum: why high-tech products drive us crazy and how to restore the sanity. Indianapolis, In : Macmillan, 1999. ISBN 978-0-672-31649-4. [return]