Here's how booster data goes into the system:
- card data is imported from mtgjson (
data/sets/*.json), it contains a lot of metadata we'll use, like rarities, types, foiling status etc. - every set has assigned base size (the second number in labels like "183/280") - it comes from mtgjson, but due to far too many errors there's override list for it in
indexer/lib/patches/patch_base_size.rb. Normally cards with numbers up to base go into boosters, and those over it don't. - for sets where it is necessary, print sheets data from
data/print_sheetsis added to the cards. There are multipleindexer/lib/patches/patch*handling it. - yaml files describing each booster are in
data/boosters/*.yaml, notably with common sheets extracted todata/boosters/common.yaml - indexer checks which sets have boosters based on yaml files, and marks these sets with
st:booster. It also has list of sets without boosters, but which go to other boosters (like Masterpieces). It happens inindexer/lib/patches/patch_has_boosters.rb - booster indexer
booster_indexer/bin/booster_indexerpreprocesses these yaml files into single fileindex/booster_index.json, doing a lot of preprocessing, and hopefully providing some error handling - when the system starts, it uses
index/booster_index.jsonfor booster information, and resolves all the queries it contains
If you want to learn about yaml files describing each booster, chck data/boosters/README.md