December 05, 2011

Optimizing on ITS Umich servers

Just a few implementation notes optimization tips I picked up at Drupal Camp Michigan.

Check suggestions from Google PageSpeed.

mod_deflate -

Ask ITS ( to enable this on the server. Then add something like the following to .htaccess:

# compress text, html, javascript, css, xml: AddOutputFilterByType DEFLATE text/plain AddOutputFilterByType DEFLATE text/html AddOutputFilterByType DEFLATE text/xml AddOutputFilterByType DEFLATE text/css AddOutputFilterByType DEFLATE application/xml AddOutputFilterByType DEFLATE application/xhtml+xml AddOutputFilterByType DEFLATE application/rss+xml AddOutputFilterByType DEFLATE application/javascript AddOutputFilterByType DEFLATE application/x-javascript

mod_expire -

This will allow the server to Leverage Browser Caching.

Ask ITS ( to enable this on the server. Drupal's primary .htaccess file should be configured out of the box for this to work.

Posted by kkwaiser at 10:59 AM | Comments (0) | TrackBack

May 07, 2010

NSF data management requirements

Here's a story in Science about NSF data management plan requirements.

And here is an email response I wrote to the person who drew this to my attention:

I think UMBS may serve as an example of one type of departmental-level response to this. We've currently finished drafting a data management policy (please don't circulate):

and we recently inserted a section on data management into a proposal our Director, Knute Nadelhoffer, is on. I think the next step for us will be to draft a generic appendix that meets requirements of the NSF solicitation (; see below). We (I) would then be available to the researchers to identify likely future datasets and customize the appendix.


(A-1) Data Management Plan (maximum 1 page): Development and adherence to community-wide standards for collection and presentation of data, such as microarray or interactome data, are highly encouraged. Large-scale datasets must be made available in a format that enables rapid comparison and effective utilization of reproducible information. All proposals must include a detailed data management plan if the project is expected to generate significant digital data for preservation (maximum 1 page). The contents of the data management plan should include:

* The types of data to be produced
* The standards that would be applied for format, metadata content, etc.
* Provisions for archiving and preservation
* Access policies and provisions
* Plans for eventual transition or termination of the data collection after the NSF funding period


Posted by kkwaiser at 11:01 AM | Comments (0)