Rodrigo Filgueira wrote: > I'm trying to understand where audit details are used and how. > My first thought was that it had to be an attribute of contribution > which is correct, but then I found it is also an attribute of the > VERSION class. > > Then I thought, ok this is better, let's audit each version and we are > done. The first version holds the info about the original > "submission", the second for the second version, etc. > > But why do we need it in contribution? of course I'm missing something > because contribution without audit details is nothing. As you may have > probably already discovered out I do not get the need for > contributions and in particular do not understand why EHR has a list > of contributions as an attribute and a list of versioned compositions > too. because 1 Contribution corresponds to 1 change-set, which might include new versions in more than one VERSIONED_OBJECT. The audit of each Version says what each change was about (e.g. a correction, an addition, etc etc) while the audit for the Contribution corresponds to the group of changes as a whole, e.g reason might be "encounter 12/07/2004". There will be some likely repetition of dates and times to be sure - that's what happens in version control systems. The BitKeeper commercial change managment tool that we used to use in openEHR works on exactly this principle. > > I've been reading the common package and these answers are quite > elusive still. > Any help would be greatly appreciated. version control is a difficult area for many people to get their heads around, and maybe the explanations there are not yet good enough. Any feedback on improving the explanations is welcome.
- thomas beale
