Uploaded image for project: 'XNAT'
  1. XNAT
  2. XNAT-6481

Decide on an approach for display of scan-level stored modality value

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.8.4
    • Component/s: None
    • Labels:
      None
    • Sprint:
    • Rank:
      0|0hzyea:r
    • Sprint:

      Description

      XNAT-6451 introduces the ability to enable a column in the session page's scan table for the modality of the scans. However, the session builder code has only been extracting this from the DICOM since 1.7.5, so for most data in existing XNATs, we're just adding a new blank column. Note that using the xsiType of the xnat:imageScanData object is not a good fallback as all sorts of things would just get called xnat:otherDicomScanData. I believe this would even happen for "common" modalities with less common SOP classes, so it would end up as a big mess. So, what's the solution? A few distinct choices come to mind:

      1. Do nothing. Just say: "deal with it, it should at least be present for new data".
      2. Help out a bit: provide a script to run that would scrape and populate the values correctly.
      3. Solve the problem: do it as an initializing task running in the background when starting tomcat.
      4. Something else I'm missing?

      These are presented in increasing effort, but also increasing ease of use for our users. Which do we pick?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              hortonw@wustl.edu Will Horton
              Reporter:
              moore.c@wustl.edu Charlie Moore
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: