0x1211 / linkedin-messages

A CLI tool to parse exported LinkedIn messages CSV file to discussion TXT files.

LinkedIn Messages

A CLI tool to parse exported LinkedIn messages CSV file to discussion TXT files.

How to get data from LinkedIn

https://www.linkedin.com/psettings/member-data

Problem

:contruction: Work in progress 🚧

Parser Steps

// ***************************** PARSER PROCESS ********************************
// **** 1. Map file through a stream to an array (note: file is provided via cli)
// **** 2. Group array by FROM prop
// **** 3. For each object map to corresponding answers (hint: use TO column)
// **** 4. For each conversation reorder items by DATE
// **** 5. For each conversation, streamwrite to a txt file
// **** 6. Exit program
// *****************************************************************************

Model

Message

Here is how a LinkedIn message is actually represented:

{
  FROM,
  TO,
  DATE,
  SUBJECT,
  CONTENT,
  DIRECTION,
  FOLDER
}

linkedin-messages's Issues

📝 (docs) Update README with proper documentation

This repository stands for a CLI tool and therefore requires some proper documentation.

☑️ To Do

Introduction section: what and why

• What is this tool ?
• Why this tool ?
  • How to download your LinkedIn Messages archive
  • Representation of LinkedIn Message data model
  • Why this tool was created

Getting started section

• How to install

User Guide section

• How to use
  • Command line example
  • CLI parameters description

🌈 Nice to have

• A word on Contribution (and a Contributing.MD file)
• A link to some Code of Conduct (and a Code of Conduct.MD file)
• GitHub Pages

✨ (feature): Date flags to output messages within a time range

ℹ️ Context

linkedin-messages currently handles a whole messages file without considering any message date. Therefore if we would like to only get messages from year 2019 or from March 2018 we can not get them yet.

🌈 Nice to have

It would be great to use CLI parameters to pass in some date parameters in order to define a date range. Example given as:

linkedin-messages --src some/src/file/path --dest some/dest/dir/path --start-date 01-2018 --end-date 03-2018

should output messages from january 2018 to march 2018.

✨ (feature): Add --dest output path parameter management

ℹ️ Context

Our CLI tool handles two parameters:

  --src      which is the input file path (the user messages CSV file)
  --dest     which is the output path where linkedin-messages will create and fill its output directory

The program will create a linkedin-messages/ folder in --dest output path to populate it with its messages files.

⚠️ Issue

Currently if no output path is set or if directory does not exist in the path (e.g. /my/path/linkedin-messages) the program will fail.

✨ Solution

We shall cover these cases as:

• if no output directory is set, create a linkedin-messages/ directory in the current working directory
• if an output directory is set, create a linkedin-messages/ directory in the output directory
• if an output directory is set and a linkedin-messages/ directory does exist the program will override it unless a CLI parameter tells not to do so (e.g. --no-dest-override)