subcommand to create an empty sheet

[xrotwang]

see https://github.com/glottobank/Grambank/issues/308

[HedvigS]

(Potentially with the empty column "contributed_datapoints")

[HedvigS]

Is this working as planned now, populating grambank/For_coders with a tsv sheet?

If so, we should remove

GramBank_most_updated_sheet.xlsx
GramBank_most_updated_sheet-21-Dec-2017.xlsx
GramBank_most_updated_sheet-20-Aug-2018.xlsx
GramBank_most_updated_sheet-11-Nov-2017.xlsx

[xrotwang]

Well, as far as I can see nobody used a sheet created by this command yet - so I don't know if it's working as planned. The command could also become more comfortable, e.g. filling in Language_ID automatically, which it isn't doing at the moment.

[HedvigS]

I'm sorry, I don't understand. There is no tsv-sheet in grambank/For_coders of this kind. I thought you meant that the cldf-function would populate the For_coders folder with an updated sheet with the latest summaries from the wiki.

No coder has been told to look for empty sheets anywhere else but in the For_coders folder.

[HedvigS]

I don't think we can expect our coders to use pygrambank.

[xrotwang]

I see. Can you do this? What info from the wiki should go into the sheet?

[HedvigS]

I'm sorry, no I cannot to this, at least not now. I thought that the PR you made would do this, but we were misunderstanding each other.

The info from the wiki per feature that should go into the sheet is the section with the title "Summary". This section is marked as

##Summary

In all the relevant wiki pages and there is always a section called "## Procedure" right after.

[xrotwang]

What if we replace the Summary or Clarifying comments column with a link to the wiki page? Spreadsheet cells with long text content tend to be hard to read, no?

[HedvigS]

Coders do use these cells for fast look up while they're coding, especially if they're in a place with no internet. We'd have to poll them to find out how a change like that would be received.

@alenawitzlack @tobiaskweber @Jaylatarche @RobHerrera do you think it'd be a good idea to remove the columns "Summary" and "Clarifying comments" from the empty "most up to date" sheet and rely entirely on the wiki?

[xrotwang]

Ok. Leaving this info in is not a problem on my side. "Summary" and "Clarifying comments" is the same thing, though.

Hedvig Skirgård notifications@github.com schrieb am Sa., 5. Okt. 2019, 02:01:

Coders do use these cells for fast look up while they're coding, especially if they're in a place with no internet. We'd have to poll them to find out how a change like that would be received.

@alenawitzlack https://github.com/alenawitzlack @tobiaskweber https://github.com/tobiaskweber @Jaylatarche https://github.com/Jaylatarche @RobHerrera https://github.com/RobHerrera do you think it'd be a good idea to remove the columns "Summary" and "Clarifying comments" from the empty "most up to date" sheet and rely entirely on the wiki?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/glottobank/pygrambank/issues/7?email_source=notifications&email_token=AAGUOKHOW2NAJHLBZLIK6STQM7KL3A5CNFSM4IXMV4L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEANFB7I#issuecomment-538595581, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGUOKHD2TSR63SVNBMIAVLQM7KL3ANCNFSM4IXMV4LQ .

[HedvigS]

Leaving that info in would be better then, thanks.

Ah, sorry. Harald has been populating "Clarifying comments" with "Summary". They used to be different things but now aren't. All good, thanks!

Just so we're on the same page, the columns in this empty sheet should be

• Language_ID
• Grambank_ID
• Possible Values
• Value
• Source
• Comment
• Contributed_datapoints
• Clarifying comments
• Relevant unit(s)
• Function
• Form

We could also add in Eri's order which some people like for convenience during coding. .

Does that sound alright?