You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You don't have to put my name on the workshop if you don't want, you really did all of the work here, and we are not co-presenting :-) I am there mostly as your primary support person. Up to you, but don't feel that you need to have my name there
For your "Overview" section, Lisa would like us to have a "Learning Objectives" section; perhaps rework this with more learning-objective language - maybe combine with contents? I believe this week we discussed learning objectives sections having bullet points in them.
In "Setup and Installation", we are doing installs on everything the night before, and putting information about installations in a separate area in the Gitbook (all together). We are also not using pip, but conda install. If things run the way we are planning them to, we have ensured that they have clean installs and everything they need by the time they come to the workshop; this part of your workshop is not necessary. Talk to Hannah and Patrick about the installation part of your workshop, and see what they need from you.
In the "Corpora" section, mention that POS tagging stands for part-of-speech tagging overtly - not everyone can get to that abbreviation on their own.
In the same section, the paragraph starting "There has been some research..." should be explained a bit more thoroughly. You introduce the research problem of if short-form platforms have decreased linguistic complexity very quickly, and you solve the problem very quickly, using terminology that you haven't yet introduced (such as function words), and with a hypothesis that hasn't been laid out very clearly. You may want to either simplify this example, or expand it to make it more accessible to people who are encountering this for the first time.
*That section ends with an incomplete sentence - "If we are only comparing function words"
In the "Data Cleaning" section, you may want to define stop words, lemmas, and normalized forms.
The text was updated successfully, but these errors were encountered:
You don't have to put my name on the workshop if you don't want, you really did all of the work here, and we are not co-presenting :-) I am there mostly as your primary support person. Up to you, but don't feel that you need to have my name there
For your "Overview" section, Lisa would like us to have a "Learning Objectives" section; perhaps rework this with more learning-objective language - maybe combine with contents? I believe this week we discussed learning objectives sections having bullet points in them.
In "Setup and Installation", we are doing installs on everything the night before, and putting information about installations in a separate area in the Gitbook (all together). We are also not using pip, but conda install. If things run the way we are planning them to, we have ensured that they have clean installs and everything they need by the time they come to the workshop; this part of your workshop is not necessary. Talk to Hannah and Patrick about the installation part of your workshop, and see what they need from you.
In the "Corpora" section, mention that POS tagging stands for part-of-speech tagging overtly - not everyone can get to that abbreviation on their own.
*That section ends with an incomplete sentence - "If we are only comparing function words"
In the "Data Cleaning" section, you may want to define stop words, lemmas, and normalized forms.
The text was updated successfully, but these errors were encountered: