feat (sparkvault): naming and organization

Described naming conventions and smart folder usage for organizing the Sparkvault.
OAM is the only client I know of that has a 3 letter client code.  I really
dislike the idea of a 3 letter client code from one system being used as
the ongoing identifier for all related things.  I've been in too many
situations were those some billing system's code was entangled in every
other system dragging down capabilities for years.




On Mon, Jun 16, 2014 at 3:15 PM, Jeremy Mack <notifications@github.com>
wrote:

> In software/1password/README.md:
>
> >
> > -When creating or storing credentials.
> > -* Use folders for each client
> > +#### Naming Conventions
> > +When naming a new asset, follow the convention `client-asset-environment`.  Some examples:
> > +
> > +* `sparkbox-seesparkbox.com-production`
> > +* `fav_customer-mandrill-production`
>
> We could use tags instead. A naming scheme for tags would make sense,
> since it's already metadata.
>
> If we still desire to have a prefix with client info, I would say do the
> three letter client code that we use internally (e.g. OAM).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/sparkbox/how_to/pull/20/files#r13824788>.
>



-- 


*Ryan Cromwell**Sparkbox*
123 Webster Street, Studio 2
Dayton, OH 45402
937.401.0915 · calendar
<http://www.google.com/calendar/embed?src=ryan%40heysparkbox.com&ctz=America/New_York>
www.seesparkbox.com