[Feature] Add Quantity for Sets #78

New Issue

2025-05-22T17:40:20+02:00

aronwk commented

2025-05-22 17:40:20 +02:00

It would be nice to be able to set a quantity of a set owned, so that can be shown more cohesively rather than them all being separate sets in the set view.

EX: I own 3 of a set, rather than showing all 3 entries on the set page, you show one entry.
Then once you go into that set, you can select different properties/attributes for each sets, if you need to do so.

It would be nice to be able to set a quantity of a set owned, so that can be shown more cohesively rather than them all being separate sets in the set view. EX: I own 3 of a set, rather than showing all 3 entries on the set page, you show one entry. Then once you go into that set, you can select different properties/attributes for each sets, if you need to do so.

aronwk commented

2025-05-22 17:51:23 +02:00

To add some more ideas to this:
I have multiple Galaxy explorer sets, each build into different version or MOCS using only parts from this set.

Main build
A alt build
B alt Build
Mech MOC
Walker MOC
2 combined into one larger ship
one un-built

Being able to have these represented as one set on the top level page, then go into the set and see all the copies of the set would make more sense then having all of the sets like this:

To add some more ideas to this: I have multiple Galaxy explorer sets, each build into different version or MOCS using only parts from this set. - Main build - A alt build - B alt Build - Mech MOC - Walker MOC - 2 combined into one larger ship - one un-built Being able to have these represented as one set on the top level page, then go into the set and see all the copies of the set would make more sense then having all of the sets like this: ![image.png](/attachments/d8ed7795-08d6-4818-8a56-c51824867a12)

image.png

330 KiB

FrederikBaerentsen commented

2025-06-11 19:14:54 +02:00

I understand, but then missing pieces wont work. The reason for having each individual set is to be able to track missing pieces for each set.

BrickTracker isn't really aimed at MOC builds.

I understand, but then missing pieces wont work. The reason for having each individual set is to be able to track missing pieces for each set. BrickTracker isn't really aimed at MOC builds.

aronwk commented

2025-06-11 19:27:10 +02:00

Hmmm, I'm not saying getting rid of the missing pieces. More like reorganize the UI.
Instead of having each set at the top level and having a card for each individual set there, have a single card for all instances of the same kit and break it down so show each individual set for that specific kit under it on a different page. Reducing clutter at the top level.
Does that make more sense?

Basically the functionality stay the same, just reorganize the UI to be less cluttered by duplicate sets at the top level

Also, not being aimed at MOCs is excluding a majority of the community around LEGO and building block/bricks

Hmmm, I'm not saying getting rid of the missing pieces. More like reorganize the UI. Instead of having each set at the top level and having a card for each individual set there, have a single card for all instances of the same kit and break it down so show each individual set for that specific kit under it on a different page. Reducing clutter at the top level. Does that make more sense? Basically the functionality stay the same, just reorganize the UI to be less cluttered by duplicate sets at the top level Also, not being aimed at MOCs is excluding a majority of the community around LEGO and building block/bricks

FrederikBaerentsen added the Kind/Feature label 2025-09-14 18:51:45 +02:00

FrederikBaerentsen added the

Priority

Low

label 2025-09-15 20:43:28 +02:00

FrederikBaerentsen changed title from ~~feat: Add Quantity for Sets~~ to [Feature] Add Quantity for Sets

2025-09-22 08:51:54 +02:00

FrederikBaerentsen commented

2025-09-26 16:34:26 +02:00

Looking at different implementation options. How does something like this look?

multicopy1.PNG

102 KiB

multicopy3.PNG

30 KiB

multicopy2.PNG

368 KiB

aronwk commented

2025-09-26 16:48:02 +02:00

yep! that looks great!!!

FrederikBaerentsen commented

2025-09-26 17:03:56 +02:00

Using Tags to display the "name" of each copy.

multi4.PNG

359 KiB

❤️ 1

FrederikBaerentsen commented

2025-09-28 07:45:53 +02:00

@aronwk The feature is available for testing using the docker label :consolidation.

Please do a database backup, as we are upgrading to version 18. Other features in this label includes:

Checkmarks (see #70)
Peeron instructions download (see #56)
Pagination (see #84)

New environment variables for consolidation:

# Optional: Enable set consolidation/grouping on the main sets page
# When enabled, multiple copies of the same set are grouped together showing instance count
# When disabled, each set copy is displayed individually (original behavior)
# Default: false
# BK_SETS_CONSOLIDATION=true

See the other issues for their specific environment variables.

Please report back any bug or feature requests.

@aronwk The feature is available for testing using the docker label `:consolidation`. Please do a database backup, as we are upgrading to version 18. Other features in this label includes: 1. Checkmarks (see #70) 2. Peeron instructions download (see #56) 3. Pagination (see #84) New environment variables for consolidation: ``` # Optional: Enable set consolidation/grouping on the main sets page # When enabled, multiple copies of the same set are grouped together showing instance count # When disabled, each set copy is displayed individually (original behavior) # Default: false # BK_SETS_CONSOLIDATION=true ``` See the other issues for their specific environment variables. Please report back any bug or feature requests.

FrederikBaerentsen referenced this issue

2025-09-28 09:33:14 +02:00

[Feature] Adding some statistic #91

FrederikBaerentsen added this to the Version 1.3 milestone 2025-10-01 19:29:23 +02:00

FrederikBaerentsen added this to the General Improvements project 2025-10-01 19:29:25 +02:00

FrederikBaerentsen commented

2025-10-01 19:29:50 +02:00

Implemented in #106. Testing on :consolidation until release.

Implemented in #106. Testing on `:consolidation` until release.

👍 1

FrederikBaerentsen closed this issue

2025-10-01 19:29:50 +02:00