tag sources

[lun-4]

this is related to #23, because this provides a good solution to the "how to remove the parent relationship but in a cohesive manner (by not deleting tags that didn't get added by the relationship)".

this also helps me on separating tag data, from manual things i have put, to tools i have made to insert tags, could be useful for training DeepDanbooru datasets!

the manual source always comes by default.

$ atags source list
0 manual

$ atags source create "deepdanbooru"

$ atags source list
0 manual
1 deepdanbooru

$ ainclude -s 1 -t this_tag -s 0 -t that_tag myfile

$ als --full myfile
myfile 'this_tag' (deepdanbooru) 'that_tag' (manual)

[lun-4]

questions about this system:

• hardcoding ids is bad, there should be only id 0 as a hardcoded thing
• how to express tag parents here, actually?
  • one possible answer is create a source for parents (id 1), and if id is 1, then a new field, parent_source_id will be set.
  • the obvious drawback is that this highlights how un-extensible this is if i want to add more default functionality (say, after i implement tag sources, i want to create a new default one?)
  • one possible answer is to make tag sources a "random" id instead of sequential, hardcode the random ids, and order them by an created_at column (or rowid, to be honest...)

[lun-4]

better idea: tag sources get types. if its an internal source (like parenting), it gets a new hardcoded type if its an extenal source (like deepdanbooru), different type id id as int type id as int primary key on (id, type id)