We both agree that tags are a more elegant solution. How about this then, I'll propose this idea:
You could have two types of tags, Storage and List. A user can define a tag and it appears in the tree on the left with the decks and can be put into the folders with Decks. The tag has properties like Type, Privacy and Label. Maybe color-code cyan/orange based on type, so most colorblind people can still differentiate them. Tags would not need a "quantity" field associated with them, that seems like a function for a Deck.
In most card tables you would need a column and/or View type to show which Storage-type tags are associated with that card. In normal view, there could be a Number of Storage Tags column next to the inventory counts, so the user could know to click a card and find out which trade binder or storage box it's in. An Edit button would be useful here. In Storage view, the cards could be separated into different tables by storage tags, with multi-tagged cards appearing in all associated tables.
If a tag was clicked, you would go to a view similar to the current Deck view, where see a table and you can add and remove cards from that tag. That's one way you could add cards to a tag without putting them in your inventory. You would also be able to click Edit in other views and add them to a tag. The Actions when you select cards in inventory/full DB views would let you add them to your tags just like you do with decks.
Thoughts worth pursuing maybe? I'm as interested in the ideal design as you are, since I'd be using it. But I work on software, so I also know shelving an idea until you have the perfect version of it means that it never happens. I'd be happy with something that covers the bases even if it's a little clunky at first.
Last edited by djdanlib (2016-04-05 14:11:16)