Re: [Teem-users] Suggested naming convention for dicom tag information in NRRD headers

[Gordon L. K. <gl...@uc...>]

This is an interesting and important use for the key/value headers, but no, there isn't any more general convention.

My only advise is to see if you can follow any precedent set by DICOM to JSON meta data converters.  The Nrrd header is obviously not as flexible as JSON, but someone may have already figure out a strategy for mapping the possible zoo of DICOM tags to some consistent simpler representation.

Certainly, it would seem like you should be to include the numeric codes that identify tags, like (0020,0037) for Image Orientation (Patient), in the key name.  

In general, I would err on the side of making the key strings longer and more verbose.  It decreases the chances of them being misinterpreted later, or clashing with different (and possibly incompatible schemes).  (Human) Legibly is nice but reliably meaningful (algorithmic) parsing is essential.

Let us know what you figure out.
Gordon


On Jul 30, 2015, at 7:16 AM, Caspar Jonas Goch <cjg...@gm...> wrote:

> Hi all,
> 
> we are currently facing the requirement that users of our library want some dicom tag information saved to the NRRD header when they convert their data.
> 
> I know that there is a naming convention for DWMRI data header information we stick to so other tools can work with it. Is there a general convention for other tags as well? So far I have not been able to find anything.
> 
> Any hints or suggestions are very much appreciated.
> 
> Best,
> Caspar
> 
> More details for those interested:
> 
> We have not finalized which data we want to store, but it is probably going to be a couple of dozen fields concerning sequence information and acquisition parameters from official dicom tags as well as custom ones. Additionally we will store information which is not saved in the dicom tags at all but added at a later date.
> 
> While it would work for us to just use our own keys and be done with it, I would prefer to stick to an established convention if possible.
> ------------------------------------------------------------------------------
> _______________________________________________
> teem-users mailing list
> tee...@li...
> https://lists.sourceforge.net/lists/listinfo/teem-users