Solverz-0

This feature would be great to have, exactly as Snipe as stated below! > You don't actually have to set either of those things. They're both optional. > > We...

> I've done a simple hack of the version 4.9.2, so that when we check-out, we can still check-out to a user and assign the asset to an alternate location....

> Use custom fields. That’s what they’re there for. That would become tricky and is prone to error and would mean there are two location fields, custom one and standard...

> There are already two. RTD (ready to deploy) location and actual location. I’m not sure a third would be a great idea. I am guessing the RTD location is...

@snipe Just to add to my previous comment. Making it behave like it does when checking in an asset, where you can change the actual location on check-in no matter...

> I'm still kind of unclear on the use case here. > > We provide two location fields, Default Location (where the asset is when it's unassigned) and Location (which...

> That makes sense, I'm just honestly not sure how to have it without it very potentially screwing up data later on, since we _do_ that inheritance process for assets....

> BTW, do not confuse the `pkgconfig` python package and the `pkg-config` commandline tool (which is required and used by the python package). Okay thank you but what dependencies can...

> ``` > apt install pkg-config > ``` Can these dependencies not be installed in the Virtualenv? (Sorry if this obvious question) Or is the Virtualenv just for python libraries?

These are some good points thank you. I have gave the metadata option a go, how you explained and they do help in replacement of the mentioned "standard fields". However...