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.
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:
users.jsonfile which contains things like first name / last name which would be handy to use. Not all users havefirst_namelast_nameproperties, some havereal_name(which are sometimes just the nickname).user(ID keyed tousers.json) and atextproperty.tsfor timestamp. In text, referenced @users use<@___ID___>format, these need to be replaced out.subtype. E.g.subtype: channel_joincan be translated toPERSON enters.