![]() However, people also made threaded replies to some of those messages. The channel's main messages on March 9 began at 4:27pm, and ended at 4:31pm. In the above example, there is a chat document containing messages from a channel on March 9. This is akin to files attached to an email message. This means that the starting time and ending time of each chat document properly aligns with the times the emails in your database were normalized at, providing consistency within your database.Īdditionally, each Slack thread ( i.e., an inline reply to a Slack message plus any further messages in that same direction, as opposed to another message in the main channel) is broken into its own documents in DISCO, and each document represents a single calendar day of messages in that thread.įinally, attachment files in a channel/set of DMs are added as family member children documents to the chat document containing that day's messages. That calendar day begins at midnight of the time zone to which your DISCO database was set. Additionally, DISCO is taking a small number of files that you downloaded from Slack and turning those into many chat documents in DISCO, with a new document for each day of messages from each channel or each set of direct/group messages.Įach chat document in DISCO represents a single calendar day of messages from a single channel or set of direct (or group) messages. However, in the background, DISCO is also collecting the needed attachment files from your Slack server. The processing of your documents will appear to occur much the same as any other ingest into DISCO. How is information broken up into documents? And what relationships are applied between documents? The size of those attachment files is not known until they are obtained.įor more details on collecting your data from Slack and ingesting it into DISCO, please also refer to this article. However, the second item is not something you'll know ahead of time, because DISCO's processing of the files in the ZIP initially obtained from Slack is what determines which attachment files will be further downloaded from Slack. The first item is something you'll easily know ahead of time, because it is simply the file size from the ZIP file. Note: The billed size of the ingest depends on two items: (i) the size of the ZIP file contents from Slack, and (ii) the size of the attachments downloaded. If it is de-selected, then the contents of attached files will not be in your DISCO database, and will thus not be able to be searched, reviewed, or produced. Note: DISCO strongly advises keeping the "Download slack attachments" option selected. Keeping this option selected allows DISCO's software to retrieve those attachments and properly include them as family member documents with your chat documents. All of those files are stored in a separate location by Slack. This includes items such as pictures, PDFs, Office files, etc. The ZIP file downloaded from Slack contains the message content and metadata from Slack, but it does NOT contain attachment files that were added to the messages. Next, on the Ingest options page, you'll again find the familiar options, plus one new option: "Download Slack attachments". The latest version of DISCO's High Speed Uploader is required for support. Note: Update for October 2, 2023: The Enterprise Grid version of Slack is supported by Chat Streams. DISCO's Chat Streams feature supports the direct export from Slack, unmodified. On the File selection page, select the ZIP file which you've downloaded from Slack. Select "Exported ZIP file", and you'll then be taken to your familiar DISCO ingest options, where you'll name your ingest session, and choose whether to send your data directly to active review or into ECA. Select "New ingest", then "Slack" from the "Cloud service" category. Ingesting an export from Slack into DISCOĭISCO's Chat Streams feature first presents itself on the ingest page. Alongside the simple user-level ingestion capability, we've also included powerful deduplication logic, standardized metadata fields for use in search, review, and production, and simplified navigation tools for moving within a Slack channel or a set of direct messages (DMs). The new features allow for data exported from Slack's built-in export functionality to be directly ingested into DISCO. Slack is the first type of data that is supported within Chat Streams. This feature is in Walk as of Tuesday, September 26, 2023.ĭISCO has released a new suite of features, Chat Streams.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |