• add
  • Usage: xents tagtofiles add <tag> <files>*
  • Description: creates links from one tag to $\ge$ 1 files
  • Alias: assign
• remove
  • Usage: xents tagtofiles remove <tag> <files>*
  • Description: removes a link one from one tag to $\ge$ 1 files
  • Alias: rm
• show
  • Usage: xents tagtofiles show <tags>*
  • Description: shows all files linked to each tag inputted. can take more than one tag as input

• add
  • Usage: xents filetotags add <file> <tags>*
  • Description: creates links from one file to $\ge$ 1 tags
  • Alias: assign
• remove
  • Usage: xents filetotags remove <file> <tags>*
  • Description: removes links from one file to $\ge$ 1 tags
  • Alias: rm
• show
  • Usage: xents filetotags show <files>*
  • Description: shows all tags linked to each file inputted. can take more than one file as input

• Nested:
  • Usage: xents filter <tags>
  • Description: the default mode.
  • Example: xents filter "organic chemistry" will return everything that is tagged with something within organic chemistry. If a file is tagged only with “carbon nanotubes”, it will be returned because “carbon nanotubes” is a sub-tag in organic chemistry
• Explicit -e
  • Usage: xents filter -e <tags>
  • Description: will only return a file if it is explicitly tagged with it
  • Example: xents filter -e "organic chemistry" will return a file marked with “organic chemistry,carbon nanotubes” but not one with just “carbon nanotubes”.
  • Note: Uses the same implementation as xents tagtofiles show <files>* and is included here with -e tags for mnemonic purposes
• Traverse Down by Count -td
  • Usage: xents filter -td <count> <tags>
  • Description: Returns files only if explicitly tagged with a tag a certain number of levels removed from the query tag.
  • Example: xents filter -td 2 "organic chemistry" will return everything explicitly tagged with any tag between 0 and 2 layers down from “organic chemistry”. In this example, files tagged with “carbon nanomaterials” will be returned but files tagged with only “carbon nanotubes” will not.
  • Note: Can be combined with Traversal Down by Increment -tu <count> -td <count>. For example xents -tu 1 -td 2 will traverse one node up the tree then return everything recursively down two layers from that.
    
• Traverse Up by Count -tu
  • Usage: xents filter -tu <count>
  • Description: Recursive by default.
  • Example: xents -tu 1 "organic chemistry" will traverse one node up the tag tree then return everything recursively down from that
  • Note: Can be combined with Traversal Up by Increment -td <count> -tu <count>

Each tag ipsodata can vary significantly in length, so an offset table is used to save lots of file space at minimal expense of lookup time. All the attributes in the ipsodata can also vary in length from eachother, so a “tag individual ipsodata part length” field is needed in the metadata. Tag ipsodata offset is the distance measured from (3.3.a). The tag UUID is not neccassary for the tag ipsodata, but is included for debug purposes.

1. Tags Metadata = {$\forall$ Tag Metadata}
   • Tag Metadata = {Tag UUID, Tag individual ipsodata part length, Tag ipsodata offset}
2. Tags Ipsodata = {$\forall$ Tag Ipsodata}
   • Tag Ipsodata = {Tag UUID, Tag name, Tag Ancestry UUIDs, Tag Children UUIDs}

The same heuristics about length variation and UUID-inclusion from (4) apply here. File-to-tags metadata starts at (3.3.b) and file ipsodata offset is the distance measured from (3.3.c).

1. Files Metadata = {$\forall$ File Metadata}
   • File Metadata = {File UUID, File individual ipsodata part length, File ipsodata offset}
2. Files Ipsodata = {$\forall$ File Ipsodata}
   • File Ipsodata = {File UUID, Tags UUIDs}