Open Teraskull opened 1 month ago
I've heard of this need from other users too.
"I think a separate ID for internal use and providing the user with the option to use their own would be beneficials.
For my use case, when I’m assisting users, I will request they give me the Asset tag of the Device. IE (KTOS06945) this is a lot easier for the user to read over the phone then a long string of random numbers and letters with no consistency. "
Contact Details
anton.grouchtchak@gmail.com
Is your feature request related to a problem? Please describe?
Our inventory is already labeled with our own QR codes and unique 6 digit asset IDs.
Would be great to have a basic
Asset ID
field that only allows unique values, and use it as a primary/secondary ID.For example, allow accessing the asset using that custom asset ID like this:
app.shelf.nu/assets/123456/overview
.Describe the solution you'd like
Add a basic
Asset ID
field to the asset and allow accessing the asset with only that asset ID.Here's a quick mockup of the field:
Describe alternatives you've considered
I have been testing https://github.com/hay-kot/homebox, but unfortunately, it's no longer being supported and developed.
The assets there can be accessed by
/item/<Asset UUID>
-homebox.fly.dev/item/66fed3c4-675c-4de3-b320-b5a2484fcc8a
But they can also be accessed by
/assets/<Asset ID>
-homebox.fly.dev/assets/000160
, which then redirects to the primary/item/<Asset UUID>
.The only downside here is that the
Asset ID
field is not unique, so it will return a list of all assets with the same asset ID if there are duplicate entries.Additional context
This will be useful for scanning existing QR Codes with the built-in scanner, and open the asset page if the asset ID exists.