By dambrisco on
http://intron.healthcare.uiowa.edu/database
This extremely basic site is one that has recently hit a more or less "stable" point in terms of what information is currently available. Probably won't make much sense to anyone without a genetics background of some kind, but it was a fun project to learn Drupal on.
There's plenty more available to logged-in users, but since that data is all unpublished as of yet, it isn't visible to the public.
Comments
Good stuff
Nice work.
I'm looking to learn from your work. I'm guessing Panels, Views (attachments?), Webform, Taxonomy for the GO, content type and CCK for fields. Any other modules that are central to the site?
How is the search done?
Any advice you can offer to other Drupalistas?
Kieran
You're about half right
Views, content types, and CCK. Mostly CCK and some terrible overall Drupaling. (I probably should've used Panels, Webform, and Taxonomy, but I never even looked into it out of laziness. Except Taxonomy - that decision was made based on the ridiculous number of terms possible.)
The GO terms are generated via a Python script that references two massive spreadsheets via a Computed Field. I can post exactly how I managed this if you'd like.
Everything else, including the search form, is Views manipulation. The search is a set of exported filters put into a block.
From a standpoint of breaking all the "rules" of Drupaling, I'd say that Computed Fields are your best friend. Pretty much everything that isn't plain-text in those exon pages was created using a Computed Field.
From the other side, I'd suggest getting your hands dirty with a custom, self-made module as soon as you've got a good grip of the basic parts of Drupal. It's complicated and frustrating at times, but it opens up entire worlds.
Feel free to contact me about anything. Chances are I might not always have an answer, but Drupal's become something I love over the past few months.
- Dan
Thnx
Thnx for the info. Computed Fields does look powerful. Have to play around with it.
Kieran