Meta Triage of Systems

From FreekiWiki
Revision as of 16:53, 3 June 2008 by Rfs (talk | contribs)
Jump to navigation Jump to search

<graphvizr>

 digraph BUILDPATH {
  node [fontname="Helvetica", fontsize="11"]
  edge [fontname="Helvetica"]
  start         [label="START HERE", shape="box"]
  missingmobo [label="Missing the\nMotherboard?"]
  damaged     [label="Missing sides?\nor Other major damage?"]
  atkeyboard  [label="AT Keyboard\nconnector?"]
  incoming    [label="Leave on \nINCOMING\npile", shape="box", style="bold"]
  reject      [label="Label and put on\nREJECT\npile", shape="box", style="bold"]
  start       -> damaged
  damaged     -> reject [taillabel="YES"]
  damaged     -> missingmobo [taillabel="NO"]
  missingmobo -> reject [taillabel="YES"]
  missingmobo -> atkeyboard [taillabel="NO"]
  atkeyboard  -> reject [taillabel="YES"]
  atkeyboard  -> incoming [taillabel="NO"]
 }

</graphvizr> The idea of this chart is to safely bypass the ever-bottlenecked INCOMING pile in system evaluation. If you don't know how to identify the terms on this page, please learn to before attempting this job. In general this job should be done by trained system evaluation instructors and staff.

Meta-triage should take into account the current needs of both System Eval 1 and System Eval 2. For example, if there are a lot of systems in Eval 1, and not so many in 2, moving incoming system directly into Eval 1 could be avoided.

Category: