Gizmo Categories - Revision history

Ali: categorized

2010-07-06T20:57:40Z

categorized

Rfs: /* Gizmo flow and stations at Free Geek */

2008-10-30T15:03:29Z

Gizmo flow and stations at Free Geek

Rfs: /* Gizmo flow and stations at Free Geek */

2008-10-30T15:03:00Z

Gizmo flow and stations at Free Geek

Rfs: /* Guidelines for good categorization */

2008-10-30T00:54:35Z

Guidelines for good categorization

Rfs: /* Guidelines for good categorization */

2008-10-30T00:53:46Z

Guidelines for good categorization

Rfs: /* Suggested target scheme */

2008-10-30T00:52:49Z

Suggested target scheme

Rfs: /* Guidelines for good categorization */

2008-10-30T00:49:44Z

Guidelines for good categorization

Rfs at 00:48, 30 October 2008

2008-10-30T00:48:32Z

Rfs at 00:47, 30 October 2008

2008-10-30T00:47:14Z

Rfs at 00:35, 30 October 2008

2008-10-30T00:35:37Z

← Older revision		Revision as of 20:57, 6 July 2010
Line 93:		Line 93:
	#* Misc		#* Misc
	#* Etc.		#* Etc.
		+
		+	[[Categories:Receiving]]

@@ Line 32: / Line 32: @@
 disbursement [shape=box]
 sales        [shape=box]
 FG           [shape=egg, style=bold]

@@ Line 42: / Line 42: @@
 FG -> recycling
 FG -> disbursement
 FG -> sales
@@ Line 50: / Line 49: @@
 disbursement -> adoption [arrowhead="none", style=dashed]
 disbursement -> build    [arrowhead="none", style=dashed]
+}

