Feature wishes: Option to load all images from rebrickable, custom fields, paypal for donation #146

New Issue

Open

opened 2026-04-14 15:38:54 +02:00 by derwohat · 8 comments

derwohat commented 2026-04-14 15:38:54 +02:00

Copy Link

Copy Source

Hi Frederik,

I have some feature wishes:

1. It would be nice to have an option to load all available pictures from rebrickable per set and also to upload my own pictures. For example I think that it would look much nicer to have the boxed pictures of the sets on the dashboard rather then some built versions. And instead of the blurry picture as a background I would suggest to put the main picture on the left border and put the rest of the pictures as a preview grid on the right side.
2. Adding custom categories, fields and values would be nice
3. Please show the correct price-tags in the dashboard. Not the rounded numbers.
4. Mass-editing for tags (or other properties) could also be useful
5. Please provide a paypal adress for donation so I dont have to put in my credit card into that buy me a coffee thing ;)

Thank you so much for that app. I am curious for future updates!

Hi Frederik, I have some feature wishes: 1. It would be nice to have an option to load all available pictures from rebrickable per set and also to upload my own pictures. For example I think that it would look much nicer to have the boxed pictures of the sets on the dashboard rather then some built versions. And instead of the blurry picture as a background I would suggest to put the main picture on the left border and put the rest of the pictures as a preview grid on the right side. 2. Adding custom categories, fields and values would be nice 3. Please show the correct price-tags in the dashboard. Not the rounded numbers. 4. Mass-editing for tags (or other properties) could also be useful 5. Please provide a paypal adress for donation so I dont have to put in my credit card into that buy me a coffee thing ;) Thank you so much for that app. I am curious for future updates!

FrederikBaerentsen commented 2026-04-14 21:23:26 +02:00

Owner

Copy Link

Copy Source

Thanks for the detailed list!

Going through each point:

1. Load all images from Rebrickable / upload own images:

I get the idea, unfortunately the Rebrickable API only returns a single cover image per set. There's no endpoint to fetch multiple photos or select if it is a box-image or build-set-image that's returned. Custom image uploads could be interesting longer term but is a bigger feature to design properly. I've noted it for future consideration.

2. Custom categories, fields, and values:

Could you explain what you mean here? BrickTracker already supports custom tags and statuses which can be created and assigned to sets. If those don't cover your use case I would love to understand what you're trying to do. Could you provide some examples?

3. Price tags showing rounded numbers:

Good catch. This is a bug. Some of the price values on the Statistics page are formatted with %.0f (rounded to whole numbers) instead of %.2f. Will be fixed in the next release.

4. Mass-editing tags and other properties:

Noted, but this is a bigger feature that won't make it into the current release. Added to my backlog. It is a functionality I've wanted myself too, so it is definitely on my radar.

5. Donation / PayPal

The README on the release/1.4-branch has been updated with the relevant link. Thanks for asking!

Thanks for the detailed list! Going through each point: 1. Load all images from Rebrickable / upload own images: I get the idea, unfortunately the Rebrickable API only returns a single cover image per set. There's no endpoint to fetch multiple photos or select if it is a box-image or build-set-image that's returned. Custom image uploads could be interesting longer term but is a bigger feature to design properly. I've noted it for future consideration. 2. Custom categories, fields, and values: Could you explain what you mean here? BrickTracker already supports custom tags and statuses which can be created and assigned to sets. If those don't cover your use case I would love to understand what you're trying to do. Could you provide some examples? 3. Price tags showing rounded numbers: Good catch. This is a bug. Some of the price values on the Statistics page are formatted with %.0f (rounded to whole numbers) instead of %.2f. Will be fixed in the next release. 4. Mass-editing tags and other properties: Noted, but this is a bigger feature that won't make it into the current release. Added to my backlog. It is a functionality I've wanted myself too, so it is definitely on my radar. 5. Donation / PayPal The [README](https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/src/branch/release/1.4#bricktracker) on the `release/1.4`-branch has been updated with the relevant link. Thanks for asking!

FrederikBaerentsen added the Kind/BugKind/EnhancementKind/Feature labels 2026-04-14 21:23:37 +02:00

FrederikBaerentsen added this to the Version 1.4 milestone 2026-04-14 21:23:48 +02:00

