Drupal 6

I needed to come up with a solution for overriding the links in the search results for the campus map project. I've created a view that uses OpenLayers presets for getting a zoom level. In the view we use the standard node/%/map_detail path to get the detail view preset applied for the appropriate node nid.

I had a brief conversation with Pablo and Alma last week and it got me thinking about how we could prototype a method of pushing information via SMS to students. If I understand the use case, we're talking about a small population that primarily relies upon their phone for communication and is missing important campus communications sent via email, flyer, portal or US Mail. Our objective would be to push information using SMS as a supplementary protocol.

I've been working with the Campus Sustainability office to identify how we might make some changes to their look and feel as well as add some functionality. They've been limited by the old campus template and need to get a fresh look without the use of the new campus template, which won't be available to them on the short term.

I've been prototyping some new ideas to get us thinking about the roadmap for the campus map. A working demo is at http://maps-dev.ucsc.edu. The notes link below talks about the technology stack; Drupal, Gmap and Location modules were evaluated in the first round and later eliminated. I've landed on the OpenLayers and Geo modules for the type of requirements we need to meet.

I'm working with John Rocchio on the prototyping of a shopping cart to assist Dining Services. See the demo at, http://asg-dev2.ucsc.edu

Problem/Opportunity

The problem/opportunity can be defined as a process improvement. Dining Services has been using a PDF based form to allow students to order and take advantage of campus purchasing power. Essentially, an on-campus student may order a box of cereal and pick it up. A financial transaction takes place at the time of delivery. 

I've been collecting resources on my own over the past year or so as I've taken a deep dive into Drupal. I'm now in the process of training some of my staff and lead contacts in Drupal. In several cases, we'll need to buy some duplicate copies of books and thought this might be a nice place to provide a list and some of my thoughts on their usefulness in my work.

I worked with Chief Trapp and Emergency Planner Gaylord to finalize our requirements around managing the contact information for Emergency Operations Center (EOC) members. The EOC is a functional approach to managing operations associated with emergencies that range from large protests to earthquakes. I've previously written on the subject of EOC Contact Management.

Background

[see http://peterm.ucsc.edu/drupal/content/how-were-using-open-atrium]

We need a method to handle work intake using as much of the ITS project management methodology as possible. Basically, this involves getting the appropriate details and initial scoping information into a one page form. One of the benefits of following the methodology is that we can aggregate and start to look at priorities against capacity for our group.

I wanted to upgrade the aegir tools on the -dev and -prod sites. I ran into some problems running the upgrade steps; which are probably due to some mistake I had made in managing the changes made since the original install. During the upgrade process, I was getting a variety of database error messages. I'm assuming that part of the problem was that I had originally installed 0.2, then upgraded to 0.3 and somewhere along the line, upgraded drush. Another symptom I was seeing was that my crontab for aegir was gone, so I could not process tasks.

I came back to work on the TPP project over the past few days. A couple of problems needed resolving. First, I'd used the CCK float type instead of using Decimal type to hold salary data. While it worked for hourly and monthly salaries, annual salaries were longer than the column could allow. So, I started my test by deleting the 37 float fields and recreating them as decimal 10,2.