-
Notifications
You must be signed in to change notification settings - Fork 185
Description
Where dimensions of an object are given in units other than lengths, these should be dealt with consistently in the JSON csv. Currently in a few cases aspects of these get recorded as width/height/depth
e.g. accession number T07479
Dimensions = "Duration: 8 min, 43 sec"
Width = "8"
Height = "min,"
depth = "43"
units = "sec"
e.g. accession number T12027
Dimensions = "duration: 1 hour loop"
width = "1"
height = "hour"
depth = ""
units = "loop"
e.g. accession number T07558
Dimensions = "overall: 1490 mm, 335 kg"
width = "1490"
height = "mm,"
depth = "335"
units = "kg"
In other cases information isn't parsed out:
e.g. accession number AR00576
Dimensions = "duration: 59min, 18sec"
width, height, depth, units = ""
Either should not parse out dimensions in these cases, or should parse to duration type fields (or maybe do the latter for csv and former for json?)