derwohat commented 2026-04-15 11:57:51 +02:00

Author

Copy Link

Copy Source

Hi,

Thanks for your reply.

1. Its a pity not to have all the pictures available. Perhaps it works with brickset api? At least it would be nice to upload the main image and some more by myself, if not automatically via one of the portals. Thanks for consideration.
2. For example if I sold a set, I would be nice to have that number too in the database. I know you dont want to go in that direction with your app, but I am not talking about some kind of automation for professional sellers on ebay. Just to have a field for custom information like notes or something, would be nice.
3. Thanks
4. Thanks again!
5. Perfect!

Hi, Thanks for your reply. 1. Its a pity not to have all the pictures available. Perhaps it works with brickset api? At least it would be nice to upload the main image and some more by myself, if not automatically via one of the portals. Thanks for consideration. 2. For example if I sold a set, I would be nice to have that number too in the database. I know you dont want to go in that direction with your app, but I am not talking about some kind of automation for professional sellers on ebay. Just to have a field for custom information like notes or something, would be nice. 3. Thanks 4. Thanks again! 5. Perfect!

FrederikBaerentsen commented 2026-04-15 15:06:25 +02:00

Owner

Copy Link

Copy Source

Thanks for the follow up!

1. I have previously looked at the BrickSet API. getAdditionalImages does support fetching additional images per set, but it requires both an API key, a user hash and a setID, which you get via getSets, as the setID isn't the same as the setNumer. The Brickset API key isn't as straightforward to obtain as a Rebrickable key. So I'd rather not add that dependency for now.
   Instead, I'm going to go the custom upload route: users will be able to upload their own images to a set, select which one acts as the cover image, and browse them in a lightbox. I'll add this to the backlog for a future release. I really like the idea, as I also prefer the box image as the cover. I will also see if i can combine it with #37, and offer a sidecar container with custom sourced data, that BrickTracker can pull from. If i could source the links to the additional images all at once, we might not need every user to get them themselves.

2. Ah, I think I understand now. Not just tags, but fully user-defined key/value pairs. So instead of a predefined field like "Owner: UserX", you could define something like "Sold for: €45" where both the label and the value are up to you. That's a more flexible system than what's currently there. I'll look info the possibilities!

Thanks for the follow up! 1. I have previously looked at the BrickSet API. [getAdditionalImages](https://brickset.com/api/v3.asmx?op=getAdditionalImages) does support fetching additional images per set, but it requires both an API key, a user hash and a setID, which you get via [getSets](https://brickset.com/api/v3.asmx?op=getSets), as the setID isn't the same as the setNumer. The Brickset API key isn't as straightforward to obtain as a Rebrickable key. So I'd rather not add that dependency for now. Instead, I'm going to go the custom upload route: users will be able to upload their own images to a set, select which one acts as the cover image, and browse them in a lightbox. I'll add this to the backlog for a future release. I really like the idea, as I also prefer the box image as the cover. I will also see if i can combine it with #37, and offer a sidecar container with custom sourced data, that BrickTracker can pull from. If i could source the links to the additional images all at once, we might not need every user to get them themselves. 2. Ah, I think I understand now. Not just tags, but fully user-defined key/value pairs. So instead of a predefined field like "Owner: UserX", you could define something like "Sold for: €45" where both the label and the value are up to you. That's a more flexible system than what's currently there. I'll look info the possibilities!

derwohat commented 2026-04-15 17:47:48 +02:00

Author

Copy Link

Copy Source

1. Perhaps you can make it a combined field. Either uploading the image from harddrive oder copy the link of an actual image i.e. from brickset so that the image will be downloaded directly from brickset to BrickTracker instead of having to safe the image to harddrive and then upload again. Could save some time.
2. Yes, exactly.
3. NEW: I just thougt of another little tweak. In the detail view of a set it would be nice to have the minifigs also inside of a foldable category. Or if it is too complicated, please put the management section up above the minifigs.

1. Perhaps you can make it a combined field. Either uploading the image from harddrive oder copy the link of an actual image i.e. from brickset so that the image will be downloaded directly from brickset to BrickTracker instead of having to safe the image to harddrive and then upload again. Could save some time. 2. Yes, exactly. 3. NEW: I just thougt of another little tweak. In the detail view of a set it would be nice to have the minifigs also inside of a foldable category. Or if it is too complicated, please put the management section up above the minifigs.

FrederikBaerentsen commented 2026-04-18 20:21:32 +02:00

Owner

Copy Link

Copy Source

Rounding error: Fixed in the upcoming 1.4.1 release. All price values on the Statistics page should now use %.2f. You can test it now with the pre-1.4.1 Docker tag.

Rounding error: Fixed in the upcoming 1.4.1 release. All price values on the Statistics page should now use %.2f. You can test it now with the `pre-1.4.1` Docker tag.

FrederikBaerentsen referenced this issue from a commit 2026-04-30 20:12:21 +02:00

fix(statistics): show price values with 2 decimal places instead of rounding to whole numbers (see #146)

FrederikBaerentsen commented 2026-06-15 21:39:24 +02:00

Owner

Copy Link

Copy Source

@derwohat, okay i got far with this!

As with #160:

I've been wanting a way to pull bricklink+brickset values without forcing it into bricktracker. What i landed on is a separate little "sidecar" container that talks to brickset/bricklink, and bricktracker just asks it for data. The container queries Bricklink on-demand and can schedule data pulls from brickset. A handful of new env vars are added, but if you do not fill out the url for the secondary container, all brickset/bricklink info is hidden automatically. That way nobody is forced to use it.

For the images part I'm using the sidecar to grab the bricklink box/set art and let you use it as the set cover. did a POC and it works.

How it would be in v1.5:

• Existing set: a "cover image" bit under management to preview the box/set art in a popup and either use it as the cover (it backs up the original rebrickable image first) or restore the original.

• Adding a single set: a "check box art" preview before you submit, plus a "use box art as
  cover" tickbox.

• Bulk add: a "force box art (fallback to normal image)" tickbox that just keeps the rebrickable
  image when theres no box art.

There will also be a setting to always prefer the box art.

I am still trying to see if i can get all images from bricklink/brickset. I'll get back to you there.

@derwohat, okay i got far with this! As with #160: > I've been wanting a way to pull bricklink+brickset values without forcing it into bricktracker. What i landed on is a separate little "sidecar" container that talks to brickset/bricklink, and bricktracker just asks it for data. The container queries Bricklink on-demand and can schedule data pulls from brickset. A handful of new env vars are added, but if you do not fill out the url for the secondary container, all brickset/bricklink info is hidden automatically. That way nobody is forced to use it. For the images part I'm using the sidecar to grab the bricklink box/set art and let you use it as the set cover. did a POC and it works. How it would be in v1.5: - Existing set: a "cover image" bit under management to preview the box/set art in a popup and either use it as the cover (it backs up the original rebrickable image first) or restore the original.   - Adding a single set: a "check box art" preview before you submit, plus a "use box art as cover" tickbox.  - Bulk add: a "force box art (fallback to normal image)" tickbox that just keeps the rebrickable image when theres no box art. There will also be a setting to always prefer the box art. I am still trying to see if i can get **all** images from bricklink/brickset. I'll get back to you there.

add_box_art.png

265 KiB

bricklink_set_art.png

202 KiB

bricklink_box_art.png

348 KiB

FrederikBaerentsen modified the milestone from Version 1.4 to Version 1.5 2026-06-15 21:40:04 +02:00

FrederikBaerentsen commented 2026-06-16 21:14:17 +02:00

Owner

Copy Link

Copy Source

@derwohat, Went through all the points on this one again, and I see i overlooked your request for additional images. I added this to the sidecar container

Images:

I added an opt-in additional-images carousel (SIDECAR_ADDITIONAL_IMAGES): the cover turns into a little carousel of the brickset images and you can pick any of them as the cover too. Custom uploads of your own photos i left out for now, since the sidecar only serves the fixed bricklink/brickset images. Let me know if upload of your own images is important to you.

Custom Fields:

You can now make your own fields in the admin, under set metadata > set custom fields. each field has a name and a type (text, number or date). After that every set gets an input for each field under management where you fill in the value.

So for your sold example youd make a field "sold price" (number) and maybe "sold date" (date), and fill them in on the sets you sold. The values are stored in the database with the rest of the set data.

It works like the tags and statuses already do: you define the field once and then use it on any set. I went this way instead of a totally free label+value on each set, because the things you mentioned (sold price, notes) are usually the same field across many sets, so this keeps it consistent and i can use it in stats and filters later. If you really need a different label on every single set let me know.

Mass Edit:

On the sets grid I added a "select" button that lets you pick several sets.

Then "edit selected" opens a panel where you change tags, statuses, owners, etc. Fields where the selected sets already share a value show that value, fields that differ show "varies" and only get written if you actually touch them, and the tag/status/owner checkboxes are tri-state (all on / all off / mixed).

Is this the idea you had?

Still has some bugs to fix, but the general functionality is there.

@derwohat, Went through all the points on this one again, and I see i overlooked your request for additional images. I added this to the sidecar container  Images: I added an opt-in additional-images carousel (SIDECAR_ADDITIONAL_IMAGES): the cover turns into a little carousel of the brickset images and you can pick any of them as the cover too. Custom uploads of your own photos i left out for now, since the sidecar only serves the fixed bricklink/brickset images. Let me know if upload of your own images is important to you.  Custom Fields: You can now make your own fields in the admin, under set metadata > set custom fields. each field has a name and a type (text, number or date). After that every set gets an input for each field under management where you fill in the value.  So for your sold example youd make a field "sold price" (number) and maybe "sold date" (date), and fill them in on the sets you sold. The values are stored in the database with the rest of the set data. It works like the tags and statuses already do: you define the field once and then use it on any set. I went this way instead of a totally free label+value on each set, because the things you mentioned (sold price, notes) are usually the same field across many sets, so this keeps it consistent and i can use it in stats and filters later. If you really need a different label on every single set let me know. Mass Edit: On the sets grid I added a "select" button that lets you pick several sets.  Then "edit selected" opens a panel where you change tags, statuses, owners, etc. Fields where the selected sets already share a value show that value, fields that differ show "varies" and only get written if you actually touch them, and the tag/status/owner checkboxes are tri-state (all on / all off / mixed).  Is this the idea you had? Still has some bugs to fix, but the general functionality is there.

cover_pick.png

196 KiB

mass_edit_select_sets.png

507 KiB

lightbox.png

807 KiB

set_custom_fields.png

27 KiB

mass_edit_data.png

311 KiB

derwohat commented 2026-06-17 01:30:00 +02:00

Author

Copy Link

Copy Source

I am super happy with your work. Can't wait to test it out! Thanks a lot!

I am super happy with your work. Can't wait to test it out! Thanks a lot!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

release/1.5

release/1.4.1

bugfix/issue-151

bugfix/issue-150

bugfix/issue-149c

bugfix/issue-149b

bugfix/issue-149a

bugfix/issue-152

release/1.4

release/1.3.2

release/1.3.2-fk-fix

release/1.3

feature/parts

feature/minifigures

feature/statistics

feature/consolidation

feature/checkbox

feature/peeron

feature/pagination

hotfix/pagination-bug

feature/bricklink-data

feature/sort-search-filter

instructions

v1.4.1

v1.4.0

v1.3.1

v1.3

v1.2.4

v1.2.3

v1.2.0

1.2.0

v1.1.0

v1.0.0

Labels

Clear labels

Compat/Breaking

Breaking change that won't be backward compatible

Kind/Bug

Something is not working

Kind/Documentation

Documentation changes

Kind/Enhancement

Improve existing functionality

Kind/Feature

New functionality

Kind/Security

This is security issue

Kind/Testing

Issue or pull request related to testing

Out of Scope

Request is out of scope

Priority

Critical

The priority is critical

Priority

High

The priority is high

Priority

Low

The priority is low

Priority

Medium

The priority is medium

Reviewed

Confirmed

Issue has been confirmed

Reviewed

Duplicate

This issue or pull request already exists

Reviewed

Invalid

Invalid issue

Reviewed

Won't Fix

This issue won't be fixed

Status

Abandoned

Somebody has started to work on this but abandoned work

Status

Blocked

Something is blocking this issue or pull request

Status

Need More Info

Feedback is required to reproduce issue or to continue work

Unraid

Unsupported/Can't help

No Label Kind/Bug Kind/Enhancement Kind/Feature

Milestone

No items

No Milestone Version 1.5

Projects

Clear projects

No project

Assignees

Clear assignees

FrederikBaerentsen

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#146