Alan Gutierrez

Morphing Grid by Dan Allison.

Ever find yourself with a data collection, and you can see the steps in your head, create a form, create a table? It’s a dry task that gets dryer by the minute once you find yourself once again creating that paged results table for the contact us or event registration form you’ve created a thousand times before.

I can’t tell you how much slicker it is to send that data directly to an EditGrid workbook. It is a quick and easy database that is intuitive for your users. Instead of a paged html table, their information is available as rich full-featured spreadsheet.

My Tchotchke Boxes by 1213 1982.

I created a series of online spreadsheets of every building, construction and demolition permit issuesd in Orleans Parish since January 2005. These spreadsheets are available at Think New Orleans.

The EditGrid API can automate the creation of reports and act as an easy use and share database for light data collection applications. I’ll write about my experience with EditGrid and why you should consider EditGrid at the back end for your next data collection task.

This is my programmer notebook on my getting to know you time with EditGrid.

I wrote my program in Java. Here are the three gotchas that I encountered.

Every time I create a new listserv, I need to remember how to do it. I’m going to write about it in Blogometer so I don’t have to think so hard next time.

Adding a new GNU Mailman listserv.

[alan@~]$ cd /usr/lib/mailman
[alan@ljubljana mailman]$ sudo ./bin/newlist barcampnola@thinknola.com
Enter the email of the person running the list: alan@thinknola.com
Initial barcampnola password:
To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases’ program:
## barcampnola mailing listbarcampnola:              “|/usr/lib/mailman/mail/mailman post barcampnola”
barcampnola-admin:        “|/usr/lib/mailman/mail/mailman admin barcampnola”
barcampnola-bounces:      “|/usr/lib/mailman/mail/mailman bounces barcampnola”
barcampnola-confirm:      “|/usr/lib/mailman/mail/mailman confirm barcampnola”
barcampnola-join:         “|/usr/lib/mailman/mail/mailman join barcampnola”
barcampnola-leave:        “|/usr/lib/mailman/mail/mailman leave barcampnola”
barcampnola-owner:        “|/usr/lib/mailman/mail/mailman owner barcampnola”
barcampnola-request:      “|/usr/lib/mailman/mail/mailman request barcampnola”
barcampnola-subscribe:    “|/usr/lib/mailman/mail/mailman subscribe barcampnola”
barcampnola-unsubscribe:  “|/usr/lib/mailman/mail/mailman unsubscribe barcampnola”

Hit enter to notify barcampnola owner…

[alan@ljubljana mailman]$

Then you cut and paste the aliases into /etc/mailman/aliases

[alan@ljubljana mailman]$ sudo /usr/bin/newaliases
[alan@ljubljana mailman]$ sudo ./bin/withlist -l -r fix_url barcampnola

My server, ljubljana.blogometer.com, will sometimes hang after receiving too many requests. I don’t want it to keep me from getting in via ssh, so I’ve written a rather drastic shell program to monitor the server. It fetches the blogometer.com home page using curl. If it takes longer than three seconds, it blocks port 80. This is run by cron every minute. The script will write out the output of the programs ps ax and free. I’ve not been able to figure out what’s really causing the server to choke with that output so I’ve added top -n 5 -b and tail -n 500 /var/log/httpd/access_log. I’m open to any suggestions of commands to add to this snapshot.