all files in awtfdb are content-addressed and can be loosely ordered in time of inclusion by their internal hash ids, however this is not useful for collections of files that have an inherent order to them.
boorus already have the concept of pools to put multiple files together in an order, we can steal the idea.
here's the proposed UI:
$ atags pool create "Name Of My Epic Pool"
pool id: 1351
$ ainclude -p 1351 file1 file2 file3
$ atags pool fetch 1351
file1
file2
file3
$ atags pool search epic
Name Of My Epic Pool
all files in awtfdb are content-addressed and can be loosely ordered in time of inclusion by their internal hash ids, however this is not useful for collections of files that have an inherent order to them.
boorus already have the concept of pools to put multiple files together in an order, we can steal the idea.
here's the proposed UI: