Approaching quantitative signatures that have a range of values

[Jonathan Ye]

Example: the length datasheet contains attribute values such as 5-10.

@sdgamboa had the idea to split this signature into several rows, with values 5-10 instead of keeping the singular row. Do we want this? If so, how would we approach decimal ranges such as 0.3-10.0?

[Jonathan Ye]

@lwaldron any thoughts? The main concern is that keeping a range of values changes the data type to character due to the "-"

[Levi Waldron]

The most formally correct and what should be required as return values by the bugphyzz import function is minimum and maximum as separate attributes, to keep the same tidy format with numeric attribute values (no hyphens or extra columns). However we use the bugphyzz software to read these sheets and do potential extra cleanup, to allow leaving some things for cleanup at import time when it is more practical that way.

[Jonathan Ye]

I see, separating the range into two columns would be better than rows, now that I think about it. Should I go ahead and make these changes to the sheets, or will this problem be fixed through the bugphyzz software down the line? I can make a copy of each sheet and change the values where applicable.

[Jonathan Ye]

I went ahead and completed the sheets link. @lwaldron do I have permission to replace the original length and width spreadsheets?

[Kelly Eckenrode]

@JonathanYe3 Looks great to me, and based on last week's meeting, I think you are all set to replace.

[Jonathan Ye]

Awesome, thank you! For now, I think we should keep the old spreadsheet just in case, and replace the link in ~/source_links.tsv

[Samuel Gamboa]

Closing. See #195