From: Fernan A. <fe...@ii...> - 2005-06-01 13:26:15
|
+----[ Michael Saffitz <msa...@pc...> (31.May.2005 15:52): | | Hi Fernan, | | In general, the issue here is that the current (and soon to be released 3.5 | schema) doesn't fully allow for representation of a particular domain. As | discussed, one approach is to "massage" the data into the available schema, | but as noted, this is not ideal for numerous reasons including overall | compatibility, data model clarity, integration concerns, and so on. The | only other approach then is to change the data model/schema to fully support | the domain. You may do this locally, within your own GUS instance, or (and | much preferred) you may submit the changes to the GUS community for | inclusion with the GUS project. I completely agree. | This latter route is what I'd suggest in this case. The | procedure for this is: | | 1) Create a ticket in the tracker with the proposed | changes, being as specific as possible. SQL DDL is much | appreciated. Maybe a diff against gus_schema.xml? Seems to me easier to apply. | 2) Send an email to the list requesting feedback and comments on the change. | This allows the community to evaluate the change and work as a whole to come | up with the best solution. Sometimes this step is not required for smaller | changes, and sometimes this step and the first step are switched in order. | | 3) Once the community has come to a consensus about the change, it will be | incorporated into GUS and included in the next release. If you need the | change sooner, you may receive it by using a CVS release of GUS (assuming | GUS 3.5 here). | | Hopefully this addresses the more larger issue and your questions as well. | | Thanks, | | Mike | +----] Just a minor issue: is it possible to submit 'tickets' to CBIL's bugzilla by email? I know bugzilla has this functionality and it is much more convenient (at least for me) to submit things this way. Fernan |