Hi Bert, [this thread may belong on the implementers list?]
On Wed, 2008-04-23 at 14:43 +0200, Bert Verhees wrote: > I have my system ready in a way that it eats archetypes, and data > belonging to those archetypes, and stores them in over a persistence layer. > There is only one important step, that is, what is a good way to connect > the data to the archetypes. Is this dADL, or better XML, or other means. I'm not sure I understand you correctly. But are you saying that you are storing an empty archetype in a repository and then in other tables (assuming a SQL database) storing the data collected from a GUI or webform that was based on the RM constraints represented by that archetype? If this is the case then you must be creating a new table for every archetype (and every new version of it) used. In that case then each table would be related to the archetype via it's ID. I guess I am also assuming that you are storing archetypes in your repository as ADL or XML serializations? This approach seems to me that it would take ALOT! of source code in order to manage connecting the data rows back to the archetypes. Hmmm, say a module for every archetype? If you could describe your data capture process a bit more as well as your persistence approach it will help. Of course I cannot leave one of these types of conversations without mentioning the utility of using an OODBMS for inherently hierarchical data. :-) Cheers, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ************************************************************** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ************************************************************** -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080423/8b00dc87/attachment.asc>
