I've read the various forums including Drupal tags where I have not seen this question asked, so I hope it's not a repeat question.
Why can we not port Omeka as a Drupal module? A lot of institutions and groups run Drupal as a front-end to their projects, so it would make sense to create a dependent version of Omeka that integrated into Drupal (or maybe wordpress, although I'm not as familiar with their level of add-in module support).
It would *seem* to me that the integration could leverage a lot of what has already been done. Couldn't we simply set a definition variable at installation? Perhaps
if ($drupal_node == "FALSE") define("INSTALLATION", "Standalone"); else define("INSTALLATION", "Module");
Then we use this definition to run a series of functions dependent on the need. So, if we're a module, we'll pull DB information and schema from the Drupal parent, but if we're stand alone we create a new db and build in that?
** Caveat - I have not poked around in the Omeka code base to see if this is possible / feasible. I'm just wondering about it. Maybe a project I pick up after dissertation time is over....