Using Organic Groups to create separate "sites" in one Drupal installation (Jessie Keck)

Event Date/Time

Fri, 5 Mar 2010 - 1:00 pm - 3:00 pm
Location: 

Law School room 85

Jessie Keck ( digital catalogs / collections ) will demonstrate how lib.stanford.edu uses Organic Groups to create separate "sites" in one Drupal installation.

This session is confirmed for 1 pm in room 85 of the Law School. (Thanks for signing up!)  

  • Mulitsite does not provide complete single code base for modules (did not need multiple settings for modules in different sub-sites)
  • Some modules do not work well with OG (are not OG-aware)
    • taxonomy does not provide OG-specific issues / need OG vocabulary module http://drupal.org/project/og_vocab
    • cck does not have OG settings
  • http://drupal.org/project/panels_tabs for sliding tabs
  • New group can choose a template
    • template defines what is on the front page http://lib.stanford.edu/files/u32/Group1.png
  • Documentation http://lib.stanford.edu/drupal-docs / http://lib.stanford.edu/drupal-docs/set-up
  • tag pages using group menu vocabulary (not clear, need demo)
  • The tabs at the top of the page, ( in https://lib.stanford.edu/art the Home, Exhibitions, New Books, etc ) are provided by the OG Panels module packaged with the OG module.
  • Drupal search is inadequate, GCS configured for each subsite
  • Ribbon with hours/location is implemented as a content type with taxonomy for the ribbon type
  • Skill-set to define content on the group home page is same as skillset needed to edit - custom templates approach does not scale as number of sites grow and number of web developers/support stay the same
  • It is nice when themes are OG-aware (e.g. adds OG to standard drupal title)
  • User management - no group-specific roles
  • Private sites with limited access to a site, some info visible only to group members
  • Sharing content between several groups / audience (e.g. visitors' info page)

Last modified Fri, 5 Mar, 2010 at 16:00