#1293 closed defect (fixed)

INCA import is importing to incorrect cases in some situations

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: critical Milestone: Reggie v4.31
Component: net.sf.basedb.reggie Keywords:
Cc:

Description

A case in our database typically have LEFT or RIGHT laterality but it can also be missing. The INCA importer doesn't consider the missing case correctly, but handles anything that is not LEFT as a RIGHT case.

If the INCA file contains a single RIGHT case this will be imported to a case with missing laterality.

If the INCA file contains both a LEFT and a RIGHT case, and our database has two cases with RIGHT and missing laterality, the data for the LEFT case will not be imported and the data for the RIGHT case may end up on either the cases (depending on the order of cases as they are returned by Postgres).

In both cases the importer will not report any mismatch between the INCA and our database.

Existing cases need to be fixed manually:

  1. Most cases are first type (single-case) and if the registered dates, PAD, etc can be matched we should update the laterality to RIGHT so that it matches the INCA data.
  2. Remaining cases need to be cleared of INCA data.

Change History (1)

comment:1 Changed 17 months ago by Nicklas Nordborg

Resolution: fixed
Status: newclosed

In 6124:

Fixes #1293: INCA import is importing to incorrect cases in some situations

Note: See TracTickets for help on using tickets.