this post was submitted on 17 Feb 2025
-39 points (11.8% liked)

Conservative

458 readers
332 users here now

A place to discuss pro-conservative stuff

  1. Be excellent to each other. Civility, No Racism, No Bigotry, No Slurs, No calls to violences, No namecalling, All that good stuff, follow lemm.ee's rules, follow the rules of your instance, etc.

  2. We are a Pro-Conservative forum. Posts must have a clear pro-conservative, or anti left-wing bias. We are interested in promoting conservatism and discussing things that might get ignored elsewhere. All sources are acceptable, however reputable sources with a reputation for factual reporting are preferred.

  3. Dissent is allowed in the comments, but try to be constructive; if you do not agree, then provide a reason which is backed up by references or a reasonable alternative interpretation of the provided facts. That means the left wing is welcome to state their opinions, but please keep it in good faith.

A polite request, not a rule, if you feel the need to report a comment, please don't reply to it.

founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 4 points 3 days ago (1 children)

Seems like all they need to do is have people go check off each one or check for fraud? Isn't there a dept for that?

[โ€“] [email protected] -5 points 3 days ago

Too early to tell. From my experience with data integrity issues first make the numbers manageable by linking data to another database (cross checking). If possible do a mass update then and what remains a red flag handle manually. This is a simplified version though, can be much more complicated. If some data is not in a database they can connect to or even worse is on paper, that can make it very labor intensive.

I have regularly coordinated and fixed data integrity issues myself. Worked for a large company that was often audited.