Chris-201208
From Stadm
Jump to navigationJump to searchContents
Daily Entries
Week of 2012-08-25 to 2012-08-31
2012-08-31 Fri -- 3 hrs
- eri:3h:Worked at resolving everything related to the pile of UPS's in 6706. Looked into and researched APC's trade-ups program. Also looked at Eaton ups' and compared them with APC's
- UPS trade in programs:
- UPS' in 6706:
- smart-ups 2200rm (x2) - RBC12
- smart-ups 1000 (x2) - RBC6
- smart-ups 1000rmnet (x2) - RBC6
- smart-ups 1000rm - RBC23
- back-ups 500 - RBC2
- back-ups pro 280 (x2) - RBC2
- smart-ups 750 - RBC34
2012-08-30 Thu -- 0 hrs
2012-08-29 Wed -- 3 hrs
- eri:30m:Tested voltage on several batteries and started to see which UPS's are usable in 6706
- cein:2h:Finally figured out how to fix the multiple group leader message problem. Also added the title of each research theme to the top of each tab on the research page
- I did this by changing the contextual filter to filter by taxonomy term (with depth), rather than just taxonomy term. I then passed the view the tid of the child term which then also displays content with the parent terms
2012-08-28 Tue -- 3.5 hrs
- eri:2h:Took hard drive out of CRUSH, unknown box, and mac mini. Also took magnets from several fiber channel drives
- cein:1.5h:Worked on making the people and contact pages look more similar to the original cein site. Still trying to work out the kinks with the group leader messages being displayed multiple times
2012-08-27 Mon -- 2 hrs
- cein:2h:Added new Event content type and a couple entries to test out the calendar module with the site in an attempt to recreate what Zack showed me.
2012-08-26 Sun -- 0 hrs
2012-08-25 Sat -- 0 hrs
Week of 2012-08-18 to 2012-08-24
2012-08-24 Fri -- 3 hrs
- eri:1h:Zack showed me what he has done with the calendar module on www-dev.eri.ucsb.edu
- cein:2h:Have been trying to insert the group leader message above the entries under each Theme tab on the research page.
- I tried creating a new view with just the group leader message and inserting it as a header into the view that was already there. It almost worked except for when there were multiple group leaders in one Theme tab even though they aren't all group leaders. This would cause the view to display several group leader messages. Trying to work around this
2012-08-23 Thu -- 0 hrs
2012-08-22 Wed -- 3 hrs
- eri:1h:Tied up and organized cables
- cein:2h:Looked at the site trying to figure out how to use one view to display the blocks on the sides of the pages (could be possible to use url as contextual filter)
2012-08-21 Tue -- 0 hrs
2012-08-20 Mon -- 2.5 hrs
- eri:1h:Read Zack's daily log to see what's happened while I was gone
- eri:1.5h:Cleaned other desk in 6706 to make room for myself, moved some of the stuff into the hallway, and set up Mariachi in the new space (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