From: Ed R. <ero...@ug...> - 2005-02-15 15:15:07
|
I have two issues with some plugins I am writing. The first is that when I load data sets produced by various predictive algorithms, I need to include a review status. This is a non-null field in most of the tables. The easy solution, and the one many older plugins use, is simply to hardcode it. Of course, hardcoding means everyone else that uses the plugin will have to use the same values in their database. It also creates the possibility of different plugins having different values. What I would like to do, and this is also a suggestion of Steve's, is to assume that all GUS instances have named values in SRes.ReviewStatus, "reviewed" and "unreviewed". All of my plugins will begin by loading the values for these into cache and using them. If they are not present in the table, then the plugins will die with an error message. This will be the default operation of all of my plugins. I would like to propse that this become a standard for all plugins. In fact, it probably should be part of the plugin superclass. If we want to have a few more assumed review status types, then we can include those as standard names also. Ultimately, these names should all be included somewhere in the Installation scripts. Comments, disagreements? thanks -Ed ----------------- Ed Robinson Center for Tropical and Emerging Global Diseases University of Georgia, Athens, GA 30602 ero...@ug.../(706)542.1447/254.8883 |