Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow different tag labels #427

Open
tevpg opened this issue May 14, 2024 · 0 comments
Open

Allow different tag labels #427

tevpg opened this issue May 14, 2024 · 0 comments

Comments

@tevpg
Copy link
Collaborator

tevpg commented May 14, 2024

Current TT tags are alpha-alpha-digit-[digit*]

Want to allow any kind of tag syntax

Well, within reason. I think a tag would be defined as a sequence of at least 2 alphanumerics, and is unique across case folding and numerals of the any digits. So

  • AB and ab fails the uniqueness requirement
  • AB1 and AB01 fails the uniqueness requirement

Implications:

  • identify tags by their presence in config file not by their syntax
  • tag inventory and audit can no longer assume tag syntax
  • optionally config has a re pattern to restrict tag formats - used when typing tags and when loading config & datafiles.
  • tags are case-folded and numeric sequences have leading 0's compressed away
  • sorting rules: hmmmm. Probably sort based on a canonical/sorting representation which pads all numeric sequences to - i dunno - ten digits or something; after that applies a simple alpha sort
  • tagid attributes:
    • mostly as-is, though want a 'sorting' representation
    • '.simple' -- the tag in its simplest form -- useful for comparing, and this is what would be used in tables like the invetory matrix etc
    • '.sorting' -- the tag with all its numeric sequences expanded to some long number of digits, so that a simple alpha compare/sort will then work

Tag inventory

  tagid tagid tagid tagid tagid tagid tagid
  In    Out   Ret   In    -     Out   Out

  tagid tagid tagid tagid tagid tagid tagid
  In    Out   Ret   In    -     Out   Out

where the layout is determined by the longer of the longest tagid (though at least 2); then
simply run together for the length of a line

Audit matrix

More or less the same - but do not need the statuses

Web reporting

Tag history and such may not have meaning in the same way. Consider the wen reports and recognize

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant