Many people manage collections in Excel or Google Sheets, and neither imports JSON comfortably.
Card entries are flat, so a defined CSV projection (fixed column names matching the field names, id.scryfall flattened to id_scryfall) would be nearly lossless and give spreadsheet users a standardized path in and out.
Should the RFC define this projection as a companion representation, or is JSON-only with per-site CSV exports enough?
See the open questions section in the README.
Many people manage collections in Excel or Google Sheets, and neither imports JSON comfortably.
Card entries are flat, so a defined CSV projection (fixed column names matching the field names,
id.scryfallflattened toid_scryfall) would be nearly lossless and give spreadsheet users a standardized path in and out.Should the RFC define this projection as a companion representation, or is JSON-only with per-site CSV exports enough?
See the open questions section in the README.