Who are MONK users?

• an individual in a large university environment, with access to collections of literary texts.
• a librarian-collection curator who is responsible for providing MONK services alongside those collections.
• a user who has his or her own collection of texts and wants to submit them to MONK-processing and is willing to act as collection curator.

For the individual user, MONK should provide tools for text-Analysis on pre-processed collections

• Tools for text-mining with pre-processed texts
  • Supervised learning
  • Unsupervised learning
• Tools for text analysis with pre-processed texts

For the curator, MONK should provide administrative tools, for example

• tools that a systems librarian can use for installing MONK
• tools for producing a formal description of the collection that functions as a configuration file that software can leverage to do pre-processing, populate interfaces, etc. (e.g., the nora chunk file)
• tools for building the MONK index once the curator has created the configuration file

What are some examples of uses?

• Doing work on Austen and Empire, for example by looking at mentions of place, using some named entity recognition in combination with a gazetteer.
• Doing work on British and American sentimentality, using quantitative tools that look for patterns of affect at various levels of the text (vocabulary, sentence structure, structure of the work as a whole).
• Doing work on Gertrude Stein's use of repetition, using tools that expose grammatical patterns with special attention to the concept of variation.

How do these examples become use cases?

• a user writes up the narrative of the process that's envisioned, noting possible objects of interest in the text, ways in which those objects might be identified by the user, identified for the software, made visible or useful by the software, subjected to analysis by the user, etc.