hay-kot / homebox

Homebox is the inventory and organization system built for the Home User
https://hay-kot.github.io/homebox/
GNU Affero General Public License v3.0
2.71k stars 214 forks source link

Asset IDs: ability to generate a random identifier #764

Closed danielrosehill closed 9 months ago

danielrosehill commented 9 months ago

What is the problem you are trying to solve with this feature?

Currently the numbering system for asset IDs starts with 000-001. I believe that if you were to try force the system to start with a different starting number (say 0321) it would not continue sequentially with further asset IDs (e.g. automatically create the next item with ID 0322).

What is the solution you are proposing?

To increase flexibility, it would be nice to:

-> Be able to configure a different asset ID starting number. For example for people who are migrating from an existing inventory management system and they've already assigned IDs to everyTO increasthing up to 103 .. start generating asset IDs from 104.

-> Be able to choose between sequential asset IDs and random identifiers which would populate randomly at each asset generation, without duplication.

-> Be able to choose between different systems for asset IDs. For instance, four upper case characters (XDSE), numbers only, 3 digits, 4 digits. Etc.

What alternatives have you considered?

No response

Additional context

No response

Contributions

hay-kot commented 9 months ago

Be able to configure a different asset ID starting number. For example for people who are migrating from an existing inventory management system and they've already assigned IDs to everyTO increasthing up to 103 .. start generating asset IDs from 104.

We just take whatever the highest asset ID is and +1 to that so if you want to do this all you need to do is create an item and set the Asset ID to whatever you want to increment from.

-> Be able to choose between sequential asset IDs and random identifiers which would populate > randomly at each asset generation, without duplication.

-> Be able to choose between different systems for asset IDs. For instance, four upper case characters (XDSE), numbers only, 3 digits, 4 digits. Etc.

I don't know what real world use case this would solve. Do you have a specific problem that you're experiencing?

danielrosehill commented 9 months ago

@hay-kot

The four letter identifiers printed beneath a QR code system is quite commonly used in some "ready to roll" type home management systems so I figured it just might be something that people are already familiar and comfortable with.

But you're correct ... no burning need (especially as the functionality you described above seems perfectly sufficient!)

qr codes

hay-kot commented 9 months ago

Thanks for following up, going to close since there isn't a clear use case here. Thanks!