I'm not sure that this is possible with a taxonomy, but I was hoping to get some feedback on the best way to store my data. My site is storing information about soccer players and teams. I have a team custom post type and a player custom post type. My team page shows all of the related players, based on Posts to Posts data previously entered.
My problem is that in the future, when players change teams, there isn't any way to store any kind of time related data with the existing relationship. For example, at a minimum, I'd love to be able to store some sort of tag 'current', so that way my team page could show the current team as well as a list of all players. Even better would be storing the years that a player was a part of the team.
I was thinking that perhaps the taxonomy description would be a place to store that information without having to create new tables or fields. I could maybe serialize some information and put it in as part of the connection process. Does that sound like a good way to accomplish what I'm trying to do? The API might then be changed to have an optional filter based on the information stored in the description.
While I'm writing this, I'm still brainstorming how to make it functional. I'm thinking that in P2P metabox, after you create a connection, there could be a little button added that would allow you to edit the relationship description. That wouldn't require much of an interface than a text area, and you just assume that the developer putting data in there would also know how to read it out.
I haven't looked super closely at the actually hidden taxonomy, so it might not even be feasible given the current setup. Thoughts?