Difference between revisions of "Meta Triage of Systems"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
missingmobo [label="Missing the\nMotherboard?"] | missingmobo [label="Missing the\nMotherboard?"] | ||
| − | |||
| − | |||
damaged [label="Missing sides?\nor Other major damage?"] | damaged [label="Missing sides?\nor Other major damage?"] | ||
| − | |||
atkeyboard [label="AT Keyboard\nconnector?"] | atkeyboard [label="AT Keyboard\nconnector?"] | ||
| − | + | incoming [label="Leave on \nINCOMING\npile", shape="box", style="bold"] | |
| − | |||
| − | incoming [label=" | ||
legacy [label="Put on \nLEGACY\npile", shape="box", style="bold"] | legacy [label="Put on \nLEGACY\npile", shape="box", style="bold"] | ||
reject [label="Label and put on\nREJECT\npile", shape="box", style="bold"] | reject [label="Label and put on\nREJECT\npile", shape="box", style="bold"] | ||
| Line 25: | Line 20: | ||
missingmobo -> reject [taillabel="YES"] | missingmobo -> reject [taillabel="YES"] | ||
| − | missingmobo -> | + | missingmobo -> atkeyboard [taillabel="NO"] |
| − | + | atkeyboard -> legacy [taillabel="YES"] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | atkeyboard -> | ||
atkeyboard -> incoming [taillabel="NO"] | atkeyboard -> incoming [taillabel="NO"] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
} | } | ||
</graphvizr> | </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. | 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 | + | 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: | Category: | ||
[[Category: Prebuild]] | [[Category: Prebuild]] | ||
Revision as of 16:28, 30 May 2008
<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"] legacy [label="Put on \nLEGACY\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 -> legacy [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: