mlhim-owners team mailing list archive

[Timothy Cook <timothywayne.cook@xxxxxxxxx>]

Dear Luciana,

Actually CCD is supposed to inherit  from AuthoredResource which defines the
meta-data.   So what needs to be done is to copy those attributes from
AuthoredResource onto CCD and they can be completed there.

If you will take care of that I will appreciate it.

Sincerely,
Tim


On Wed, Apr 20, 2011 at 7:33 AM, Luciana Tricai Cavalini <lutricav@xxxxxxxxx
> wrote:

> Hello MLHIMers,
>
> Next week we will (slowly) start to build CCDs for our projects and the
> modeling people are concerned about the fact that there is no place to
> register the CCD metadata (what's called the "header" in the openEHR
> archetypes), especially the authorship information.
>
> The plan is to have that directly registered on HCKR when the CCD is
> about to be commited, what I think it is the best idea, but the fact is
> at this point we don't have a functional version of HKCR and that will
> take a certain time due to the operational situation of the HKCR project
> - basically (IMO), no community enough working on it, what is not
> anybody's fault; the project is complex indeed and some ideas are still
> taking shape or demanding documentation.
>
> OK, but the CDD project is cruising, and we have a functional version of
> CDD, so I can't see any reason for us to delay the development of CCDs
> while we wait on HKCR to be up and running.
>
> But I agree with my colleagues that we need to have a provisional
> solution for the fact that the CDD doesn't register metadata. I can see
> three alternatives:
>
> 1) Writing the metadata on a separate file and commit both on a zip file
> to the HKCR branch that I will create as a provisional CDD respository
> while HKCR is being developed;
>
> 2) Creating a new tab on the CDD named "Metadata" and allow people to
> fill it up with the metadata there. When HKCR is ready, this Metadata
> tab on CDD could be removed.
>
> 3) Not doing anything and relying on our memories to remember the
> metadata (including authorship) of a given CCD when HKCR is ready.
>
> I vote on (2) because the "separate file" or the "memory" ideas sound to
> me like the problem of missing context that the MLHIM and the openEHR
> people are trying to solve. Especially the "memory" idea. I am sure I
> won't remember the metadata (including authorship) of a CCD that I
> modeled 6 months ago. Depending on the person, he/she won't remember
> that even 6 weeks or 6 days ago.
>
> But I have the impression that some of us could feel uncomfortable with
> the idea (2), so I would like to ask for alternative ideas to solve this
> problem of the metadata registration for CCDs while we don't have HKCR
> functioning.
>
> Otherwise, if everybody thinks the the idea (2) is the best idea that he
> have at this point, I would like to ask permission to edit the CDD 2.1
> *.xmt file, including the Metadata tab, according to the Dublin Core
> standard, that I think I found on http://dublincore.org/documents/dces/.
>
> Thank you,
>
> Luciana.
>
>
> --
> Esta mensagem foi verificada pelo sistema de antivírus e
>  acredita-se estar livre de perigo.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mlhim-owners
> Post to     : mlhim-owners@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mlhim-owners
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
================
Timothy Cook, MSc
Project Lead - Multi-Level Healthcare Information Modeling
http://www.mlhim.org

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
Skype ID == timothy.cook
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or
from this link http://timothywayne.cook.googlepages.com/home