4 ms·
Having worked in the OCR world pretty much non stop for about a decade, i'd say its more just a case of there not being a lot of 101 yr olds, and there being a
by verelo 7y ago
Having worked in the OCR world pretty much non stop for about a decade, i'd say its more just a case of there not being a lot of 101 yr olds, and there being a lot of 1 year olds; the system is likely over-optimized for switching the digits to 20 v's 19 as it's more probable that the individual is 1 than 101. Really, when the confidence is low, or the data seems exceptional, it should be flagged for a manual review.
- 6510 7y agoThere are many more 101 year olds than 1 year olds doing their own administration.
- verelo 7y agoI'm not sure what the user experience is, my assumption is that it could be the individual or a parent scanning this data, so unless it was attached to a parent profile before entering the data, it's hard to know who is doing the administration. Having said that, if your assumption was correct ("The person is doing their own administration"), i'd agree with you.
- zenlot 7y agoIt's not hard. In EU settlement scheme application you have to tick a box if you're applying for yourself or someone else is doing that for you.
- verelo 7y agoThat makes sense, thanks for the context! I've been through Canadian immigration processes (I'm from Australia), but have no idea how the UK/EU process works.
- deleted 7y ago[deleted]
- baddox 7y agoI bet not that many more.
- 6510 7y agoinfinitely more! :P
- mjevans 7y agoAttaching a confidence / accuracy score to the data isn't a step that's commonly taken. However for qualifying user input this sounds like a great idea.
- verelo 7y agoI would be there at the time the data is scanned, but you're totally right. I imagine it could be added to a "metadata" or "notes" type section of the submission so the reviewer has the context the decision engine was using.
- jlangemeier 7y agoThis is making some very kind assumptions about basic administrative staff. For people that work in our industry, a confidence/accuracy score is something that's usually well understood, and is generally treated as an assessment of a single item in context with the whole. Once you get to the general public it's another matter entirely; for instance, look at how 538 was pilloried for their "30% chance to win the presidency for the current head of state," and how many times they've put out detailed information on how 30% =/= 0%. Your general person running review of the data (not the engineer hiding in the back office tuning the results, who should have access to the information) is going to treat most things above 50% as inherently true and anything below 50% as inherently false (within some margin of error, i.e. 50% +/- 5 points). It would be better to go the 'dumb' machine route of setting up some standard escalation flags; which looks like it may be what happened with this (albeit in a bad way), "person self filing and < 18 years of age; raise flag." The system being bad at differentiating 1919 & 2019 and then sending out an automated response seems more like a bad UX problem at this juncture, since it's something that could have been avoided with a quiet internal flagging instead of a loud external one.
- chinesempire 7y ago> there not being a lot of 101 yr olds, and there being a lot of 1 year olds handing their own papers to an employer of UK home office? I don't think so...
- mytailorisrich 7y agoI don't think it's due to OCR because although the Home Office's app does take a picture of the passport's ID page it then actually scans the passport's chip. So I don't really understand how it can misinterpret the birth date unless someone really stupidly coded the system to keep only the last 2 digits of year and then try to guess what it really was later...
- Aaargh20318 7y agoThe chip in the passport usually only contains the last 2 digits of the year or birth.
- mytailorisrich 7y agoAh the stupid idea may not be where I assumed it was, then...