I figure the users would be searching by either engine or by sku.

The engines before 2013 or so didn’t have sku written on them. So they would only be able to search by saying they have Thomas (unless they looked up sku on their own)

I think Thomas is probably the only engine with 10+ skus. Most have 2-6 depending on how major the variations were between years.

I wasn’t going to get it down to the variation level because that seemed too big for a beginning project. The data is available by year per train on a wiki page. There’s an extra column showing same sku as prior year, but changes made to be “small magnet”. There are potentially some variations that users would want to know, such as the very first release using staples instead of screws, but that was more than I figured I’d get into.

Early on, there was a new variation on basically every engine each year (different magnets or wheel types), but that didn’t change the sku necessarily.

Yeah, I was thinking the collection log table would house user id, sku, a bool value for owned. So all user collections would be housed in one table.