Archive Project Update:
Goal: Remove outdated audio/video/textbooks/manuals etc. from HCMC Archive by June 2007.
Progress: Shipment #1 (temporarily stored in HCMC workshop)is ready for sending to individual Language Depts.; administrative memo advising Depts. materials are coming is in progress.
Shipment #2: In progress in Archive Room;additional assistance has been requested recently in order to move this project forward and have it completed by June 2007.
Jan. 8/07: Todate-over 72 boxes prepared for shipping out.
Note: hrs. spent in 2006 approximately _________
Yesterday, I suggested that we use blogs to track our CTO. Greg proposed that we should actually use the Minutes Worked field to track CTO. This looked promising till we did some research into it. There are two objections:
- The Minutes Worked field is an unsigned integer, so it can't handle negative amounts. That's probably not a major problem.
- We'd end up with confusing numbers for the Minutes Worked. Imagine this:
- I work 180 minutes on Project X.
- 60 minutes of it is CTO.
- I post 180 minutes in the Project X blog (I have to do this because otherwise the time worked on Project X is incorrect).
- I post 60 minutes in the CTO blog (I have to do this so that there's 60 minutes of CTO for me on that day).
- If you do a stats readout on me for that day, it now looks as though I worked 240 minutes, because the CTO minutes are posted in two blogs.
For those reasons, Stew and I feel that a simpler approach such as that outlined below is better, at least for the moment. We can also extend it to cover vacation time, like this:
- We create a blog called "Vacation/CTO".
- We create two categories in the blog, CTO and Vacation.
- I post my CTO as outlined below (post header: "CTO + 1 hour = 43 hours"; post body: explanation of why I had to do it).
- I post my vacation in the same way (post header: "Jan 5 to 9: vacation; 30-4=26 vacation days remaining".
It will be easy to recover anyone's current status in CTO and vacation, or to look at their history. This is WAY better than the current system, where we keep personal, private records of our CTO and vacation, because it makes us open and accountable, and makes it easy for anyone to see our status and history.
If we don't get any serious objections to this, I'll go ahead and create it at the end of today, and then we can all enter our current status into it before year-end, ready to use the system properly starting in January.