Showing source for Querki Use Cases
ProWiki
|
RecentChanges
|
Preferences
<b>To be filled in</b> -- this page should contain a variety of use cases for the Querki model. Talk about LARP development; bug tracking; spec writing; what else? Come up with some examples that aren't just drawn from LARP and software development. See siderea's comment at http://jducoeur.livejournal.com/237235.html?thread=1645235 for a few rough examples on the management side. <b>Public form-filling:</b> This use case is the casting questionnaire for the LARP; or, only slightly different, the Rolls Ethereal. Allow members of the public to fill in a predefined form of a specific type, which then becomes queryable in the LARP. For the casting questionnaire case, I want to be able to predefine the expected entries with their email addresses, and automatically send email to everyone in that list with passwords (maybe embedded in the one-shot URLs) taking them to their own entries. For the Rolls, I want anyone to be able to create password-protected entries, but require some sort of admin approval before making those pages available to public queries (so that wikispam is useless for this case). <b>Story Management System:</b> As soon as possible, the system should be used to develop and manage itself. <b>Bug Tracking System:</b> Same as the above -- this is a system where eating its own dogfood makes lots of sense. <b>Cookbook:</b> An example that's a great fit, and less meta. A cookbook is just right: a collection of pages that are partly data fields, and partly open text. Note that this introduces an interesting new requirement: for each ingredient, we really want the "ingredient" and "quantity" to be separate conceptually, so that we can query on ingredients. That implies that a property potentially needs to be a parameterizable data structure unto itself, not just a string or link. Fun! Back to [[Querki Design Notes]].