-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit form Physical Object section inputs should default to either metric or imperial/American, but not both. #2242
Comments
It should default to imperial (for now). Eventually, once we get proper localization we can make the default locale specific, but for now it should default to imperial. |
@cdrini Was there some rationale for choosing Imperial as the default? Even in the US, repository libraries principally use SI units for new records, while still supporting older records using Imperial. Other things being equal, it would seem to make sense to prefer units understood by the whole world, rather than just a fractional area. AMZ sites use the units customary to current business in a specific country, so amazon.de uses cm with the decimal comma (https://www.amazon.de/Tall-Tales-Wee-Stories-Connolly/dp/1529361338/) while amazon.co.uk and amazon.co.jp use cm with the decimal point (https://www.amazon.co.uk/Tall-Tales-Wee-Stories-Connolly/dp/1529361338/) and amazon.com uses both inches and pounds with the decimal point (https://www.amazon.com/Tall-Tales-Wee-Stories-Connolly/dp/1529361338/) Most of the AMZ sites (except the US one) omit the weight entirely, and where it is shown, it is sometimes for a boxed product shipping weight. For automated import, it would be simple enough to just accept the stated value and units in a source record: |
I'd favour metric, but would mostly favour consistency. |
Until we have proper i18n, we have to take into account that the majority of our users are in the US. That sucks, I know (I'm Canadian, we use metric (like normal people)). I actually don't think it will be super difficult to make this i18n-aware; we should try to make that work if possible; but if that's not easily achievable, I think we'd have to use imperial just to match expectations of the majority of our users :/ |
I favor metric as well. The current storage format is a concatenated string of all the dimensions, which is kind of silly, but we can fix that separately. I've created #2587 for that piece. |
I can handle the issue and set the default to metric. May I please get some code pointers. |
@manav014 (or anyone else), I believe the defaults are specified in the |
Hello, guys! Was the issue closed? If not, may I try to resolve this? |
@kazikhanmargulan if you feel like you have enough information to give it a try, feel free! EDIT: actually, it looks like we may have a PR open for this #4134 which @cdrini may wish to provide feedback on before we get started (sorry for putting the cart before the horse) |
Changed default inputs as kilos for weight and centimeters for dimensions.
I kind of did the exact same thing as was done on the mentioned issue commit. If you would want me to pull request it, let me know. |
Assignees removed automatically after 14 days. |
Description
The weight defaults to grams; dimensions to inches.
Evidence / Screenshot (if possible)
Relevant url?
Expectation
The default should be one system or the other. Ideally, the data would be appended, not overwritten if someone adds value of another type.
Details
Proposal & Constraints
Stakeholders
The text was updated successfully, but these errors were encountered: