Closed huy-d-nguyen closed 2 years ago
cc @rajivsinclair
Hi @huy-d-nguyen, I will take a look at it this afternoon and update this issue as soon as I know what's going on.
Hi everyone: that uid was in the personnel table when I last updated the documents table on Dec. 21 (this is the snapshot I used). I will run an update of the extraction/matching code this weekend, so only uid's that are in the latest snapshot are included. I had previously thought I would only need to run updates when I processed additional documents or made other changes, I did not realize that created uid's could change or disappear. I'll update my workflows accordingly.
re-ran the match and pushed it, let me know if you're still seeing this problem.
I think this solved the immediate issue, I'm closing this in favor of #16, which should address this going forward
Hi @tarakc02, we have checked the
documents
table in WRGL hub and it looks like some officers in thedocuments
table do not exist inpersonel
table. For example, the document with thedocid
3c82a768 has thematched_uid
deda497a28be3d134292921ac546b3c4 but we cannot find that one in thepersonnel
table. Can you help us check it again?