I have been struggling with making everything digital for years now, and there are stacks of photos and thick albums that remain uncharted territory. Every once in awhile I sit down and scan in an album.

Trouble is, unless you do the whole job at once, it’s pretty easy to lose track of where you have already been. And if that’s not bad enough, we always bought double prints—they didn’t cost much more, and we could give some away. Now how do I know if I have scanned the long-lost twins of some photos that are already on my computer? That’s a problem for another day.

Here’s how I make sure I don’t scan the same single photo twice:

That’s right, I leave breadcrumbs in the form of little dots on the back of each one.

Such a simple thing, but it saves me from a lot of head scratching and wasted time scanning the same stuff over and over.

Scanned photographs are an entirely different brew. They typically represent events from the distant past, and scanner software EXIF data is hit or miss.

I looked for commercial software to handle a few special cases of EXIF data troubles, but came up empty handed. So I wrote a few useful AppleScript droplets that do these tasks quite nicely, and I will share them here.

Warning!

These scripts use jhead to manipulate and rewrite your JPEG files!

Don’t be a fool. Experiment first with a safe set of throwaway JPEGs. And never use these tools on original files; always keep a backup.

Prerequisite

All of these scripts depend on a fine piece of free software called jhead written by Matthias Wandel.

Installation is not difficult, but it does involve the command line.

• Go to the jhead site
• Scroll down to the Releases section and look for Pre-built OS-X Intel executable
• Right click on the jhead link on that row and choose Save Linked File to “Downloads”

At this point, I found that jhead was saved as jhead.txt. Oh well. We needed to do some command-line magic anyway.

• Open a terminal window and enter the following:

These lines do the following:

• Lines 1 and 2 navigate to the Downloads directory and remove the “.txt” from the name
• Line 3 makes the file executable by everyone on your Mac
• Line 4 places the file in a public area where everyone on your Mac can see it (you will be prompted for your password)

Stripping All EXIF Data

Sometimes I receive files that have corrupt EXIF data. I had a large quantity of scanned files in my collection that claimed to be scanned some time in 2038, while others insisted that they had been around since 1901. Neither situation is good, and I found that standard EXIF editing tools may fail to change these corrupt EXIF sections.

The answer is to blow away the EXIF data.

Download: Strip EXIF

This zip file contains a compiled AppleScript application. You can unzip it and place the application on your desktop. Safari will probably unzip it for you when you click the link.

To be safe, open AppleScript Editor and use it to open the Strip EXIF app to see its magic.

Now you can drop any number of JPEG files onto the Strip EXIF app and it will kindly eviscerate each JPEG, removing all traces of EXIF data.

Adding Basic EXIF Data to a vanilla JPEG

Some tools create JPEG files without EXIF date and time information within. This is typically the hallmark of photo manipulation software and dodgy scanner software. And if you happened to use the Strip EXIF app to rip out a bad EXIF block, then you will want to replace it with a proper data block so that you can still use camera date and timestamps.

Download: Add Basic EXIF

Again, unzip the file, place the app on your desktop, and then drop any number of JPEG files onto Add Basic EXIF.

The app will set the EXIF date to the file creation timestamp.

Spreading EXIF Timestamps

This is the real reason why I wrote these scripts. I couldn’t find a satisfactory tool on the market that would allow me to automatically spread out the shooting times for a series of images.

Why would anyone want to do this? Because some processes give you fifty JPEG files all with the exact same creation time and exact same shooting time. I like to use file renaming tools to incorporate the shooting time in the filename, so that files sort by chronological order. This doesn’t work if all of the timestamps are the same.

So I wrote a little app that adjusts the first photo by one minute, the second by two minutes, and so on. If there are fifty photos, then the last one will have its shooting time adjusted by fifty minutes.

The result is a series of photos/scans that have different timestamps.

Download: Spread EXIF Timestamps

Again, please look at the short program before you run it.

Closing Thoughts

I hope that my favorite tool implements these tricks soon (A Better Finder Attributes, I’m looking at you!), but until then, I will be dropping my files onto these three little droplets.

The jhead tool is so versatile that I will probably end up with a whole slew of similar droplets that will do all kinds of spiffy stuff. Nevertheless, I would rather the commercial products already provided these features. Not everyone likes dipping into AppleScript and the command line!

My situation is worse—both my wife and I are musicians, to one degree or another. Throw in the fact that she is a music teacher and you can imagine just how many pages of sheet music there are filling bins and flexing cheap shelving in my house.

What do I have and Where is it?

The biggest problem we face is knowing what we have and where it is. I have hundreds and hundreds of pages of classical and jazz guitar sheet music, but if I need to find Villalobos’ Choros no. 1, where do I look?

Shortly after I bought my ScanSnap, I began scanning in all of my sheet music (I have left much of my wife’s collection untouched—I’m sure you’ll understand). In most cases, I simply hacked the spine off of the original book and fed the sheets through the scanner. Now, I have less paper in the house and my music is searchable.

In most cases I didn’t bother to run OCR on the documents since there is little in the way of printed words on most sheet music that is worth indexing. I did take care to name the files well.

If you ever hope to find your music on your computer, make sure you include at least the composer/artist and song title in the file name.

Is this really cutting down on paper?

Whenever I find what I’m looking for I might play it directly off of the computer screen, but it is more likely that I’ll print it out. Doesn’t this kind of negate the idea of removing paper from my home? Not really. Think about it—most sheet music is never played. We have books with hundreds of songs in them and we play only  a handful. That’s just the way it is.

The fact that I print out five or ten pages in a month does not negate the many hundreds of pages that were scanned and then recycled.

Great for Music Lessons

I started taking jazz lessons again a month or two back, and my teacher gave me some lead sheets, with all kinds of useful annotations on them. As soon as I was home, I scanned those babies in, so I would not risk losing the valuable information. I also went through all of my notes from prior lessons and scanned them in as well. These kinds of things are precisely the sorts of paper that tend to get lost in some mismash of unsorted music.

Now, I can type in “Four” in my favorite PDF library application and find the lead sheet for Miles Davis’ Four.

Maybe you don’t have that many notebooks full of music lesson notes, but when you have been trying (poorly) to learn for as many years as I have, those notebooks begin to proliferate. Just scan them all in, give them some good filenames, add some keywords to help, and you’re in business.

What about copyright?

It seems that the jury is still out on digitizing works you own. There’s one fellow who made a right awesome device for scanning in textbooks in minutes, by photographing the pages. That guy’s machine has spurred much debate about whether or not you have the right to digitize your own stuff.

On the one hand, you bought the book and paid for it, so it would seem that fair use covers this; on the other hand, publishers are eager to monetize digital media, reselling the same works to you if they can.

So, is Daniel Reetz’s butt-kickin’ book scanner legal?

That would depend on who you talk to, says Pamela Samuelson, a professor at University of California at Berkeley, who specializes in digital-copyright law. Trade publishers are almost certain to cry copyright infringement, she says, though it may not necessarily be the case.

Google was recently forced to pay $125 million to settle with angry book publishers and authors who claimed copyright infringement as a result of the search giant’s book-scanning project.

But not so individual users who already own the book, says Samuelson. If you scan a book that you have already purchased, it is “fine, and fair use,” she says. “Personal-use copying should be deemed to be fair, unless there is a demonstrable showing of harm to the market for the copyright at work,” says Samuelson.

(Source: wired.com)

Here’s another take on this:

Question

I bought a book for school, can I make a copy of the book for my own use to write on so I don’t write in the book and can get my money back when I return the book to the campus store.

Accepted Answer

You have the right to make a copy of the book you purchased as long as you are using the copy for your personal use. The copyright laws merely prevent you from making copies to sell or distribute.

(Source: justanswer.com)

Of course, if you go passing your PDF documents around to all of your friends, all bets are off.

Final thoughts
Music is a hobby that seems to accumulate great stacks of paper, but these music sheets are peculiar in that you only need one or two out of every hundred. Why not digitize the whole lot and keep those book shelves from sagging?

Among other things he discusses options for prioritizing and cutting down on the total volume of stuff you plan on keeping, digital or otherwise.

“Backup, backup, backup” made number four on his list.

And finally, he provides a few notes on some helpful free organizing software. I think I’m going to check out that Know Your Stuff application he mentioned.

Five Tips to Paperless Finances (moneytalksnews.com)

