rhettbull/autofile

Mac command line app to automatically move or copy files based on metadata associated with the files. For example, file your photos based on EXIF metadata or use MP3 tags to file your music files.

autofile's Issues

Add filter(predicate) from osxphotos

Add new filter(x) filter from osxphotos

Document the plugin system

Update docs to show how to use the plugin system

Add {counter} template from osxphotos

Add a regex filter

A filter that could use regex to pull value(s) out of the filtered value would be very useful. E.g. pulling dates out of filenames (e.g. filename_2020_01_01.jpg)

Pull out the metadata plugins into separate mdinfo package

If the metadata plugins were pulled into a separate mdinfo package, could have a tool like this:

mdinfo "comment: {finder:comment}" "title: {exiftool:title}" --json file.jpg

and get something like this:

{
    "title": "Title",
    "comment": "My Comment"
}

Or

$ mdinfo {docx:author} file.docx
John Doe

Add caching to {pdf} template

Add per-document caching

Add --type to file types of files, regardless of extension.

Needs to inspect the type. Maybe use UTI?

Would then be possible to autofile "all images", etc.

{mdls} field sometimes fails tests

{mdls} is sometimes flaky -- add a retry to ensure the command was successful

Add slice, splice filters

slice(1:), slice(:4) -- similar to Python list slice, works on strings and lists
splice(start, deleteCount, item1) -- similar to javascript Array.splice() -- apply to both strings and list values

Pull out the MTL parser into a separate class so it can easily be reused

The MLT parser is used today in osxphotos, exif2findertags and autofile. I'll likely use it again. Rather than maintain 3 separate versions, the common parser engine could be pulled out into it's own package, mtlparser

class MTLParser:

    def __init__(self, get_field_value: Callable):
        ...

get_field_value would get passed the current field,subfield, default, options and return the field value so that could be implemented separately from the parser.

common things like punctuation and filters would be part of the parser class but could be overridden to implement custom filters, etc.

{pdf} appears to hang on some large PDF files

Add documentation to show how to use {exiftool} to read pdf metadata which works much better
Explore options other than pdfminer.six

Add {docx} field to read Word doc/docx metadata

Add --ignore-case for --regex

Add {today}, {now} datetime fields

Use mdinfo for the metadata parsing

See also #14, #10

Sanitize unicode output

Need to sanitize template output for unicode to filesystem conversion before creating paths

Combine --target and --directory

Instead of autofile --target ~/Music --directory "{audio:Artist}"

Just combine these to ~/Music/{audio:Artist}

If this is done, could possibly eliminate both --target and --directory and place the target as the last argument like mv or cp

Add {xattr} template field

Add {xattr} to read extended attributes

List/load specific plugins

Add ability to list available plugins and load only specific ones

Add {pdf} field to read PDF metadata

Add {tab} template

Change filters to match all, not any

Currently regex, glob, filter all match AND between each other (e.g. if specified, a glob AND a regex must match for a file to match) but match OR (any) if more than one of each specified. E.g. two --filter args will match True if either matches. This is not intuitive. Make all filters cumulative (e.g. all must match for a file to match)