Skip to content

Brick Work 0.8.0

Choose a tag to compare

@Ulef1005 Ulef1005 released this 03 Nov 19:08
· 452 commits to main since this release

Milestone A, onboarding: a fresh install reaches its own collection through one guided flow, Get started. No schema change: a 0.7.0 collection (schema 4.1) opens as it is, and going back to 0.7.0 needs no restore. See Bring your collection in from another app and Settings and maintenance.

  • No key yet is not a failure (#139). A step that only lacks a key (a BrickLink price, Brickset's set data) now ends as done and waiting for the key, so a job no longer shows failed on an install where you skipped the keys. Jobs says Waiting for a key · runs once it is stored. Storing the key puts those steps back in the queue, and so does a start with a key set in the environment. A key the site refuses still fails.
  • BrickLink part numbers that name several parts (#140). BrickLink files some Rebrickable parts under one number: 3001 also names the old mould 3556. An XML line for such a part now takes the part with the same Rebrickable number and says so in the review. Without one, it names the candidates. Before, it was refused as Colour needs manual matching although the colour was known.
  • Bulk actions are one job (#127): Refresh pictures, Bulk refresh prices and fetching missing booklets show as one row in Jobs, with its progress (done, failed, cancelled, to go), the failed items with their reasons, and Cancel for what is left. Your own work runs first: an Add's import and part list, or a single Update price, go before the batch's next item, so a new set no longer waits up to 45 minutes behind a picture refresh. The per-source budgets hold as before. See Settings and maintenance.
  • Get started (#83, milestone A): the first run is one flow of four steps, in this order: Load the catalogue, Set up your keys (optional), Bring your collection in and See how the inventory works. Every step can be skipped for now and taken back. The flow resumes at the first open step, and after the first run it opens again from Tools & Admin › Get started, with how many steps are done. Before, the keys came first and the BrickTracker import was a fourth step. The catalogue step explains what the catalogue is (what it holds, Brick Work ids, what comes later), and once it is done shows how many items and colours it holds and the date of its files (#85). The keys step carries the key cards of Catalogues & keys: what each key gives, a link to where it is made, Test and save, and the site's reason when it refuses one; it says what is missing without keys (#84). Step 3, Bring your collection in, asks where your collection lives today: a Rebrickable or Brickset account (Collection sync), a BrickLink XML file, Import from BrickTracker, another app's BrickLink XML or Rebrickable CSV, or by hand. Each opens its existing path, which offers ‹ Back to Get started. There, a summary counts what came in, how many copies still lack condition and completeness, and links each imported from … tag. Brickset's My Sets CSV is read by Add (File): owned sets with their count, split by new and used, or wanted sets to a wishlist; a file without the columns it needs is refused by name (#12). Add opens on a mode given in its link (?mode=file). New guide: Bring your collection in from another app (#86). Step 4, See how the inventory works, is five short cards (sets and copies, completeness, loose stock and lots, the workflows at the table, an assistant), each linking to the screen it explains, with the important words in bold; Got it marks it read (#87). See Settings and maintenance.