Chris-201208
From Stadm
Contents
Daily Entries
Week of 2012-08-25 to 2012-08-31
Week of 2012-08-18 to 2012-08-24
2012-08-24 Fri -- 0 hrs
2012-08-23 Thu -- 0 hrs
2012-08-22 Wed -- 0 hrs
2012-08-21 Tue -- 0 hrs
2012-08-20 Mon -- 0 hrs
- eri:1h:Read Zack's daily log to see what's happened while I was gone
- eri:1h:Cleaned other desk in 6706 to make room for myself (also met Zack)
2012-08-19 Sun -- 0 hrs
2012-08-18 Sat -- 0 hrs
Week of 2012-08-11 to 2012-08-17
2012-08-17 Fri -- 0 hrs
2012-08-16 Thu -- 0 hrs
2012-08-15 Wed -- 0 hrs
2012-08-14 Tue -- 0 hrs
2012-08-13 Mon -- 0 hrs
2012-08-12 Sun -- 0 hrs
2012-08-11 Sat -- 0 hrs
Week of 2012-08-04 to 2012-08-10
2012-08-10 Fri -- 0 hrs
2012-08-09 Thu -- 0 hrs
2012-08-08 Wed -- 0 hrs
2012-08-07 Tue -- 0 hrs
2012-08-06 Mon -- 0 hrs
2012-08-05 Sun -- 0 hrs
2012-08-04 Sat -- 0 hrs
Week of 2012-08-01 to 2012-08-03
2012-08-03 Fri -- 0 hrs
2012-08-02 Thu -- 0 hrs
2012-08-01 Wed -- 0 hrs
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
