please close this issue when you are ready for Nick to review your preliminary analyses and deliverables

[nicholasjhorton]

The aspirational goal for today is that you've substantially completed both of your main analysis goals for your selected book. (I realize that some of this remains unfinished, particularly if you have a complex Shiny app in development.)

I want to ensure that you have timely feedback that you could incorporate before your submission on March 15th. This issue is intended to let me know how I can help you.

• what should I review?
• what issues/questions do you have?
• how can I assist?

While my hope is that you can finish things up today, if you need to take until Saturday to provide this information and close this issue, that would be fine.

In the interim, please comment and update other issues as appropriate.

Good luck with all you are juggling: I look forward to seeing your results (even in preliminary format).

[arogers24]

@nicholasjhorton This morning, I've made some commits to my app.R. I've written it so it prints a data table of the part of speech, a scatter plot of frequency per chapter, and made the scatter plot interactive. When the user clicks on a point, the text of the chapter prints below. My next step is to annotate this, and I'm wondering if you have suggestions. My idea is to replace the tokenized text with bold HTML bounds if the part of speech matches, then paste that column. My only worry is that this won't keep the paragraph structure. I guess I can add newlines when the document number increases. What are your thoughts?

Also what do you mean by both of my main analysis goals? I've been pushing on the Shiny app, but what else should I be working on? I'll be a bit busy this weekend since I have a thesis presentation on Tuesday.

[nicholasjhorton]

Good luck with your thesis presentation! I hope that all continues to proceed well on that front.

I've been encouraging people to have some form of text analytics (in a report or similar) as well as a Shiny app (that features the text). In an ideal world, these might be integrated, but that's not necessary.

I'll try to take a look at the app. I suspect that your proposal to keep track of the document number would be a good solution.

Please let me know if you have specific questions or if there are other ways that I can be of assistance.

[arogers24]

Thank you!

I can put together some form of written analysis to complement the app, but that may come after tomorrow. My plan would be to document my exploration of the data. The narrative would be 1) textual analyses highlighting different writing styles, 2) exploration of what the differences are in terms of parts of speech, NER, topic modeling(?), and 3) creation of the shiny app to allow user exploration

I also have access the the whole chapter from my data package. I was wondering if there was a way to find the verbs by matching that to the tokenized data table, but that may be unnecessary. I think I would have to split that by word, match, then combine again. It makes more sense to paste the tokenized text after some function to pad verbs with .

[nicholasjhorton]

Please take the time you need. There’s flexibility on my end. All the best for the weekend and your work. NickOn Mar 8, 2024, at 3:12 PM, arogers24 @.***> wrote: Thank you! I can put together some form of written analysis to complement the app, but that may come after tomorrow. My plan would be to document my exploration of the data. The narrative would be 1) textual analyses highlighting different writing styles, 2) exploration of what the differences are in terms of parts of speech, NER, topic modeling(?), and 3) creation of the shiny app to allow user exploration I also have access the the whole chapter from my data package. I was wondering if there was a way to find the verbs by matching that to the tokenized data table, but that may be unnecessary. I think I would have to split that by word, match, then combine again. It makes more sense to paste the tokenized text after some function to pad verbs with .

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[nicholasjhorton]

Any updates on this front? Is there anything that you'd like me to review?

[nicholasjhorton]

I look forward to reviewing your book submission.

just a reminder to let me know:

1. when you are ready for me to review your pre-spring break submission, and
2. where I can find what to review.

Don't hesitate to open other issues or share questions if you run into any issues before then.

[arogers24]

Hey @nicholasjhorton I just pushed my report. I was having trouble rendering HTML text and plotly output, so I rendered the report as an HTML doc. I apologize for the convenience, but you may have to render the report in order to see it in a clean format. If you have suggestion on how to fix this, I would be interested