You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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;
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.
The text was updated successfully, but these errors were encountered: