Six Years Of Work And Rationale In A DIY Book Scanner Documented

[Daniel Reetz] spent six years working as a Disney engineer during the day and on his book scanner, the archivist at night. Some time last year, [Daniel] decided enough is enough, got married, and retired from the book scanner business. There’s a bit more to it than that, but before leaving he decided to dump, not just the design, but the entire rationale behind the design into a twenty-two thousand word document.

One of his big theses in this document, is his perceived failure of the open hardware movement. The licenses aren’t adequate, as they are based on copyright law that only applies to software. This makes it impossible to enforce in practice, which is why he released the entire design as public domain. He also feels that open hardware shares design, but not rationale. In his mind this is useless when encouraging improvement, and we tend to agree. In the end rationale is the useful thing, or the source code, behind a design that truly matters. So, putting his money time where his mouth is, he wrote down the rationale behind his scanner.

The rationale contains a lot of interesting things. At a first glance the book scanner almost seems a simple design, not the culmination of so much work. Though, once we began to read through his document, we began to understand why he made the choices he did. There’s so much to getting a good scan without destroying the book. For example, one needs a light that doesn’t lose any color information. It doesn’t have to be perfect, as the software can correct the white balance. However, it can’t lean too far away from the natural spectrum, it can’t be too bright, and it can’t be uneven, and it can’t be prohibitively expensive. A lot of thought went into the tent light design.

[Daniel]’s book scanners are immensely popular, and are being used all over the world. He’s certainly made an impact, and the community that formed around his project continues to grow without him. He made some interesting points, and if anything wrote a really good build and design log for the rest of us to learn from.

6 thoughts on “Six Years Of Work And Rationale In A DIY Book Scanner Documented

    1. Haven’t found a better OCR software than the TextBridge that came with a logitech pagescan color, although i haven’t tried many after scanning one book, which got wiped out when the HDD went bust. At that time (something 10+ years ago) i tried couple that were several years newer than the TextBridge, thinking newer must be better, but they were crap. TextBridge gave almost perfect text, didn’t take much to clean it up. Too bad about the HDD breaking.

      Who knows, maybe they are better now. Should be.

  1. I agree the only way to protect hardware from being patented is to put it in the public domain. And the only way to be able to improve on a design is to know the thoughts that went into it.
    I just lost two hours of my life reading about someone that is living theirs.
    Ironic.

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.