As it turns out, my original script does not work in Snow Leopard, and I promised that I would one day clean up and publish my new and improved version.

Chris posted a comment today as a gentle reminder, so here is the new and improved version without further delay…

The Details

Unfortunately, Snow Leopard came around and caused some indigestion. For starters, the ScanSnap Manager didn’t work correctly and Abbyy Finereader would not process anything made by the ScanSnap. A couple of months later they got everything straightened out and delivered new versions of each product.

The new version of the Abbyy Finereader product does not play well with my original script.

Since I cannot do without this important functionality, I rolled up my sleeves and rewrote most of the script. The new version works in Snow Leopard quite nicely with one small annoyance: you really don’t want to try to use the machine for anything other than scanning or OCR while it is going because the new Finereader version keeps bouncing the darned icon all the time it is running and that is quite annoying to watch.

Fortunately, I really don’t need to use my machine for anything else while it is chewing on the docs; I just wanted to be able to continue scanning at the same time!

Note: Before going forward, note that you will need to upgrade the ScanSnap Manager and Abbyy Finereader to the Snow Leopard versions first! Get the files here.

Here is a link to the new script…

And here’s the code itself:

Installation

• Use the Script Editor to save this script as Run OCR on New Folder Items under User Home/Library/Scripts/Folder Action Scripts
  You may have to create the Folder Action Scripts folder.
• Now open a Finder window and navigate to the parent folder of your scanned documents folder.
• Right click (control-click) the scanned documents folder and choose Folder Actions Setup…
• At this point if folder actions are not enabled, you will likely have to enable them and add the script manually.
  • Check Enable Folder Actions
  • Use the “+” buttons on the left and right sides to add the scan folder and then this script.
• Otherwise, a list of scripts will come up. Choose this script from the Choose a Script to Attach dialog.
• Close all windows.

That’s it! The script will be invoked automatically every time a new file appears in your scanned documents folder.

Please let me know if you have any ideas that can improve this script. I’m not an AppleScript guru, so someone might just know how to keep that annoying Finereader icon from jumping.

[UPDATE: I spoke too soon—they only delivered half of the goods. See below.]