@@ Line 66: / Line 66: @@
 * If there is confusion about what a gizmo type means, then it can skew our numbers. For example, if a Macintosh mouse is sold in the store with a gizmo type of Macintosh, then (to the rest of Free Geek( it will appear that a system got sold rather than a "Miscellaneous:Mouse". If it is necessary to associate the Mac mouse with Club Mac, then we need at least two types -- Macintosh-System and Macintosh-Part (or something like that).
-* If the sheer number of gizmo types gets too big, then data entry becomes too difficult and the system invites avoidance.
+* If the sheer number of gizmo types gets too big, then data entry becomes too difficult and the system invites avoidance, and the data becomes unmaintained and useless.
 * It is likely that as time progresses, we'll need to change the scheme. Stuff that used to matter doesn't anymore. Other stuff matters where it didn't before. The scheme should be able to be changed as needed.

@@ Line 58: / Line 58: @@
 == Guidelines for good categorization ==
-The gizmo categorization scheme needs to account for the differences needed in all areas (incoming and outgoing) without overburdening any one area with too much detail.
+* The gizmo categorization scheme needs to account for the differences needed in all areas (incoming and outgoing) without overburdening any one area with too much detail.
-We also need to keep an eye on certain types of gizmos that we expect to change how we do business. For instance, it would be useful to know what the ratio of LCDs to CRTs is and has been over time (in order to predict when we might need to switch the FreekBox spec to include LCDs instead of CRTs) or what our costs for recycling each are. It's also probably wise to watch TV numbers fairly closely.
+* We also need to keep an eye on certain types of gizmos that we expect to change how we do business. For instance, it would be useful to know what the ratio of LCDs to CRTs is and has been over time (in order to predict when we might need to switch the FreekBox spec to include LCDs instead of CRTs) or what our costs for recycling each are. It's also probably wise to watch TV numbers fairly closely.
-A well designed categorization scheme will also tell us enough about where the gizmo likely spent time that we could use donation, sales, disbursement, and recycling numbers to illuminate how much time and money is spent processing each. For instance, it should be obvious to tell that at least most Macintoshes came from receiving through Club Mac and into the store or recycling. Compare this to most PC systems (same track but through Prebuild and Build), or Laptops (same track but through Laptop Build). If the categorization scheme fails this test it should be worked on.
+* A well designed categorization scheme will also tell us enough about where the gizmo likely spent time that we could use donation, sales, disbursement, and recycling numbers to illuminate how much time and money is spent processing each. For instance, it should be obvious to tell that at least most Macintoshes came from receiving through Club Mac and into the store or recycling. Compare this to most PC systems (same track but through Prebuild and Build), or Laptops (same track but through Laptop Build). If the categorization scheme fails this test it should be worked on.
-If there is confusion about what a gizmo type means, then it can skew our numbers. For example, if a Macintosh mouse is sold in the store with a gizmo type of Macintosh, then (to the rest of Free Geek( it will appear that a system got sold rather than a "Miscellaneous:Mouse". If it is necessary to associate the Mac mouse with Club Mac, then we need at least two types -- Macintosh-System and Macintosh-Part (or something like that).
+* If there is confusion about what a gizmo type means, then it can skew our numbers. For example, if a Macintosh mouse is sold in the store with a gizmo type of Macintosh, then (to the rest of Free Geek( it will appear that a system got sold rather than a "Miscellaneous:Mouse". If it is necessary to associate the Mac mouse with Club Mac, then we need at least two types -- Macintosh-System and Macintosh-Part (or something like that).
-If the sheer number of gizmo types gets too big, then data entry becomes too difficult and the system invites avoidance.
+* If the sheer number of gizmo types gets too big, then data entry becomes too difficult and the system invites avoidance.
-It is likely that as time progresses, we'll need to change the scheme. Stuff that used to matter doesn't anymore. Other stuff matters where it didn't before. The scheme should be able to be changed as needed.
+* It is likely that as time progresses, we'll need to change the scheme. Stuff that used to matter doesn't anymore. Other stuff matters where it didn't before. The scheme should be able to be changed as needed.
 == Suggested target scheme ==

← Older revision		Revision as of 00:52, 30 October 2008
Line 71:		Line 71:

	== Suggested target scheme ==		== Suggested target scheme ==
		+	Input needed for this section based on people who work in each area and/or need to analyze the data.
		+
		+	Maybe we should pull laptops and TVs out into their general categories
		+
		+	# System
		+	#* Mac
		+	#* PC
		+	#* Integrated CRT/System
		+	#* Other
		+	# Monitor
		+	#* CRT
		+	#* LCD
		+	# Laptop
		+	# TV
		+	# Printer
		+	# Other
		+	#* Mac part
		+	#* Laptop part
		+	#* Mouse
		+	#* Cable
		+	#* Card
		+	#* Misc
		+	#* Etc.

← Older revision		Revision as of 00:49, 30 October 2008
Line 67:		Line 67:

	If the sheer number of gizmo types gets too big, then data entry becomes too difficult and the system invites avoidance.		If the sheer number of gizmo types gets too big, then data entry becomes too difficult and the system invites avoidance.
		+
		+	It is likely that as time progresses, we'll need to change the scheme. Stuff that used to matter doesn't anymore. Other stuff matters where it didn't before. The scheme should be able to be changed as needed.
		+
		+	== Suggested target scheme ==

@@ Line 1: / Line 1: @@
 There are currently four main categories of gizmos in the database. Here they are with some suggested subtypes to clarify:
@@ Line 18: / Line 19: @@
 (Actually, some of the subtypes above are in slightly different categories in the current scheme.)
 As gizmos come into and leave Free Geek their flow (in or out and to where) needs to be tracked. Each of the major stations below (in the rectangles) has its own needs that apply to the area in which this gizmo flow is tracked.
@@ Line 53: / Line 55: @@
 For instance, the store needs to track gizmos in one way but recycling in another. Take a Macintosh System (without a monitor). When it is received the front desk counts it as a System. When it is recycled it also considered a System. But when it is sold it matters that this system is a Macintosh. THe other stations don't care.
 The gizmo categorization scheme needs to account for the differences needed in all areas (incoming and outgoing) without overburdening any one area with too much detail.

← Older revision		Revision as of 00:47, 30 October 2008
Line 59:		Line 59:

	A well designed categorization scheme will also tell us enough about where the gizmo likely spent time that we could use donation, sales, disbursement, and recycling numbers to illuminate how much time and money is spent processing each. For instance, it should be obvious to tell that at least most Macintoshes came from receiving through Club Mac and into the store or recycling. Compare this to most PC systems (same track but through Prebuild and Build), or Laptops (same track but through Laptop Build). If the categorization scheme fails this test it should be worked on.		A well designed categorization scheme will also tell us enough about where the gizmo likely spent time that we could use donation, sales, disbursement, and recycling numbers to illuminate how much time and money is spent processing each. For instance, it should be obvious to tell that at least most Macintoshes came from receiving through Club Mac and into the store or recycling. Compare this to most PC systems (same track but through Prebuild and Build), or Laptops (same track but through Laptop Build). If the categorization scheme fails this test it should be worked on.
		+
		+	If there is confusion about what a gizmo type means, then it can skew our numbers. For example, if a Macintosh mouse is sold in the store with a gizmo type of Macintosh, then (to the rest of Free Geek( it will appear that a system got sold rather than a "Miscellaneous:Mouse". If it is necessary to associate the Mac mouse with Club Mac, then we need at least two types -- Macintosh-System and Macintosh-Part (or something like that).
		+
		+	If the sheer number of gizmo types gets too big, then data entry becomes too difficult and the system invites avoidance.

@@ Line 15: / Line 15: @@
 #* Cable
 #* Etc.
 <graphviz>
@@ Line 47: / Line 51: @@
+}
 </graphviz>