Table Structure for Managing a Collection with Org Table

I have found org tables to be very powerful and useful. I feel like I have movement, table restructuring and basic formulas down fairly well. But I am having a difficult time wrapping my head around how I should structure this for tracking large collections. Not sure if I can do this in one table or if I need multiple tables.

Say I have a business that buys and sells trading cards. There are baseball, basketball and football cards. I want to track purchase price, sale price, purchase date, sale date, average sale price, last sale price, quantity in stock, and item condition for every card sold or in stock.

Is it possible to do this in a single table or do I need multiple tables?

I'd like to track statistics such as:

"What is the average price of all football cards sold in the last six months?"

"In the last month, did I buy more basketball cards or baseball cards?

And for a more lengthy example:

"Last year I sold 4 Mickey Mantle cards. 2 in Mint condition, 1 in Excellent condition, 1 in Poor condition and 1 unsold. What percentage of Mint Mickey Mantle cards were sold last year?"

To reiterate, in org-mode can all this be accomplished within a single table? How would it be structured if say, you knew Tops only made 2000 unique cards in a particular year, would table only contain 2000 rows? (plus the header) Sorry if most of this sounds like a high school math problem with no code but I'm sure most people (at least here) know what a single org table with the mentioned columns and a finite set of rows would look like.

Edit: I originally posted this to the Emacs specific Stack Exchange. I will delete the one that doesn't receive a response.

0 Comment



Captcha image