joeworkman / paperless Goto Github PK

OCR is not the best when parsing text... therefore when someone inserts a space into a condition, paperless will replace that with the regular expression \s*. The reason for this is that its very common for words to be concatenated or maybe get more than one space inserted between them.

Add a command line option to allow for more verbose output to the terminal

Howdy,

I have paperless "mostly" setup.

The --simulate command works fine, but then I get the following error when running "paperless create itinerary.pdf"

Processing rules...
Processing PDF pages...
Basing the date off the discovered string (2): 5August 2011
Saving /Users/jordanbrock/Dropbox/Action/itinerary.pdf to

• File: /Users/jordanbrock/Dropbox/Action/itinerary.pdf
• Service: finder
• Destination: /Users/jordanbrock/Dropbox/Documents/Processed
• Title: itinerary.pdf
• Date: 2011-08-05
• Tags:

There was an error processing the command.
error: undefined method `+' for nil:NilClass

I suspect that the error is occurring in lib/paperless/services/finder.rb between lines 24:29, but I haven't been able to confirm that. I can't work out what would be nil, because the output seems to have all the fields it needs.

Is there any way to run it in "verbose" mode, or a debug mode?

PS Thanks for a (what I hope will be) a fantastic service that pretty much fits my needs exactly.

When a rule generates a file with exactly the same name as a previous file, and moves it to the destination folder, it overwrites the existing file.

I, personally, would prefer a behaviour similar to that of MacOSX where it creates a new file with a (1) or a (2) or (x) after the filename.

Often, when the system can't parse the date, it just starts applying the filedate with the < match > variable and you end up with files being overwritten.

Cheers,

Jordan

Move to JSON files

You can do this with syslog

The base configuration is in the home folder. But if there is a config file in the same folder as in the file being processed, then use that one.

Possibly inherit the the home config/merge?

Right now the documentation is one huge README file. This needs to be broken up so that its less daunting to review.

Using the --rules_file flag will cause this error to be printed on the command line:

There was an error processing the command.
error: can't convert Symbol into Integer

This error is reproducible even when passing in the default rules file.

Example command:
paperless --rules_file=~/paperless.rules.yaml --simulate create ~/Desktop/AnyPDF.pdf

Running this same command without the --rules_file flag does not reproduce the issue.

The rules that are defined in the default rules file get displayed when you run the --help option. The reason for this is a limitation of the GLI framework used to create paperless.

The feature request on GLI davetron5000/gli#128

https://github.com/meh/ruby-tesseract-ocr
https://github.com/tesseract-ocr/

If a directory is passed to paperless, then recursively go through that directory and process all files found.