(public).sospep.events ~ view task ~ SCENARIO-005-events

<h1 style="text-align: center;">USE CASE -&nbsp;SCENARIO</h1>
&nbsp;
<ol>
<li>] SCENARIO - events -&nbsp;'taskmaster tyler' uses sospep to 'plan' and to 'document' all aspects of all of 'his projects'</li>
<ol>
<li>] Tyler begins by managing all of "the work" around a single project/plan, this includes ...</li>
<ol>
<li>] everything that someone has to do to complete the project</li>
<ol>
<li>] every task&nbsp;&nbsp;</li>
</ol>
<li>] everything that has been done in relation to the project including</li>
<ol>
<li>] who did it</li>
<li>] how long did it take</li>
<li>] when it was done</li>
</ol></ol>
<li>] Tyler&nbsp;runs a startup company, he keeps all of the tasks related to running his company in&nbsp;a ...</li>
<ol>
<li>] <a href="/view/plans?id=71" target="_blank">calendar named&nbsp;business</a>&nbsp;- Tyler has decided his company will apply to the startup accelorator program, ycombinator. He is adding a new&nbsp;project called "accelorator application ycombinator" to&nbsp;track all of the&nbsp;tasks involved in completing that application. &nbsp;</li>
</ol>
<li>] when tyler opens&nbsp;his 'business'&nbsp;calendar, he has the option to view ...</li>
<ol>
<li>] <a href="/view/taskgroups?id=104" target="_blank">plans business</a>&nbsp;- all of the tasks that he needs to do, in relation to this project</li>
<li>] <a href="/view/taskgroups?id=105" target="_blank">documenting business</a> - an ongoing record of all tasks completed in relation to this project</li>
</ol>
<li>] for each plan that Tyler creates, he has the option to divide that plans&nbsp;tasks into</li>
<ol>
<li>] <a href="/view/tasks?id=441" target="_blank">taskgroups</a> - which are just individual groups of related tasks to a specific job. Sometimes Tyler is lazy and just uses the default taskgroup to contain all of the tasks for a project. For this project he has created a taskgroup named accelorator-application-ycombinator, which contains all of the tasks related to applying to their program. If, Tylers application is successfull he will create another&nbsp;taskgroup called accelorator-interview-ycombinator.</li>
<li>] when viewing a taskgroup, Tyler can work with multiple tasks at the same time, for&nbsp;example - moving, copying or deleting tasks, or&nbsp;changing selected task fields like the status of multiple tasks can be completed as quickly as if working with a single task, Tyler can also&nbsp;see the progress he has made at a glance by looking at the total # of tasks, % completed and estimated total time remaining</li>
</ol>
<li>] each task&nbsp;CAN contain 'many&nbsp;details', but a 'title' is all you need to get started quickly &nbsp;</li>
<ol>
<li>] example task <a href="/view/task?id=4981" target="_blank"># 4981 - research how to apply to ycombinator</a>&nbsp;- is the first step on Tylers application journey.</li>
</ol>
<li>] more 'events' goodness ...</li>
<ol>
<li>] obviously, your tasks can be viewed on a <a href="/view/calendar" target="_blank">calender view</a> as well, it is a 'calendar' after all</li>
<li>] or an <a href="/view/agenda" target="_blank">agenda view</a> - where you can view the tasks at their scheduled date and time, drag and drop them to reschedule them, ...</li>
<li>] distribution/publishing - &nbsp;</li>
<li>] task templates -</li>
<li>] scheduler view -</li>
</ol></ol></ol>
&nbsp;
<hr />
<h1 style="text-align: center;">+ integration</h1>
<ol>
<li>we&nbsp;believe that sospep events is a pretty good, task/project manager on its own accord, but what makes it even better is the integration with the other sospep core apps &nbsp;</li>
<ol>
<li>SUBJECTS - example - when Tyler started 'researching' how to apply, he ended up with a fairly large collection of notes(aka articles)&nbsp;from several different sources. He compiled these articles into <a href="/view/chapters?id=303" target="_blank">a noteBook</a> that&nbsp;he organized into chapters. He can now easily refer back to the results of&nbsp;his research and even share it with co founders or other interested parties.</li>
<li>OBJECTS - example - no real objects (aka inventory ) management&nbsp;related to this project, AND thats OK, you dont have to use the functionality of every sospep app, you can if you need/want or choose to</li>
<li>SYSTEMS - example - Tyler knows getting accepted into ycombinator is tough and may take several application attempts, thats why he is creating a step by step guide (aka a system) to detail the steps he took at each stage of&nbsp;his ycombinator journey. He started with the applicaton process, and began outlining the interview process. If Tyler needs to complete another application for the next batch, he knows exactly what he did to complete the job previously. Tyler's goal is to be able to write the office hours and dinner time @yc procedures guides</li>
<li>PEOPLE - example - Tyler can quickly access any of his&nbsp;existing contacts to share details on this project, he can easily add new contacts related specifically to this project like he did for the <a href="/view/people?id=111" target="_blank">people @ycombinator</a>.</li>
<li>PLACES -&nbsp;example - ] San Francisco ]</li>
</ol></ol><hr />
<h1 style="text-align: center;">&nbsp;+ collaboration</h1>
<ol>
<li>a&nbsp;'sospep' can be used by 1 person OR by&nbsp;many people</li>
<ol>
<li>] for this project, Tyler needed to&nbsp;gather some information from his&nbsp;cofounder Toby, Tyler added Toby as an editor&nbsp;to this project in his sospep. Now when Toby logs into his sospep he sees the option to open Tylers sospep and when he does, he has access to this project in Tylers sospep, where he can view, add and edit records. Of course Toby only sees the single project that Tyler has added him to and NOT all of Tylers projects.</li>
</ol></ol>
&nbsp;
<hr />
<h1 style="text-align: center;">+ privacy + public ity</h1>
<ol>
<li>] all of the information in your sospep is private by default</li>
<ol>
<li>] only you and any people that you choose to add to&nbsp;your sospep&nbsp;will be able to view or access your sospep.</li>
</ol>
<li>] but, sometimes, you want to go public</li>
<ol>
<li>] you can easily publish your information to our public sospep and anyone on the web&nbsp;can view that information.</li>
<li>] Other sospep users can use any public sospep information to quickly and easily build a foundation for their own version of that information, import an existing notebook and use that content as the starting point for your notebook. You can import just the structure of sospep apps or both the structure and content.</li>
<li>] sospep users can also share their data with other sospep users.</li>
</ol></ol>

~ view task ~ TaskGroup] FEATURE-4860 FROM [ Plan] plan-projects IN [ calendars] prj-022-sospep