[UPDATE 2: Hurray! It's fixed! The birds are chirping and the sun is shining and life is good!]

When Snow Leopard came out back in August, I ordered my copy the first week and was so excited that I installed it the day it arrived. My joy was short-lived, however: the most important software package I use did not work!

I depend greatly on the OCR capabilities of the ABBYY FineReader software that comes with the ScanSnap scanners, and this was one of the many pieces of software that did not smoothly transition to Snow Leopard. I could scan documents, with limited functionality, but the OCR feature did not work.

Now that Fujitsu has released their official update, I will probably be installing Snow Leopard tomorrow evening. Now, do I do an upgrade or a full install? Hmmmm…

UPDATE

Well, they only delivered half of the goods.

I was reading through the seven-step process for updating the ScanSnap drivers and I arrived at step seven:

Step 7: The download for FineReader for ScanSnap update to Snow Leopard will be hosted by ABBYY but is not yet available. If you have already subscribed to be notified by Fujitsu regarding the Snow Leopard updates, an email will be sent to you when it is posted.

How displeasing. The only thing I really cared about was getting the OCR to work, and apparently Abbyy has not yet delivered their part (How hard can it be to update the part in your code that says “If the PDF metadata doesn’t match X then the document isn’t a ScanSnap doc” ?).

UPDATE 2

Instead of making us wait another month or two, ABBYY has delivered their patch in record time . I quickly installed the update and tested my ScanSnap script…

There are a few kinks to work out, but it is pretty clear that I will have my same old workflow AppleScript folder action up and running in short order. I will post the newer script as soon as I have it running properly.

And, as a side note, I had already purchased PDFpen from SmileOnMyMac as a backup plan. Their tool incorporates the OmniPage OCR engine, an engine that rivals that of ABBYY. My script was already running with PDFpen, but there were some issues with tables in documents that I forwarded on to SmileOnMyMac. One of these days I’ll post my scripts for PDFpen.

I trust my digital life to PDF. Almost everything I scan and most documents I write eventually end up squirreled away somewhere as PDF documents.

Have you ever considered just how portable those documents really are?

What’s wrong with PDF?

It seems strange to question the portability of these files, doesn’t it?

For the past ten or fifteen years Adobe has been providing Acrobat Reader and singing the wonders of their new universal document format. And it seemed to be all that, too—regardless of the audible groan we give when Acrobat launches after we click a link, isn’t it amazing that we can download press-ready copies of our income tax forms, that are guaranteed to look exactly the same when you print them as when I print them? Read on to see what dangers lurk within.

What’s the Problem?

In order to understand the nature of the PDF portability issues, one need only look as far as the web browser for an analogy. Consider how the web browser went from a barebones tool that could display a simple language, HTML, in a neutral way, fitting the web content onto each user’s screen, to a memory hogging behemoth that is an integral part of your operating system. It didn’t happen all at one; it has been death by a thousand cuts.

Mirroring the evolution of web browsers, the PDF document standard has adapted over the years to include many bells and whistles such as embedded audio, video, and JavaScript. It is these features that chip away at the core purpose and raison d’être of the PDF standard.

An example: Font Issues

A simple example of the weakness of these extended PDF features is the humble text font. When your application generates a PDF document, there is the option of using 14 standard PDF fonts, local machine fonts, or embedded TTF or Postscript fonts.

There are 14 standard fonts that should be available by default in each PDF reader. These fonts are Courier, Courier Bold, Courier Italic (Oblique), Courier Bold and Italic, Helvetica, Helvetica Bold, Helvetica Italic (Oblique), Helvetica Bold and Italic, Times Roman, Times Roman Bold, Times Roman Italic, Times Roman Bold and Italic, Symbol and ZapfDingBats® (source)

Guess what happens when you set your document in Mona Lisa Solid ITC and then print to PDF and send to all of your colleagues? Does your friend’s machine have a copy of this font? Maybe, and maybe not.

As I was writing this, I planned on putting together a cute demo by saving a document set in Mona Lisa Solid ITC in PDF from my Mac and then opening it on a PC. Much to my surprise (and delight), I found that the default “Print to PDF” functionality on my Mac does, in fact, embed the font within the document.

Regardless, if you have always just trusted that the fonts would be identical across platforms, you could get quite a surprise when your friend tries to print your beautiful document.

PDF/A Standard

Some time back, Adobe recognized the need for a more tightly controlled standard, for creating really portable documents, instead of mere portable documents. This standard, dating from 2005, is referred to as PDF/A, where the A stands for Archive.

A key element to … reproducibility is the requirement for PDF/A documents to be 100 % self-contained. All of the information necessary for displaying the document in the same manner every time is embedded in the file. This includes, but is not limited to, all content (text, raster images and vector graphics), fonts, and color information. A PDF/A document is not permitted to be reliant on information from external sources (e.g. font programs and hyperlinks). (Wikipedia)

Basically PDF/A forbids all of the flashy stuff and sticks to the basics: good solid document rendering.

Banned features include:

• Audio and Video
• JavaScript
• Encryption
• Nonstandard metadata
• Transparent images

In addition to the loss of several features, PDF/A documents can be somewhat larger, due to the embedded fonts, and they might have rendering issues with images that depend on transparency.

With all that, it still sounds like an enticing concept. Many PDF tools speak fluent PDF/A. Check out your own toolkit and see if you can future-proof your documents a little more

Here’s more on PDF/A documents

Long-term digital archiving with PDF/A (The PDF Blog)
PDF/A (Wikipedia)
PDF/A – A new Standard for Long-Term Archiving (PDF/A Competence Center)

I had promised that once I cleaned up the embarrassing bits of code I would post a perfect polished version here, but such promises are rarely fulfilled. A reader posted a comment asking for that source code, so I will post it here in its current state. The truth is, I have been using this script for months and, though it has some quirks, it works fine.

So this post is about Macintosh, AppleScript, and the ScanSnap-to-FineReader workflow. If these don’t interest you, better move on.

Update: The script on this page works only with Leopard (10.5). Get the Snow Leopard version here

The Original Problem

The Fujitsu ScanSnap S510m, my workhorse scanner, was designed to scan documents quickly and generate PDF files—this it does flawlessly. In order to provide OCR support, they have shipped a special version of FineReader, called FineReader for ScanSnap. The standard OCR configuration is to chain the output of the scanner to the FineReader program.

The problem is that this forces scanning and OCR to run in lockstep: you scan a document, you wait for OCR, and then you scan another document.

My desire was to write a simple AppleScript that would detach the “Scan a Document” process from the “OCR” process. By using this script, I can scan documents at whatever rate pleases me, and the OCR engine will chunk along at its own pace, consuming my scanned documents and producing OCR documents.

My Approach

I really looked hard at the OCR application, trying to find AppleScript hooks or special command line switches that might allow me to control it better. Sadly, it was not designed to be scriptable. The only thing I could do is call the FineReader application with a source file.

Given this limitation, I considered writing a script that would look at a particular folder, identifying new files as they appear and passing them on to FineReader.

Fortunately, AppleScript provides this kind of functionality with little effort in the form of Folder Actions. Perhaps the best way to see these in action (and try it out) is to see this post on Exploring the power of Folder Actions.

In order to achieve my goals, I did the following:

• Created a folder called “Pending Documents”
• Wrote the script to find the oldest-unprocessed-file and call FineReader with it
• Attached the script to the folder as a Folder Action

The Script

Let’s jump right in to the AppleScript. Download the script here.

Installation

• Use the Script Editor to save this script as Run OCR on New Folder Items under User Home/Library/Scripts/Folder Action ScriptsYou may have to create the Folder Action Scripts folder.
• Now open a Finder window, control-click and choose More / Configure Folder Actions…
• Check the Enable Folder Actions checkbox, if not checked
• Click the “+” in the bottom left
• Select a folder and click Open
• Choose the script Run OCR on New Folder Items and click Attach

Picky Details

As you can see in the source code, there were several issues to address:

• I had to make sure the script didn’t step on itself. If FineReader was running, I would wait until it was ready before processing.
• The script needed to determine which files had been processed already. This was handled fairly trivially by looking for a matching file with the processed by FineReader.pdf suffix. In other words, if I was looking at Scan001.pdf, I would see if there was a matching Scan001 processed by FineReader.pdf file.
• Part of checking for a source file’s “buddy” was stripping off the PDF suffix. This was done in a hackish way by using a one-line shell script, at lines 106-107.
• I thought it was important to verify that the source file was, indeed, a ScanSnap file—the FineReader will not process other PDF documents. This was done at lines 117-121 by looking at the Spotlight metadata for the Creator of the source file. That took some more shell scripting (133-154).
• The actual work was done by a single line, line 63.

The real work was fairly simple, while the bulk of the code was needed to polish pesky little details. Isn’t that the way code development often is?

If anyone has any improvements on my script, please let me know!

I guess there must have been a time when we all lived simpler lives and didn’t care a whit about who was grubbing through our trash. Honestly, as I am shredding the week’s load of pre approved credit card offers and the like, I imagine I could just be bold and tear them all in half and toss them, unshredded (gasp!).

But anyone who is packing serious scanning hardware should also be packing serious shredding hardware. It may not matter if another Capital One offer slips into the trash intact, but there’s no way I’m going to dispose of old tax records or medical records without rendering them completely useless to the enemy.

Here is my own short list of things to look for when you are buying a new shredder.

A Serious Tool for a Serious Job

There are lots of sites out there that have buying recommendations for shredders, and once you wade through all of the commercial spam sites and get to some good articles, they offer pretty even coverage of the different features to look for. This is where my own opinion differs from theirs.

Don’t waste your time with some namby-pamby little shredder that sits on your desk and shreds three thin sheets of rice paper at a time. If you are serious about reclaiming your home from paper, you need something that can wolf down loads of documents, paperclips and all.

This is my most firm recommendation: go for the most solid machine you can afford. Otherwise you will be buying a new one next year.

I don’t know about you, but I have been through three of the darned things. I tried the relatively cheap one and killed it within six months by overheating it. I then bought a heavy duty model that served five very good years before expiring with some mysterious illness. My current one is a somewhat smaller model, selected specifically for its reduced size by my wife.

Good Capacity

Make sure that your shredder is rated at a minimum of 12 sheets at a time. This way, you can insert just about any stapled document and be confident that it is not going to choke the machine.

See if the device can eat both credit cards and CDs. Both of these features are pleasing to have.

Don’t bother with those silly things that have narrow slots that require you to fold the paper like a letter before insertion. Do you really want to have to fold five hundred sheets of paper like that?

Solid Construction

This is a fairly subjective assessment. Look at several of the machines and see which one is built better. Chances are that the el cheapo version will have plastic gearing and other brittle parts. If you can look inside (often from the underside) look at the gears to make sure they are metal.

Emptying the Basket

Imagine yourself emptying the basket. You will be doing this dozens of times.

Many machines have a built-in trash can that flips out from the front, leaving the rest of the machine standing. I like this feature and look for it. You should try removing and replacing the basket a few times to see if it is a fiddly task and if there are little cheap plastic tabs that are going to snap off after two weeks.

One kind of shredder sits on top of its basket—you must lift it off the basket entirely in order to empty the waste. Pick it up a few times. Do you mind lifting the weight? I know that my wife didn’t want to have to lift the shredder every time she emptied it, so we skipped past this style.

Another point to consider is whether those special shredder bags will fit in the basket of your machine. As far as I know, all shredders have some sort of mechanical interlock between the machine and the basket that shuts off the device if it is not on the basket. This is usually achieved by some little tab on the basket that slides in some slot, closing a switch. If you use a shredder bag, make sure you can do so without interfering with this safety mechanism.

Basket Size

A small amount of paper becomes a large volume of confetti. If you don’t mind having a larger unit taking up space in the corner, then go for the one with the bigger basket. Trust me, you are going to be lazy and let it get filled up anyway—why not at least have a longer delay before you are forced to empty it?

Consider a tall basket rather than a short basket. Once the top of the confetti reaches the underside of the shredder mechanism, it is possible for the blades to draw in the already shredded paper and come to a grinding standstill that may not be easy to recover from.

Strip vs. Crosscut

I don’t know just how much to worry about this one. Everyone says to get a crosscut shredder, so that it tears your paper into little tiny diamonds, but they still are manufacturing strip shredders. The fact of the matter is, strip shredders can handle a heavier load since they aren’t chopping the paper to little tiny bits.

Once the paper is shredded into skinny strips, I’m pretty happy with it. Unless you are some high profile person with valuable secrets, why get worked up about it? Do you really think that someone is going to piece together all of those little strips and read about your colonoscopy three years ago?

I’m not saying that it doesn’t matter at all; if you want the added security of crosscut, then go for it. I’m saying that this can be a lower priority than some of the other criteria. Don’t automatically rule out a solid performer because it is a strip shredder.

Other Features

They all come with various other nifty features such as automatically detecting inserted sheets and automatic reversal when there is a jam. One nice feature is an automatic cutoff when the unit has worked too hard. I think all of them do this, but some do it ungracefully by dying forever, while others tout a graceful cutoff.

Think Before You Shred

You don’t get a second chance. Make sure whatever you shred has been electronically captured and backed up. Is there an electronic copy safely in two places?

If you do not have an electronic copy, then make absolutely certain that you intend to destroy the document forever—this is exactly what you are doing.

Summary

I believe in buying the best tools I can afford for the job, and this holds especially true for shredders. It is a serious machine that has migrated from government/military circles, to offices, and finally to the home. Pick a solid performer that can chew through whatever you throw at it.

A final thought: Don’t buy one sight unseen. These devices must be handled in person to be truly appreciated!

“How a lifestyle experiment and a disaster made me realize the value of turning atoms into bits” — Mike Elgin

A couple of months back, Mike Elgin of Computerworld posted an article on his foray into the paperless world: Paperless office? Ha! How about a paperless life?

In this followup article, he considers how lifestyle changes and the raging wildfires closing in on his city have made it clear to him that it is critical to protect whatever can be easily preserved in digital form.

Mike gives a sound strategy, starting off with a fast pass at just getting it digitized with little regard for perfection, followed by more focused efforts.

He pointed out how some objects just aren’t as important as the memories that they represent, illustrating this with a photograph of his son’s martial arts trophies that he has since donated to various organizations.

Mike makes it very clear that backups are mandatory. My kind of guy!

Here’s the whole article: Why you should digitize ‘everything’ (Computerworld.com)