FAIRSpectra - Enabling the FAIRification of Analytical Science
User Required? On the Value of User Research in the Digital Humanities
1. User Required?
On the Value of User Research in the
Digital Humanities
Max Kemman
University of Luxembourg
@MaxKemman
Martijn Kleppe
Erasmus University Rotterdam
@MartijnKleppe
2. The problem with tools
• Digital Humanities ♥ tools
• But tools not always used
• Two approaches
• Just publish the data
• User-centred design
3. User-Centred Design
What is the added value of user research for developing tools
aimed at digital research methods?
Two problems:
• Does the user know what she wants/needs?
People don’t know what they want
until you show it to them
4. User-Centred Design
What is the added value of user research for developing tools
aimed at digital research methods?
Two problems:
• Does the user know what she wants/needs?
First Rule of Usability? Don't Listen to
Users
5. User-Centred Design
What is the added value of user research for developing tools
aimed at digital research methods?
Two problems:
• Does the user know what she wants/needs?
The technology will come first, the
products second, and then the needs
will slowly appear
6. User-Centred Design
What is the added value of user research for developing tools
aimed at digital research methods?
Two problems:
• Does the user know what she wants/needs?
• Can user requirements be generalized?
basic functions common to scholarly
activity across disciplines, over time,
and independent of theoretical
orientation
7. User-Centred Design
What is the added value of user research for developing tools
aimed at digital research methods?
Two problems:
• Does the user know what she wants/needs?
• Can user requirements be generalized?
This model of what researchers do maps
quite naturally onto a model of an
infrastructure that supports these research
processes
8. User-Centred Design
What is the added value of user research for developing tools
aimed at digital research methods?
Two problems:
• Does the user know what she wants/needs?
• Can user requirements be generalized?
A 'one size fits all' approach would be a
disastrous underestimation of the specific
needs of humanities research
9. User-Centred Design
What is the added value of user research for developing tools
aimed at digital research methods?
Two problems:
• Does the user know what she wants/needs?
• Can user requirements be generalized?
We will review user research of two case studies we
conducted
10. Case studies
PoliMedia
• Automatically creating links between debates
of the Dutch parliament to media items, made
available in a search user interface in which
debates of the Dutch parliament can be
explored
• www.polimedia.nl
14. Case studies
Oral History Today
• A search user interface similar to Google but
including advanced filter options, in which oral
history interviews and collections can be
searched and explored to discover topics
across a multitude of collections
• zoeken.verteldverleden.org
21. Results – PoliMedia
39 user requirements
• 21 deemed within-scope
• 18 deemed out-of-scope
• 27 unique user requirements
Most common (3/5):
• Media output from before the debate
• Names of people involved
• Location in the newspaper
22. Results – PoliMedia
Requirements with impact
• Function of actors (e.g. minister,
member of parliament, but also show host,
interviewer, etc.) (1)
• Party of actors (e.g. VVD, PvdA, but also
Greenpeace or other lobby groups) (2)
• Media output about subject before
debate (3)
23. Results – Oral History Today
75 user requirements
• 33 deemed within-scope
• 42 deemed out-of-scope
• 34 unique user requirements
• Most common (10/15):
• Filter for time period
24. Results – Oral History Today
Requirements with impact
• Description of project (within
which collection was created) and
how collection came to be
• Organization behind collection
(management/creation)
• Distinguishing search filters
between content-related to general
25. Discussion
• Scholars are aware of what they want
• But also limitations:
• Generalizing is difficult
Requirements Project goals
Current practices
26. Discussion
• Within-scope requirements lead to usable tools
• Out-of-scope requirements give hints of wider
research workflow & compatibility
• Tool takes place in a wider research workflow
27. Developing
For – With – By
Humanities
• User research!
• Support workflow demanding multiple tools
• Separate tool and data
Conclusion
X
“tool” mentions almost 100 times in DHBenelux proceedings (not counting our own abstract)
http://www.slideshare.net/cgueret/stop-making-tools-nobody-likes-them-anyway
User-Centred design may sound like a silver bullet, if we develop what the users want, they will use the tool more. But it is debatable whether this is the case. So we have a somewhat boring research question, that actually leads to a really interesting debate
http://www.redmondpie.com/a-trip-through-the-life-of-steve-jobs-photos/
User-Centred design may sound like a silver bullet, if we develop what the users want, they will use the tool more. But it is debatable whether this is the case. So we have a somewhat boring research question, that actually leads to a really interesting debate
http://chrisgrosse.com/images/projects/jacob_lg.jpg
User-Centred design may sound like a silver bullet, if we develop what the users want, they will use the tool more. But it is debatable whether this is the case. So we have a somewhat boring research question, that actually leads to a really interesting debate
http://www.experientia.com/blog/donald-normans-new-book-on-sociable-design/
User-Centred design may sound like a silver bullet, if we develop what the users want, they will use the tool more. But it is debatable whether this is the case. So we have a somewhat boring research question, that actually leads to a really interesting debate
http://people.brandeis.edu/~unsworth/
User-Centred design may sound like a silver bullet, if we develop what the users want, they will use the tool more. But it is debatable whether this is the case. So we have a somewhat boring research question, that actually leads to a really interesting debate
Blanke: https://www.youtube.com/watch?v=Df7BLU0oNkk
User-Centred design may sound like a silver bullet, if we develop what the users want, they will use the tool more. But it is debatable whether this is the case. So we have a somewhat boring research question, that actually leads to a really interesting debate
http://www.surfsites.nl/srie13/programma/print/?full=402
User-Centred design may sound like a silver bullet, if we develop what the users want, they will use the tool more. But it is debatable whether this is the case. So we have a somewhat boring research question, that actually leads to a really interesting debate
http://www.surfsites.nl/srie13/programma/print/?full=402
categorizing into within- or out-of-scope
Within-scope
Gaining insight into contextual information
Function of actors, Party of actors, Type of programme, …
Frequency of terms
Mathematical queries, Comparing/sorting search results by frequency of terms, …
Search operators
Boolean operators, Google search operators
Analysis of debates
Length of document per actor, Ability to export non-formatted text, …
Out-of-scope
Linguistic analyses of debates and newspaper articles
Speech functions, Type of speech fragments, Genre, …
Image processing of newspaper pages
Size of headers, Number of columns on a page, Presence and size of photographs, …
Audio-visual processing of television programmes
Length of talk, Presence of music, Use of filming techniques, …
Out-of-scope
Linguistic analyses of debates and newspaper articles
Speech functions, Type of speech fragments, Genre, …
Image processing of newspaper pages
Size of headers, Number of columns on a page, Presence and size of photographs, …
Audio-visual processing of television programmes
Length of talk, Presence of music, Use of filming techniques, …
Within-scope
More instructions and clearer details of functionality and collections
Description of project (within which collection was created) and how collection came to be, Organization behind collection (management/creation),…
More advanced searching with filters
Locations, Collection, Topics, Year Event, Access conditions
Navigation within the search user interface
Navigate from interview to interview collection, Clicking a topic should result in all interviews with the same topic, Links between related interviews
Workspaces
Search trail, Bookmark functionality for interview
Out-of-scope
Features of the search technology
Boolean operators, Search explicitly for broad or narrow terms, Detect synonyms of search terms
Additional metadata on the interviewee , interviewer, interview
Age/Year of birth, Gender, Religion, Community of experience, Social class, Research question underlying interview, Location of interview, Description of interview per 10 minutes, …
Scholars are aware of what they want
But also limitations:
Little overlap between requirements and project goal
Requirements based on current instead of future practices & distrust of potential innovation
Generalizing?
Large number of requirements were unique
All user requirements are available open access via
Kemman, M., Kleppe, M. (2014): User Requirements for Two Digital Humanities Projects: PoliMedia and Oral History Today [dataset]. figshare. http://dx.doi.org/10.6084/m9.figshare.1170077