Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse Slack message history into Fountain (basic) #2

Open
louh opened this issue Nov 22, 2017 · 2 comments
Open

Parse Slack message history into Fountain (basic) #2

louh opened this issue Nov 22, 2017 · 2 comments

Comments

@louh
Copy link
Member

louh commented Nov 22, 2017

Slack exports: https://get.slack.help/hc/en-us/articles/201658943-Export-data-and-message-history

At minimum write a very simple converter for messages to Fountain format (we'll do more complicated work later)

Observations:

  • Slack format has a standalone users.json file which contains things like first name / last name which would be handy to use. Not all users have first_name last_name properties, some have real_name (which are sometimes just the nickname).
  • Slack does not have gender pronouns (because why would they?) but knowing this would make stage direction and words exist better
  • Messages are grouped by channel / day
  • Messages are in an ordered array
  • Messages have a user (ID keyed to users.json) and a text property. ts for timestamp. In text, referenced @users use <@___ID___> format, these need to be replaced out.
  • Messages have a subtype. E.g. subtype: channel_join can be translated to PERSON enters.
@louh
Copy link
Member Author

louh commented Nov 22, 2017

@slifty Can you do a dump of channel history at https://thegpf.slack.com/services/export? And choose a small subset of chats to do a first pass on.

@slifty
Copy link
Member

slifty commented Nov 22, 2017

Yes -- but I'll be making sure we have permission from folks involved in whatever the channel is!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants