Sadie is a general-purpose data server written in Ruby and it's intended to be used by a Rubie developer to simplify access to inter-related data sets.
It is designed to provide handle-based access to data of all types, much like a simple hash. Unlike a hash, a sadie instance is created with a pathname which points to a directory of primers which tell sadie how to determine what the value of a given hash key should be, but values are not assigned until the hash keys are requested. In this way, only necessary data transformations and/or accesses are performed.
Valid primers currently are:
.ini - provide access to section, key, value data in ini-style-files .dbi.conx - simple access to database handles .sql2ar - simple access to database data .res, .res.rb - provides access to general-purpose, programatic manipulation of data (i.e. just use sadie instance for input and output of data) .tmpl - simple templating engine for text-based file types
It's very simple to add new primer types, so it would be simple to create primers for html, xml, csv, xls, pointers to all of the above on remote machines, or any- and everything else.
At Landmetrics, we use a predecessor to Sadie to power perimetercomps, producing each 50+ page report with charts, graphs and tables with only 12 queries to the database.
As noted above, perimetercomps is an example of how one might use sadie to to create a templating engine wherein many pieces of related information from many different sources are made into charts, graphs, tables and text before being assembled into a single deliverable document. We used LaTeX, but html, xml, css, txt, etc. would be just as easy.
- data import
Tasks involving grabbing data from different places in different formats and massaging the data into a consistent and useful format. A few simple primer plugins would make this very easy.