Categories/tags

[DizzyHSlightlyVoided]

I'd like an option to separate entries by category, i.e. if you have multiple Twitter accounts, put them in the "Twitter" category. Another way to do it would be to have tags, which would mean an entry could have multiple "categories" but would amount to the same thing for the purpose of searching.

[devgeeks]

I hadn't thought of this, but now it's really in my head.

Going to need to think about it a bit, but I really like this idea.

[ghost]

I would strongly recommend tags, although I think that tags should be hierarchal as well (like gmail labels).

[devgeeks]

What is it you want from hierarchical, and what is the value you are looking for from them?

I am going to be doing tags for sure, it looks like. I am just trying to understand so I can implement it the best way I can.

[ghost]

Well, I have one giant folder in KeePass that I've named "community" where I have folders for social networks, chat servers, wikis, forums, etc. that are all categorised, and I'd rather have these folders grouped together than loose in a giant list. I also have a group for chat clients that's sorted into IRC and XMPP, and I'd imagine that people with multiple social networking accounts might want Social/Twitter, Social/Facebook, etc. tags. I mean, this is easily doable if you allow adding slashes in names, but treating them conceptually as hierarchal allows you to add more UI in the future to collapse them, etc. once everything else is in place.

[devgeeks]

I see.. well.. tags are a certain, I'll have to work out if we can do them hierarchical right away or push that till later on.

[kenmanheimer]

Here's an envisioning of how Encryptr could offer tags. It's intended to be a whole picture, but not necessarily implemented all at once - it could be done in stages, building gradually to a conclusion that's cohesive.

To provide for content organization by using tags, Encryptr could offer a set of included tags that are universally applicable, and would lead users to see how to apply and extend them to avoid clutter.

To facilitate this, I think the set of tags included with the app should:

• Be fairly universal, to be immediately useful to most people.
• Convey that tags divide things categorically, but also can be combined:
  • Some are categoric opposites - work versus personal versus community
  • Some are mutually independent, so suitable for combination. For example, service can combined with both work and personal, for work/service vs personal/service.

The UI would need to convey that the default tags can be used, as is, and also be trivially supplemented with new ones. There are conventional UI tropes for this, like tag-entry text boxes that offer completions from already-present tags but also allow entry of entirely new ones.

Here are some tags that might qualify:

• Contexts: work, personal, community
• Applications:
  • system - workstation, mobile, and network device logins, certs, ,
  • service - web-based resources, gas, electric, telecom utilities, financial online accounts
  • vendor - shopping accounts
  • entertainment - amusement accounts
  • physical - for lock combinations and passcodes
  • identity - social security number, drivers license number, PGP/GPG keypairs, ssh keypairs

I agree that expressing tag combinations hierarchically helps people organize how they think about them. Combinations of tags would be expressed as paths: work/service/aws versus home/service/netflix. The ordering isn't actually significant - it could equally be service/aws/`work``.

[DizzyHSlightlyVoided]

I think that it would be better if tags are user-provided, rather than something built into the app, but I can also see the benefit of including pre-built ones.

[devgeeks]

@KimikoMuffin - user added as well, for sure... the provided ones will just be a seed to show what can be done

[DizzyHSlightlyVoided]

Yeah, that's what I meant, I was responding to @kenmanheimer's comment

[kenmanheimer]

@KimikoMuffin, I agree. I think if we arrange it well, including some initial ones won't work against people using their own, and to the contrary, can foster that. That's also why I was suggesting that the UI needs to provide for entry of entirely new tags, as well as preestablished ones, etc.

[shibacomputer]

Added to 3.0 feature set.