Zack-201207

Daily Entries

BEGIN PARSING ENTRIES - DO NOT REMOVE THIS LINE

Week of 2012-07-14 to 2012-07-20

2012-07-20 Fri -- 0 hrs

• eri:2h:rebuilt calendar, content types, and taxonomy
• eri:1h:repaired resources table and added month selector to filter resources by date
• eri:1h:created wiki guide for calendar located on the bottom of this page

2012-07-18 Wed -- 6 hrs

• eri:2hr:researched contextual filters; vertical alignment of blocks on front eri7a page;
• eri:1hr:researched calendar sorting by taxonomy, enabling color coding;
• eri:3hr:video tutorials on module development; drush tutorial;

2012-07-17 Tue -- 4 hrs

• eri:1.5hr:viewed online tutorials on hook_form_alter as well as calendar/date and Features modules
• eri:2.5hr:created calendar view and resource view; inputted content from main eri site; built taxonomy term hierarchy to filter resources from events that are displayed in the calendar GUI

2012-07-16 Mon -- 4 hrs

• eri:1hr: compiled questions and met with Aaron about drupal
• eri:1.5hr:researched calenda and bibliography modules and tested pannel settings
• eri:1.5hr:created test pages, views and blocks for various attachment types; adjusted attachment settings; followed Chris's guide to using arguments to filter content into table view; tested tokens

2012-07-15 Sun -- 0 hrs

2012-07-14 Sat -- 0 hrs

Week of 2012-07-07 to 2012-07-13

2012-07-13 Fri -- 4.5 hrs

• eri:0.5:reviewed CEIN modules and theme options

• eri:2.5h:built quicktabs table and bio type on eri7a-dev -- couldn't filter content by taxonomy term

• eri:1.5:figured out work around for filtering quicktabs content -- still doesn't match structure of CEIN quicktabs; added test menu from biogeog to eri7-dev; tested forum module

2012-07-12 Thu -- 5.5 hrs

• eri:3h:read drupal module development guide and git use, theme development
• eri:2h:reviewed structure of quicktab module and people tab guide, functionality of CKEditor
• eri:0.5h:met with Darla about Wordpress uses and theming/layout

2012-07-11 Wed -- 4.5 hrs

• eri:1.5h:started reading drupal documentation guide
• eri:3h:worked with eri7-dev drupal settings

2012-07-10 Tue -- 2 hrs

• eri:1h:training/intro

2012-07-09 Mon -- 0 hrs

2012-07-08 Sun -- 0 hrs

2012-07-07 Sat -- 0 hrs

Week of 2012-07-01 to 2012-07-06

2012-07-05 Thu -- 0 hrs

2012-07-04 Wed -- 0 hrs -- Independence Day

2012-07-02 Mon -- 0 hrs

2012-07-01 Sun -- 0 hrs

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

Calendar Guide

Location

• The current calendar/resources setup is located at: http://www.eri7a-dev.eri.ucsb.edu/events_resources

Structure

• Calendar view is a page with location "events_resources"
• Resources is a view placed under "Main Page content" in the "Content" block

1. Set to only be displayed on "events_resources/*" and "events_resources"

Advanced Instructions for Calendar

• It should be noted that, to create a new calendar page or block, you must use the "Add view from template" feature rather than "Add new view," as doing the latter will produce an error and not display the calendar

1. Once you have clicked "Add view from template," chose the "Calendar" option with the description "A calendar view of the 'field_date_time' field in the 'node' base table."

• To filter content into the Calendar, the "Filter Criteria" in the Calendar view is used.
  • It checks to make sure that:

1. The content is published
2. The type of the content is "Event"
3. It does not contain the term "Resource" in its taxonomy
   1. This is done with the "Has taxonomy term" filter, with the "Is none of" operator.

• The value "Content: Type" under the "Fields" heading is necessary to color-code events based on their taxonomy term. If you would like to change the taxonomy vocabulary, this item must be kept and updated to match the new terms of the vocabulary

Advanced Instructions for Resources Table

• The resources table has a slightly more complicated filter than that of the calendar (filter settings are located in Structure->Views->Resources).

1. Has taxonomy term is equal to "Resources"
2. Start date of Resource will be filtered by the date the user selects in the year and date drop-down menus.
   1. "Expose this filter to visitors, to allow them to change it" must be checked for user to be able to select their month. If this checkbox is disabled, the date filter should be turned off to display all Resources.
   2. AJAX must be turned on for this to work

• Global Text area is set to display "Resources" as a padded header above the table because the default Header styling was a little cramped. This could be accomplished by editing the stylesheet instead.

Terms/Taxonomy

• Vocabulary: Event Type
• Terms:

1. ERI Meeting
2. ERI Seminar
3. ERI General Event
4. General UCSB Event
5. Resource
   1. Shows up in "Resources" block under calendar
   2. These events should contain a link to the resource in the description

To Add New Event/Resource

• Click "Add Event" under "Administration" in Sidebar Menu
• Enter title, description (which should include a link if possible), date (this has multiple options, and can span a range), event location, and finally category

1. Be sure to only select "Resource" if you don't want the event to show up in the Calendar, and would instead like it to appear as a link in the table below the Calendar
2. If item is a resource, you should input the dates that the resource will be relevant. For example, if you are posting a restaurant menu for the month of July, put 07/1/12 as the start date and 07/31/12 as the end date. If you do not want the item to expire, select today as the start date, and some time far in the future as the end date. This is a workaround, and the CMS student assistant should work to find a cleaner method of setting a non expiring resource.

• Click "Save"

Customizations/Additions

• You can add new event types by going to Structure->Taxonomy->Event Type =>Add Terms

1. Once you have added a term, to define the color that the Event type should show up as in the calendar, go to Structure->Views->Calendar => edit-> Format -> Settings next to Calendar Entities
   1. Scroll down to the bottom and use the color selector next to the term you have just added
   2. Click "Apply"
   3. Click "Save" at the top of the Calendar menu

Usage

• Calendar month can be changed by clicking "Next" or "Prev" at the top right of the page above the Calendar
• You can check resources applicable to a given month by selecting the "Year" and "Date" under the "date" heading above the table of resources. For example, if this month is July, and I want to see a menu for this month, I would select 2012 and July.

Portability Notes

• Since there are many components necessary for this page to function, it seems like the easiest way to move the entire page to another site would be to export all of the elements as a module using the "Features" module that is on both the eri7-dev and eri7a-dev sites.
• To create a feature, go to "Structure"->"Features" and then click the "Create Feature" tab at the top of the box that appears.
• Below is a non-comprehensive list of all the elements that should be included when exporting the "Feature." If this is not the first time exporting the feature, check the last version name to avoid naming confusion. The Update XML field can be left blank for now.

1. Content types
   1. Event
2. Dependencies
   1. Block
   2. Calendar
   3. Color
   4. Chaos Tools
   5. Date
   6. Date All Day
   7. Date API
   8. Date Popup
   9. Date Repeat API
   10. Date Repeat Field
   11. Date Tools
   12. Date Views
   13. Field UI
   14. List
   15. Options
   16. Path
   17. Taxonomy
   18. Views
   19. Views UI
3. Fields
   1. node-event-body
   2. node-event-field-date-time
   3. node-event-field-type
   4. node-event-field-location
4. Taxonomy
   1. Event Type
5. Views
   1. Resources
   2. calendar

• Once the module is downloaded and installed on the desired drupal installation, events specific to the site must be added using the same content type as mentioned in this tutorial (the content type should be included when exporting the "Feature"). Also, side menu item must be added to reflect location of calendar -- this might not change, but because the module doesn't include the menu item, the new menu link must be added anyway.

Other Stuff

AVWH: 168