FrederikBaerentsen/BrickTracker
8
20
Fork 12
Code Issues 16 Pull Requests Actions Packages Projects 1 Releases 10 Wiki Activity

Storage and Purchase information #41

New Issue
Closed
opened 2025-01-19 11:28:49 +01:00 by FrederikBaerentsen · 8 comments
FrederikBaerentsen commented 2025-01-19 11:28:49 +01:00
Owner
Copy Link
Copy Source

A couple of features I'd like to see I'm currently using Koillection for mine but like the idea of how this breaks down individual components, any chance there's the possibility of adding in "Purchase Price", "Purchase Date", "Storage Location" or even if we could add our own check boxes that would be great, Thanks for putting in the time and effort to make this as good as it already is.
Also I like the idea of adding multiple sets at once (mainly for initial setup) and also grabbing the instructions as well.

Originally posted by @GazaShaggy in #25 (comment)

Storage Bin Location (I currently print out labels for each tub for what sets are in it, but would be much easier and more flexible if the tubs were numbered and I could track what was in each digitally!)

Originally posted by @davidjroos in #35 (comment)

  • Add fields to database table. Ensure it doesn't break existing table.
  • Add env option:
# Optional: Show fields for purchase info.
# Default: false
# BK_SHOW_PURCHASE_INFO=true

# Optional: Show fields for storage location.
# Default: false
# BK_SHOW_STORAGE_LOC=true
  • Add fields on /add (not on /add/bulk) to input purchase info like price, date and storage loc.
  • Add fields on /sets/*/details to show and edit the data
> A couple of features I'd like to see I'm currently using [Koillection](https://github.com/benjaminjonard/koillection) for mine but like the idea of how this breaks down individual components, any chance there's the possibility of adding in "Purchase Price", "Purchase Date", "Storage Location" or even if we could add our own check boxes that would be great, Thanks for putting in the time and effort to make this as good as it already is. Also I like the idea of adding multiple sets at once (mainly for initial setup) and also grabbing the instructions as well. _Originally posted by @GazaShaggy in https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/issues/25#issuecomment-196_ >Storage Bin Location (I currently print out labels for each tub for what sets are in it, but would be much easier and more flexible if the tubs were numbered and I could track what was in each digitally!) _Originally posted by @davidjroos in https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/issues/35#issue-81_ - [ ] Add fields to database table. Ensure it doesn't break existing table. - [ ] Add env option: ````bash # Optional: Show fields for purchase info. # Default: false # BK_SHOW_PURCHASE_INFO=true # Optional: Show fields for storage location. # Default: false # BK_SHOW_STORAGE_LOC=true ```` - [ ] Add fields on `/add` (not on `/add/bulk`) to input purchase info like price, date and storage loc. - [ ] Add fields on `/sets/*/details` to show and edit the data
FrederikBaerentsen added the Kind/Feature label 2025-01-19 11:28:49 +01:00
FrederikBaerentsen added this to the General Improvements project 2025-01-19 11:28:49 +01:00
gregoo commented 2025-02-03 16:39:55 +01:00
Contributor
Copy Link
Copy Source
  • Admin

image

  • Add

image

  • Set management

image

  • Badge (I'm running out of default colors 🙃)

image

image

image

- Admin ![image](/attachments/a770cfc5-02b5-4518-a807-753dc9302508) - Add ![image](/attachments/772bf9ba-5545-4399-8560-ba26471f9ab5) - Set management ![image](/attachments/4e784df5-8623-417a-a595-3407e420ae45) - Badge (I'm running out of default colors 🙃) ![image](/attachments/779bd785-353a-4b90-b418-a9ded861a5fc) ![image](/attachments/102939d0-7677-4312-b5fd-52b3f21b79d6) ![image](/attachments/fef3b9dc-a100-4e80-a0c2-3eb28ae71801)
image.png
105 KiB
image.png
54 KiB
image.png
40 KiB
image.png
441 KiB
image.png
34 KiB
image.png
20 KiB
gregoo commented 2025-02-03 16:58:34 +01:00
Contributor
Copy Link
Copy Source
  • Grid filtering

image

- Grid filtering ![image](/attachments/536e9c26-e9e1-4397-8bfc-cf818a153c18)
image.png
11 KiB
gregoo commented 2025-02-03 17:06:35 +01:00
Contributor
Copy Link
Copy Source
  • Grid search

image

- Grid search ![image](/attachments/0aba41b6-6f12-42e4-821e-d7c61a12125f)
image.png
151 KiB
gregoo commented 2025-02-03 22:43:01 +01:00
Contributor
Copy Link
Copy Source
  • Content of storage

image

- Content of storage ![image](/attachments/860262b3-665c-4281-9b1f-ee2271a713c7)
image.png
250 KiB
gregoo commented 2025-02-03 23:37:50 +01:00
Contributor
Copy Link
Copy Source
  • Storage list

image

- Storage list ![image](/attachments/e84884df-516f-4786-be8c-a794235f1c56)
image.png
59 KiB
gregoo commented 2025-02-04 12:30:13 +01:00
Contributor
Copy Link
Copy Source

Set purchase location

  • Admin

image

  • Set

image

  • Badge

image

  • Filter

image

Set purchase location - Admin ![image](/attachments/ecb9e05b-543d-47fd-892b-4fd8bbe65bc5) - Set ![image](/attachments/48e96384-a9e1-4178-8b45-039ef623351e) - Badge ![image](/attachments/7ff1e491-7efe-4952-b77e-f6c51d6a345b) - Filter ![image](/attachments/e143806e-83cf-4cd0-81de-b9ba3bfa0195)
image.png
28 KiB
image.png
19 KiB
image.png
44 KiB
image.png
368 KiB
gregoo commented 2025-02-04 16:54:16 +01:00
Contributor
Copy Link
Copy Source

More purchase fields (the currency symbol is controlled by an environment variable)

  • Management

image

  • Badges

image

image

  • Sort

image

More purchase fields (the currency symbol is controlled by an environment variable) - Management ![image](/attachments/7655e857-6c08-46fe-bd41-bc9a5d9b3ed8) - Badges ![image](/attachments/4a205816-618d-4588-9614-34c9a4584e68) ![image](/attachments/718c5c4e-e634-4f64-a923-8381123d8cc7) - Sort ![image](/attachments/3de58ef2-3a1e-42e1-8ab1-f247b603ed45)
image.png
53 KiB
image.png
448 KiB
image.png
16 KiB
image.png
219 KiB
gregoo commented 2025-02-10 16:46:20 +01:00
Contributor
Copy Link
Copy Source

Implemented in 1.2.0

Implemented in `1.2.0`
FrederikBaerentsen moved this to Done in General Improvements on 2025-09-15 20:42:29 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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/Feature
Milestone
No items
No Milestone
Projects
Clear projects
No project General Improvements
Assignees
Clear assignees
FrederikBaerentsen
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#41
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?