Eddie-201307

Daily Entries

BEGIN PARSING ENTRIES - DO NOT REMOVE THIS LINE

Week of 2013-07-13 to 2013-07-19

2013-07-17 Wed -- 0 hrs

• it:2h: Cygwin USB .bat file scripting

2013-07-16 Tue -- 2.5 hrs

• it:1h:Recycling of Batteries and Haz Waste Room 6716
• it:1.5h:Cygwin on USB and SSHing into mariachi

2013-07-15 Mon -- 3.5 hrs

• it:3.5h:Cygwin Install onto USB

2013-07-14 Sun -- 0 hrs

2013-07-13 Sat -- 0 hrs

Week of 2013-07-06 to 2013-07-12

2013-07-10 Wed -- 2.5 hrs

• it:2.5h:InDesign of Library Display Instructions

2013-07-09 Tue -- 3 hrs

• it:3h:Photoshop and InDesign of Library Display Instructions

2013-07-08 Mon -- 6 hrs

• it:5h:Cable length measurements server room
• it:1h:Kickstarter on oangun

2013-07-07 Sun -- 0 hrs

2013-07-06 Sat -- 0 hrs

Week of 2013-07-01 to 2013-07-05

2013-07-05 Fri -- 0 hrs

2013-07-04 Thu -- 0 hrs -- Independence Day

2013-07-03 Wed -- 2.5 hrs

• it:30m:Server Room installation of annapurna into rack
• it:2h: PHP and Python: csv generation

2013-07-02 Tue -- 3 hrs

• it:3h: PHP parser

2013-07-01 Mon -- 5.5 hrs

• it:5.5h:Python and PHP Scipting of html dump

FINISH PARSING ENTRIES - DO NOT REMOVE THIS LINE

Recharge Examples/Entry Instructions

Recharge Entries fall into 3 broad categories:  
  Direct charges - charges to a PI, Category, Account fund - Done monthly
  Deferred charges - charges that are accumulated for Services (Disk Storage, Backups, Websites, etc) paid quarterly
  Departmental charges - entries that are made to track time taken for various services that are provided by the department.  Possibly used by IT staff to make decisions

Recharge Entry Examples (each entry is expected to follow a list tag entry in the final html (ie: an asterisk in the wiki editor)):
 *NEES:20 min:Backups                         -- basic entry, NEES charged 20 minutes for backups
 *Frew:20:Backups                             -- implied units -- units default to minutes
 *Dozier:1.5h:Backups                         -- units flexible - space between amt and units optional, h is shorthand for hours, m shorthand for minutes
 *Davey/Frew/Dozier:20 min each:Backups       -- create recharge entries for this amt of time for each of the categories
 *Davey/Frew/Dozier:2 hours split:Backups     -- split time equally between each of the categories
 *eri.web:20m:Work on research website

Project examples: - ie: NEES, Snow, Oceancolor, Dragon, CCBER
Account entries can be subcategorized by creating a hierarchy using "."'s to separate fields (ie: eri.space.girvetz)

More detailed Syntax Breakdown (in pseudo BNF) :
 ENTRY = *ACCTSPEC:TIMESPEC:DESCRIPTION                         -- one entry per line
 ACCTSPEC = ACCT[[/ACCT]...]                                    -- the Account/Category/Project/CostCenter to be recharged
 TIMESPEC = AMT [UNIT [LOOP-OP]]                                -- amount of time spent - default is minutes
 ACCT = PI | Project | Account | Category [.SubCategory[...]]   -- PI/Project/Acct/Category: ie: Frew, NEES, Dragon, Infra, conf,...
 AMT = float | integer                                          -- Amount of time spent -- float or int
 UNIT = [hour|hr|h|minute|min|m]                                -- units of time to apply to amount - default is minute -- spaces optional between amt and units
 LOOP-OP = [each|split]                                         -- specialized operators - CATEGORY list is split on "/"s and an entry created for each one when processed.

Non-direct Recharge Categories (and associated SubCategories):
 *admin - efforts for administrative staff

 *lic.[itt, matlab, math, arcgis] --licensing stuff.
 *web.[drupal,wiki,cms,ftp]       -- not sure this will be a top level charge

 *stor.[disk,bk,tape]
 *stor.bk                         -- efforts relating to backups
 *stor.disk                       -- disk server related time
 *stor.tape                       -- tape backups
 
 *it.[net,dev,team,ucsb,stadm,dsr,nsmgmt]
 *it                             -- alone infers ERI business (infra/sysadm/blahblahblah).
 *it.net                         -- efforts relating to departmental networking (cabling)
 *it.dev                         -- software development, scripting, new services...
 *it.team                        -- efforts relating to IT team meetings/discussions... how about powow?
 *it.ucsb                        -- UCSB training/meetings/discussions/committees or campus greater good.
 *it.stadm                       -- efforts relating to any IT student assistants
 *it.dsr                         -- efforts relating to departmental safety representative work

Other Stuff

AVWH: 176