possible nickname reuse quandry?

[Jim Sharp]

I'm still thinking through the use case here, so my apologies in advance if this isn't 100% formed.  It is also entirely possible that I'm just too lazy or not doing it right.

In short, when entering "how did it go?" notes after a run, I want to minimize the extra entry for tagging a pair of shoes.  Combine that with (for the first time!) joining the ranks of those on a second pair of the same model of shoes, and I'd like to just tag them with a simple and memorable nickname such as "Adrenaline" without having to remember if this is "Adrenaline 3" or "Adrenaline 4," if the first couple pairs are marked as retired.

If/when I get to the point where I have more than one active pair of the same model going, I totally would understand (and be inclined to) keeping track of which is "Adrenaline A" and which is "Adrenaline B."

Man, I hope that makes at least a little sense...I swear I usually feel like a better communicator than this.

Potential Scenario:

• User starts with one pair of shoes, names them "Adrenaline"
  
• User tags with curly-braces using this name {Adrenaline} and, predictably, activities are imported and associated with these shoes
  
• User retires shoes named "Adrenaline"
  
• User purchases new shoes of same model, and wants to reuse name to avoid typing {Adrenaline Pair Two Because I'm AWESOME} when tagging in RK
  
• User renames retired shoes "Adrenaline 2012, pair 1" so he can re-use name "Adrenaline" on the new pair
  
• User adds new pair with name "Adrenaline" (and is allowed to do so, having renamed the retired pair)
  
• User refreshes activity list from HG...
  
• ...Sad trombones play because now all the {Adrenaline} tagged activities get associated with the new pair instead of the old pair.

If this is an accurate prediction of behavior (and very limited playing around on my part indicates that it might be), then I'd be eager to help brainstorm a way around this!  

I wonder if it would be possible to alter/edit the original curly-brace tag via API after retrieval to prevent this from being changed on future refreshes?  For example, after pulling {Adrenaline} and associating that activity with that pair, perhaps the original note is edited to read [Adrenaline] or "Shoes used: Adrenaline" so that future "imports" don't see a curly-brace-surrounded note that would cause the associated shoes to be altered? 

I very much love the simplicity of this and the gaping hole it seems to fill, even having just gotten start with it tonight!  I had been considering creating my own google doc to track this until I had time to try interacting with the API, so was thrilled to see this option.

Keep on being awesome!

j

(if it's of any use, RK profile is http://runkeeper.com/user/jimbly/profile)