Project anonymization and session XML content

[Duncan Smith]

Hi all,

We were recently reminded of an older issue where if only using project level anonymization, the session XML file appeared to be generated before the anonymization script ran, so would contain fields that had then been stripped immediately after.

After some testing on XNAT 1.7.6 I haven't been able to see the same issue, so I wanted to check if this issue has now been officially resolved or if the testing has missed it.

The issue in question: https://issues.xnat.org/browse/XNAT-3267

Thanks,

Duncan

[Moore, Charlie]

Hi Duncan,

The last time I looked at that ticket on a recent version of XNAT (I think it was around 1.8.2?), I wasn't able to recreate it either. That is, I think it got fixed at some point in time, but not knowing why/how makes me a little nervous so I haven't closed the ticket out because it's such a serious one. So, I wouldn't say it's really "officially" resolved, but it sure seems like it is.

Sorry for the likely unsatisfying answer,

Charlie

---

From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Duncan Smith <duno...@gmail.com>
Sent: Wednesday, January 5, 2022 9:03 AM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Project anonymization and session XML content

 

* External Email - Caution *

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/04c0e489-9b5a-474e-827d-0a21a3e48e41n%40googlegroups.com.

 

---

The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. 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.

[Duncan Smith]

Hi Charlie,

Thanks for the response. We'd been looking through some of our old XNAT issues but I don't believe we have run into this for quite a while, so it's useful to know the current situation.

Duncan