Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

image capture keybinding and configs #20

Open
linuxcaffe opened this issue Feb 6, 2017 · 2 comments
Open

image capture keybinding and configs #20

linuxcaffe opened this issue Feb 6, 2017 · 2 comments

Comments

@linuxcaffe
Copy link

linuxcaffe commented Feb 6, 2017

Let\s say you wanted to process a big box of receipts AND you wanted to scan each one as you go. This feature request is for support of capture, naming and taming of image files related to transactions.

Capture support could take the form of a keybinding that invokes a user-definable script, that;

  • triggers the image-capture/ scan of the source document
  • uses pre-defined locations (config file) for both image file(s) and physical document(s)
  • produces files named like $DATE_$DESCRIPTION.$EXT
  • adds transaction comment tags like ' ; scan: $FILE_LOCATION/$DATE_$DESCRIPTION.$EXT'
  • adds transaction comment tags like ' ; document: $DOC_LOCATION # tracking the source paper file

How exactly webcam/ smartphone/ scanners are triggered and what process the image files undergo, is beyond the scope of this suggestion. This issue is really more of a discussion-starter.

@hpdeifel
Copy link
Owner

hpdeifel commented Feb 8, 2017

This is very specific. I think a reasonable general approach would be to pipe the current transaction to a user-definable script and read the modified transaction back again. This would allow to do arbitrary transformations on the transaction, including the addition of tags.

simonmichael/hledger#501 could be useful for this.

@linuxcaffe
Copy link
Author

well.. yeah!
;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants