Fieldreport ID and Dates

The dates may have been set in a non-chronological / illogical way by migration / import scripts due to misunderstanding of the meaning of the dates / no Mine Action knowledge.

fieldreport table Database column fieldreport_localid dateofreport reportreceiveddate reportcompleteddate reportverifieddate verifiedby dataentrydate GUI name Form ID Date of Information Data Entry Date Submitted Date Approved Date Approved by Last updated date GUI GUI Action Entered in DEF (either using button or typing) Entered in DEF (Age of Information) (there are no checks in the code that this date is before the other) Clicking on Save (might be NULL if DEF is imported) Clicking on Submit (might be NULL if button is not clicked) Clicking on Approve (bug in 5.x could cause NULL) Clicking on Approve (bug in 5.x could caused NULL) e.g. switching template Example DEF-456 2011-09-11 oldest 2011-10-04 2011-10-05 2011-10-06 newest emma 2014-06-19 Importance Mandatory Mandatory Good to have Not necessary (depends on permission configuration) Should have Should have Do not use for UPDATE* Error Reconciliation tab will be empty Not Possible to Unapprove Should have been fixed in the upgrade Should have been fixed in the upgrade * Never ever use fieldreport.dataentrydate for updating anyone of the above because that is Last Updated date which e.g. changes when the template is switched. Read more Field General information MySQL queries PostgreSQL queries Form ID Upgrade from 5.08.04 section Missing Local ID MySQL Missing Local ID PGSQL Date of Information Upgrade from 5.08.04 section Missing Date of Information MySQL Missing Date of Information PGSQL Approval Information Upgrade from 5.08.04 section Missing approval information MySQL Missing approval information PGSQL Template:NavBox Hub