Owned view & bulk actions

The Owned view

Owned aggregates everything physical in one screen: cards in your binders, plus copies reserved by tracked decks and their commanders. It's the answer to "what do I actually have?" — searchable, sortable and filterable like any binder, with its own analytics and value screens.

The Owned view is also available to you on the web at silvane.app (only you can see it — visitors never can). See Public profile.

Where is this card?

From any card's page, the "In your collection" section lists every place it lives: which binders hold copies (with quantity, finish, condition) and which tracked decks reserve them. The available = owned − reserved math runs behind the scenes wherever it matters — deck building, Build sessions, sale pick lists — so you can't promise the same copy twice.

Bulk actions

In grid view, long-press any card in a binder or list (or pick Select cards from the ⋯ menu) to enter multi-select — bulk selection is grid-only, so switch out of list view first. The toolbar becomes an action bar for the whole selection:

• Tag — add tags to everything selected at once.
• Move — send the selected copies to another collection.
• Add — duplicate the selection into another collection, leaving the originals where they are.
• Bulk — the batch editor: set quantities to a number or adjust them ±N, consolidate everything into one finish, move the selection to a condition (copies merge into the matching condition bucket), or flag For Trade — with a live summary of exactly what will change before you confirm.
• Edit — select exactly one card and the Bulk slot becomes Edit: the full single-card edit screen (quantities, condition, language, printing) without leaving the grid.
• Delete — removals go to the recycle bin.

Merging collections

Merge one collection into another (for example, a "New order" list into your main binder once the cards arrive) from the collection's management sheet. Quantities combine per printing/finish/condition/language — and the source collection is deleted after merging (the confirm dialog says so; it lands in the recycle bin like any deletion).