Bert Verhees wrote: > I have a problem with both archetype-editors, I explained a few times on this > list why. > Both change archetypes while loading them, f.e. one likes to add node-id's to > datavalues, and the other does not like that. > There are some more incompatibilities, between the both. I forgot the details. > Then one is not able to create demographic archetypes, also a problem. > --------- > Both are not configurable. > I would like to have an archetype editor which can be feeded with some > RM-definition, and configured to use it, and then is being able to create > archetypes following that definition. > ... > Do you know how I create archetypes (I don't if I can someone else having to > do it :), but I work my way in LinkEHR or the Ocean editor, and edit them > manually in a text-editor, with syntax-highlighting.
Hi Bert, Problems with the Ocean Archetype Editor should be reported to http://www.openehr.org/issues/issues/?jql=project%20%3D%20AEPR . The Ocean Archetype Editor only gets worked on when we have spare time, or if there is a pressing business requirement for us to fix something in it, so mentioning a problem on a mailing list is not likely to get it fixed. If you have examples of archetypes generated by LinkEHR that are not handled properly by the Ocean Archetype Editor, please attach them to your problem report. Alternatively, you could try fixing it yourself. I recall that you compiled it under Mono a few years ago, but you had a problem that there were dependencies on some DLLs that only worked under Windows. We have removed those dependencies, so you should be able to build it successfully under Mono these days. But I understand that you're a very busy guy yourself, so submitting a problem report would probably be best ;-) Peter
