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 could enforce xml_hash uniqueness before removing the formatting restrictions, but we could not (I was mistaken) enforce UUID uniqueness while the formatting restrictions are in place. That's because we need to identify cases where UUIDs collide but XML content is not identical, and then rewrite their UUIDs to append something like "DUPLICATE n" (which would violate the existing formatting restrictions).
The OpenRosa spec allows people to implement a "custom ID scheme" for
<instanceID>
, although it "must be a universally unique string identifying this specific submission".We don't currently support this:
kobocat/onadata/apps/logger/xform_instance_parser.py
Lines 72 to 93 in a8fbca5
Some people have uploaded submissions containing the likes of
This results in the
logger_instance.uuid
column diverging from the<instanceID>
in the XML.We should:
logger_instance
table;<instanceID>
stringThe text was updated successfully, but these errors were encountered: