AI Sauna/Dreaming of workflow for digital humanities
Dreaming of workflow for digital humanities
[edit]Description
[edit]Let's say you have paper documents, lot of paper documents. You have photographed these documents with you phone and now you have lot of images with different orientations. You want to make text searches from these texts and You want to find out what persons are mentioned in these documents. Is your workflow clear to You?
We are trying to build simple, transparent and self-documentative workflow platform for these kind of tasks.
But what is simple workflow? Simple for who? What does "transparent" means in this case? Overall, is this feasible approach?
We are trying but we need help. Join the project and come to discuss and dream!
Project page: $5
The team
[edit]What were the roles of each?
Created by: Ari Häyrinen
Team members:
- Sarianna Silvonen
- Julia Matveeva
- Saga Jacksen
- Ari Häyrinen
All with humanistic background!
Results
[edit]Our method
[edit]How did you work?
Two parts:
Dreaming of workflow
[edit]Target group: Non-techinal persons
Target material: images, archive materials, audio, metadata, objects, texts
UX design principles:
goal: User friendly and intuitive for non-tech
- User path: Guides for beginners – real project examples or templates.
- Language used for non tech users!! No buzzwords or tech jargon.
- Intuitive user interface
- Help for choosing useful tools for My case (chatbot)
- fail early
- Failing early saves time if the method does not seem to work
- easy to experiment
- You have to be able to experiment with different settings and those experiments must be saved
- technical transparency
- user can export information of all tools and setting used under to hood
- User can download the latest result of the nodes
- For example to use in the actual paper or for other future needs
- Protect user for deleting manual edits by accident (manual protectin also possible)
- Trash bin, not hard deletes
Evaluation
[edit]Demo & discussion: Node-based UI
- Node-based UI might be frightening (Blender nodes!)
- But, it's the only way to show history of complex flows
- There must be way to hide nodes
- Users don't need to see the workflow history all the time; it is important to preview the latest versions of the mediatype in question.
- Way to highlight/add notes to nodes
Resources we usedWhat resources did you use? Were they useful?
[edit]https://github.com/OSC-JYU/MessyDesk
Conclusion
[edit]What did you learn?
point of view: How people find the tools and how to make them attractive and not SCARY!
Pre-tool information = information about tools that could help you that you did not know about
We found out what aspects are important to users.
Evaluation of MessyDesk
Node based UI history might work, needs user testing
Needs also other views, like "view of latest output" (needs better name!)
What next
[edit]Do you wish to continue exploring this? What was not covered? What did you get curious about?
Development of MessyDesk continues. Test service available with HAKA-credentials. Contributions welcome. https://www.csc.fi/haka-kayttajatunnistusjarjestelma
Links, images, documentation
[edit]Upload at least one image to Wikimedia Commons for the image of the page banner.
