Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you think you could build...

Oddly enough, The Internet Archive did a substantial portion of just that: https://openlibrary.org/dev/docs/bookreader

It's used by numerous other organizations as well:

https://openlibrary.org/dev/docs/bookreader#users



I don't think you understand what USPTO need, it's not just a scanning system, it's an entire workflow system.


I didn't claim TIA created everything the USPTO requires.

I did point out that they created precisely the element you indicated was challenging: accomodating different document types from different sources.

Given that the USPTO's system is likely based on electronic filings at this point, even the scan-and-present aspects of the BookReader solution are likely more than is required.

Another salient point is that by breaking the problem into discrete components, you're more likely to come up with a viable solution, or at least significant portions of one.

And I've worked on a number of systems (FDA clinical information systems) which address a great deal of your other feature points. Suffice to say: such systems do in fact exist.

They do, in fairness, take more than a couple of days to assemble.


But workflow systems can't do shit with scanned documents other than route them via human instructions.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: