Replace column_name with field_name in data dictionary

[wavingtowaves]

*Term to change: column_name and column_long_name Submitter: Rob Crystal-Ornelas Justification: Aligning with terms in FLMD and CSV reporting format. Right now we call the CSV headers field_names and in the CSV data dictionary we switch to these being called column names. Should we use the term field_name instead?

I suggest the following changes (leave blank whatever would not change):

• Term name: field_name and field_long_name
• Definition of the term:
• Format of the term:
• Additional Instructions (recommendations regarding content, etc.):
• Examples:
• Refines (name of the broader term this term refines, if applicable):
• Replaces (name of the existing term that would be replaced by this term, if applicable): column_name and column_long_name

[tvelliquette]

@robcrystalornelas I think all of the instructions may need a new read through to go along with the replacement to "field_name" as well as the addition we had with data presented with field_names horizontally or vertically.

Once we get consistency across the reporting formats, the instructions will again need a good review.

[regnans]

Could "variable_name" be an option? Suggesting this following from Charu's comment in the CF meeting that field_name could be confusing. I agree with that - often temporary "field names" are used, and then are replaced in final data. e.g. a plant species that has not been formally identified "in the field".

[tvelliquette]

For me, field_name made sense from database terminology perspective. Variable was used early on and then it morphed to column but with the addition of the horizontal/vertical presentation of data, column name no longer made sense thus field_name was introduced. Variable to me implies the data part of the matrix but the doesn't necessarily fit for site, notes, dates, collection_codes, etc. although variable_name may be the term most familiar to this community. Arctic Data Center uses that term. Then there is the proposed column/row_name that came up today.

[wavingtowaves]

Yes, as Terri said, variable_name was what we had in mind originally, but because not all of the column names are variables, we switched that term out for the current field_name. Now we can consider whether providing the options of column_name or row name would be clearer than field_name, while still allowing the flexibility to let these names be variables or other information..

On Mon, Mar 8, 2021 at 10:50 AM Terri Velliquette notifications@github.com wrote:

For me, field_name made sense from database terminology perspective. Variable was used early on and then it morphed to column but with the addition of the horizontal/vertical presentation of data, column name no longer made sense thus field_name was introduced. Variable to me implies the data part of the matrix but the doesn't necessarily fit for site, notes, dates, collection_codes, etc. although variable_name may be the term most familiar to this community. Arctic Data Center uses that term. Then there is the proposed column/row_name that came up today.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ess-dive-community/essdive-file-level-metadata/issues/13#issuecomment-792988330, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADTX7SLEMCEBYLSAL3HAO6TTCUL7XANCNFSM4YP3APLQ .

-- Rob Crystal-Ornelas, PhD Postdoctoral Scholar Lawrence Berkeley National Lab | ESS-DIVE Pronouns: he/him/his

[regnans]

Yep, understand. Alternatively, a variable could be a data variable or a metadata variable. Sometimes the line between what is data and metadata gets quite blurry to me. However, I am sure there are numerous technicalities on this that I am unaware of - very happy to defer to the experts. From my pov as a user clearly explaining the use and definition of whatever term is decided on is the most critical part.

[tvelliquette]

related to issue #16

[wavingtowaves]

We have updated this element of the data dictionary to Column_or_Row_Name so I'm now closing this issue.