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
if data is there, check with site that the PASAT record doesn't belong to an actual ID, otherwise GOTO 4
if it does belong to an actual ID, rename the processed file, upload it under a valid Import ID, and add an exception to special_cases::harvester::ignore_processed_paths for the original NOID name; otherwise GOTO 4
if the data isn't there, or it is a confirmed legit test case, close the issue (and maybe remove the processed file).
See e.g. sibis-platform/ncanda-operations#8145.
The resolution steps are unwieldy and require filesystem manipulation. But we already have a mechanism for sites to fix incorrectly entered subject ID - they just need to do that in the Import project! Therefore, perhaps we shoud allow for that.
The text was updated successfully, but these errors were encountered:
Right now,
harvester
raises an error whenever the parsed PASAT DB results in any ID-less output (i.e. files that start withNOID
ornan
). (This behavior is from db0cf2f in Feb 2018.) The SOP for the ID-less PASAT case is:special_cases::harvester::ignore_processed_paths
for the original NOID name; otherwise GOTO 4See e.g. sibis-platform/ncanda-operations#8145.
The resolution steps are unwieldy and require filesystem manipulation. But we already have a mechanism for sites to fix incorrectly entered subject ID - they just need to do that in the Import project! Therefore, perhaps we shoud allow for that.
The text was updated successfully, but these errors were encountered: