This new plugin supersedes the previous Sample Modality worklists plugin. The new plugin provides a REST API to manage worklists and enables saving the worklists in the Orthanc database.
The Orthanc Explorer 2 plugin has been updated to version 1.10.1 to provide a user interface to create and browse worklists.
The Authorization plugin has also been updated to version 0.10.3 to better cope with these new features.
I have just added this feature request in the TODO.
If you wish to expedite the feature, do not hesitate to get in touch with https://orthanc.team to fund its development.
I donât think I explained myself well. The Worklist C-Find: parsed 0 worklists, found 94 match(es) is very helpful for customer support. It provides a quick way to see how many responses have been returned to the client.
At the moment, it is necessary to set the system log level to âverboseâ to see this message.
The result is that in addition to this log, every info log message is also printed. This makes it very difficult to see the worklist result.
Rather than the configuration enabling/disabling this log level, would it be possible to configure the log level that prints this?
ie: LogMatchedWorklistIds: "default" which if set prints this log as log(warn) so it appears in the system logs by default?
This would allow this log to be visible without having to change the log level of the system.
The other part that would make this invaluable for support would be to include the AET of the client that the query is from. For example:
Worklist C-Find: parsed 0 worklists, found 94 match(es) for client AE SOME_CLIENT_AET
This will make troubleshooting worklist âissuesâ far easier.
Iâm not in favor of allowing the users to play around with the log levels for each log entry - that would multiply the number of configuration entries and, in my opinion, such a log should not be at the warning level.
I think a general rule about logging is âlog as much as you can and then, use a tool to filter only the relevant informationâ.
However, I get your point and we usually do not have filtering tools either so I have just moved these 2 log entries to the DICOM category. Therefore, if you start with only --verbose-dicom, you wonât be flooded by other stuffs but, still, youâll get a few extra other logs like those:
I0123 12:17:51.183126 DICOM-SERVER CommandDispatcher.cpp:334] (dicom) Association Received from AET FINDSCU on IP 127.0.0.1
I0123 12:17:51.183868 DICOM-SERVER CommandDispatcher.cpp:675] (dicom) Association Acknowledged (Max Send PDV: 16372) to AET FINDSCU on IP 127.0.0.1
I0123 12:17:51.234279 DICOM-1 orthanc-worklists:/Plugin.cpp:335] (dicom) Worklist C-Find (from 'FINDSCU'): parsed 2 worklists, found 1 match(es)
I0123 12:17:51.234882 DICOM-1 CommandDispatcher.cpp:940] (dicom) Finishing association with AET FINDSCU on IP 127.0.0.1: DUL Peer Requested Release
I0123 12:17:51.234928 DICOM-1 CommandDispatcher.cpp:948] (dicom) Association Release with AET FINDSCU on IP 127.0.0.1