XNAT 1.6: anonymization script issue

198 views
Skip to first unread message

Isaiah Norton

unread,
Sep 13, 2012, 11:46:24 AM9/13/12
to xnat_di...@googlegroups.com
Hi,

I recently installed XNAT 1.6 and am  trying to use the site-wide anonymization feature. I created a script under Administer->Configuration->Anonymization, starting out with only the few basic fields as shown in the Anonymization section of the documentation:

(0008,1030) := project
(0010,0010) := subject
(0010,0020) := session

Unfortunately, this script does not seem to be applied to my data at either the prearchive or archive stage. The original name, MRN, and session id are displayed in the prearchive and remain in the archived images (verified with dcmdump).

I have also enabled the same script at the project level, but this did not help.

I would be grateful for any pointers about where to start tracking this down. I checked xdat.log and saw some old messages about FileNotFoundException and NullPointerException, but they predate my most recent data push by at least 20 minutes.

Thanks,
Isaiah




Sanket Gupte

unread,
Sep 20, 2012, 5:49:02 PM9/20/12
to xnat_di...@googlegroups.com
I was just going to make a post about this but thought about searching if someone has a similar issue. So, I am not the only one. :)

From what I get about DicomEdit, I made a tiny modification in the pre-existing 3 lines of anonymization.
I made it

session := format["{0}-{1}",(0008,0050),(0010,0020)]

(0008,1030) := project
(0010,0010) := subject
(0010,0020) := session

Well, it doesn't work. Am I doing something wrong? is there any other place where I have to 'Enable' this Anonymization script?

Moreover, a few times it happened that, even after considerable amount of modification in the script, when I hit 'Save' it still gives the Message "None of the site information appears to have changed".

Herrick, Rick

unread,
Sep 21, 2012, 9:46:28 AM9/21/12
to xnat_di...@googlegroups.com

Hey Sanket,

 

There definitely appears to be a bug in the dirty flag handling (the thing that makes it say nothing’s changed) in that dialog. I’m looking into it right now. Thanks for the info.

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/xnat_discussion/-/0TAUgN9vBW0J.
To post to this group, send email to xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to xnat_discussi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xnat_discussion?hl=en.




The material in this message is private and may contain Protected Healthcare Information (PHI). If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

Herrick, Rick

unread,
Sep 21, 2012, 4:20:38 PM9/21/12
to xnat_di...@googlegroups.com

Hey Sanket,

 

I’m reasonably certain that the issue is related to how the form is getting “dirtied” in the interface. Basically there’s a check to keep you from saving settings when nothing’s been changed. Once you change a checkbox or setting in a tab, the Reset button should be activated and you should be able to save as well. The textbox on the anon script tab is a bit of a pain, because that requires capturing keystrokes and different browsers do this in different ways.

 

I’m guessing (hoping? J) that you pasted your changes to the script into the textbox, which won’t trigger the onkeypress event in many browsers . As a possible work-around in the short term, try just typing a few characters directly into the textbox, then deleting them. This SHOULD trigger the dirty mechanism and make it possible to save the changes to the anon script.

 

I have a fix that will be in 1.6.1 today that *should* make this work more as you’d expect.

 

We’ve tested the anon script itself and your changes work as we’d anticipate they would, the catch is just getting the script changes saved!

 

From: xnat_di...@googlegroups.com [mailto:xnat_di...@googlegroups.com] On Behalf Of Sanket Gupte
Sent: Thursday, September 20, 2012 4:49 PM
To: xnat_di...@googlegroups.com
Subject: [XNAT Discussion] Re: XNAT 1.6: anonymization script issue

 

I was just going to make a post about this but thought about searching if someone has a similar issue. So, I am not the only one. :)

--

You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/xnat_discussion/-/0TAUgN9vBW0J.
To post to this group, send email to xnat_di...@googlegroups.com.
To unsubscribe from this group, send email to xnat_discussi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xnat_discussion?hl=en.

Sanket Gupte

unread,
Sep 24, 2012, 2:44:14 PM9/24/12
to xnat_di...@googlegroups.com
Hi,
About the anon script. It still doesn't work for me. So, may be I am doing something wrong, or having trouble understanding DicomEdit.
When I did
session := format["{0}-{1}",(0008,0050),(0010,0020)]

(0008,1030) := project
(0010,0010) := subject
(0010,0020) := session

I was hoping that say if (0008,0050)=1 and (0010,0020)=subSess1 in my Dicom header, then after the script,
session =1-subSess1  AND when I do Dicom SCP send of this scan/session, in the pre-archive the session name is '1-subSess1' . But it is not.

Am I understanding it wrong?
My goal:- Have the session name automatically assigned before/when the scans arrive in pre-archive.
Reason:- I have 10TB of data, I cannot look into the naming of each scan/session, but I would still want it to have a similar naming convention.

P.S: It didn't work when I put it in the project specific anon block either.
Reply all
Reply to author
Forward
0 new messages