It's not quite clear what you're asking. Are you saying that studies retrieved via the DICOM Query Retrieve plugin are being anonymized using the site anonymization script, and you want that not to happen? If so, I
think this would work:
- From Administer > Site Administration > Miscellaneous, click the "View the Swagger page" link to launch Swagger.
- Find the "archive-processor-instance-api" API.
- From the call to /processors/site/enabled, get the list of active processors. Find the entry with a "processorClass" of "org.nrg.xnat.processors.MizerArchiveProcessor".
- Make it so that this processor (site anonymization) does not run on your DQR receiver. You can either use the PUT to /processors/site/id/{instanceId} and exclude the processor from your receiver with a whitelist/blacklist, or you could just delete it with
the DELETE to the same endpoint.
You should back up your system before doing this (and do it on a dev server first), but the reason I think this would work is this: site anonymization is handled in two separate ways.
- For a receiver not using custom processing, site anonymization ignores the processors and happens if the script is enabled.
- For a receiver using custom processing, site anonymization only happens if you have the site anon processor set up (which is set up by default).
So, if you have a standard receiver not using custom processing, that receiver could receive studies not from DQR and still run site anonymization, while your custom processing receiver for DQR would skip anonymization.
Hope that helps.
Thanks,
Charlie