Feature Request - add units to values of container dimensions

[Jegelewicz]

Is your feature request related to a problem? Please describe.

I did not know that all container measurements are required to be in cm - see ArctosDB/arctos#6427

Describe what you're trying to accomplish

Why do I have to convert to cm? Why can't this form accept any length units from the code table? https://arctos.database.museum/info/ctDocumentation.cfm?table=ctlength_units

Describe the solution you'd like

Add a units field for the length/width/height values in container dimensions

• See discussion, this is one new field, container_units, which applies to (length, width, height)

Additional context

1. See Request - Change the order of dimensions on object tracking so they are always in the same order arctos#8221 - order container dimensions as (length, width, height)
2. Same source: Splat-F depth - stick with (length, width, height), don't use alternative labels

[Nicole-Ridgwell-NMMNHS]

This would be useful.

[dustymc]

Not much opinion from me, but there are considerations.

1. It would add complexity - I'm not sure if you're asking for 1 or 3 fields, either way has its own problems. I suspect this is a significant impact on usability, but ??
2. It would add some cost - I'd have to convert before doing the volume comparison (but PG is very good at that sort of thing, probably not hugely significant).
3. I'd probably just report stuff in 'base units' - meters in this case (at least without some significant complexity, still probably)

And (4) means I might also lose some precision in the converting, but that's probably negligible.

[mvzhuang]

Well i currently plan in inches because all the external blueprints we get are in Imperial - so having to convert to CM for Arctos and then convert it back if I ever need that information again (which does come up occasionally) is impacting the usability of the feature. But the pt is it needs to be consistently up front across documentation if we just stick to CM. I've accidentally used inches twice now and had to go back and redo things.

1. If we go towards choosing own units, 1 additional units field should be enough. I doubt anyone would mix units across volume measurements. And main function as I see it is to make sure internal containers don't exceed external sizes and then provide info to future planners in a spot that makes sense and is easily accessible.
2. Shouldn't need to convert if just assuming everyone currently is on cm? People after can decide if they want to convert.

[dustymc]

Thanks @mvzhuang that seems pretty compelling.

re (2) - I'm not sure if it's displayed anywhere but I calculate volume for a check.

[Jegelewicz]

Suggest one unit field for all three length measurements.