You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we use the DirectoryStorageService to store DICOM files. As directory structure and filenameTag we use something similar to "DicomTag/Date/SOPInstanceUID". The content of the DicomTag is user-defined and therefore error-prone. (incoming DicomTag=A, an hour later the corrected DicomTag=B arrives, the SOPInstanceUID is identical).
Is it possible to add an optional feature, which deletes all files with the same filenameTag (=SOPInstanceUID in our case), so that users can correct their mistakes without user interaction? Something like a Map which maps filenameTag to Path and ensures that the old file (in a different directory) is removed, before the new one is written?
What's the best approach to implement this features? Would it be possible to add such a feature to the upstream CTP repository?
The text was updated successfully, but these errors were encountered:
Hi,
we use the DirectoryStorageService to store DICOM files. As directory structure and filenameTag we use something similar to "DicomTag/Date/SOPInstanceUID". The content of the DicomTag is user-defined and therefore error-prone. (incoming DicomTag=A, an hour later the corrected DicomTag=B arrives, the SOPInstanceUID is identical).
Is it possible to add an optional feature, which deletes all files with the same filenameTag (=SOPInstanceUID in our case), so that users can correct their mistakes without user interaction? Something like a Map which maps filenameTag to Path and ensures that the old file (in a different directory) is removed, before the new one is written?
What's the best approach to implement this features? Would it be possible to add such a feature to the upstream CTP repository?
The text was updated successfully, but these errors were encountered: