Skip to content

A software component that uses TF-IDF statistical analysis of the words in files to extract the 10 most important terms in a document and provide a short, 5 sentence summary.

License

TechBorn99/tf_idf

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

TF-IDF statistic

Intuitively, a term is more important if it occurs more frequently in a document. However, some common words will appear frequently in nearly all documents in a corpus. Therefore, the TF-IDF metric has two parts - term and document frequency.

The number of times a term occurs in a document is called its term frequency.

Each term is a single stem of a word, and two words are considered to be the same term if their stems match. For example, "think" and "thinking" are considered the same term because their stem is "think", but "rethink" and "thinker" are not. Libraries that remove morphological affixes from words, leaving only the word stem, are called stemmers. For the purposes of this implementation, SnowballStemmer from the NLTK library was used.

Document frequency is defined as the number of documents in a corpus that contain at least one occurence of the given term.

The inverse document frequency is then calculated as idf(t) = log(N/k(t)), where N is the number of documents in the corpus, and k(t) the number of documents that contain the term t. (For this implementation, defining the metric in the special case when k(t) = 0 was not considered.)

Finally, the TF-IDF metric of a term in a document that's part of a corpus is obtained by multiplying its TF and IDF metrics.

Input

In this implementation, inputs are given through the standard input.
The first input line should contain the path to the folder which contains the corpus of documents.
The second input line contains the path to the *.txt document that needs to be analyzed.

Within the corpus folder, there can be multiple subfolders, each containing one or more *.txt files, which are all part of the corpus. An example is given below.

<corpus_folder>/
├──<subfolder_1>/
│        ├──example_file_0.txt
│        ├──example_file_1.txt
│        └──example_file_2.txt
├──<subfolder_2>/
│         ├──example_file_3.txt
|          ├──<subfolder_3>/
│         │        ├──example_file_4.txt
│         │        └──example_file_5.txt
|          └──<subfolder_4>/
│                   └──example_file_6.txt
└──<subfolder_5>/
          └──example_file_7.txt/
          └──<subfolder_6>/
                    └──example_file_8.txt

Some assumptions are:

  1. The names of all folders and *.txt files in hierarchy can take arbitrary values.
  2. There will be at least one *.txt file in the hierarchy of each subfolder.
  3. Each *.txt file is encoded using UTF-8 encoding.
  4. Input text sequences can contain leading and/or trailing spaces.
  5. Input text sequences are not empty.

Example input:

Insert the path to the corpus: ...\corpus
Insert the path for the file that ...\corpus\goose\Domestic goose.txt

An example corpus folder is provided as corpus-example in the project structure.

Output

All results are printed to the standard output.
Results for each document are printed in form:

Keywords:
<top_10_most_important_terms>
Summarized document:
<5_sentence_summary>

Top 10 most important terms are printed in a single line that consists of comma-separated terms (ex. "term1, term2, ..., term10"). Result is printed in the order given by the TF-IDF score, from most to least significant. When multiple words have the same score, they are ordered lexicographically.

The resulting list of 5 sentences is printed to the standard output in a single line. The sentences are separated by a single space (ex. "Sentence1. Sentence2. ... SentenceN."). The order of the sentences ais the same as in the original document. If multiple sentences have the same score, the higher priority is assigned to the sentence that comes earlier in the document.

Example output:

Keywords:
hors, breed, poni, domest, bone, anim, ride, equus, inch, mare
Summarized document:
These feral populations are not true wild horses, as this term is used to describe horses that have never been domesticated, such as the endangered Przewalski's horse, a separate subspecies, and the only remaining true wild horse. All horses move naturally with four basic gaits: the four-beat walk, which averages 6.4 kilometres per hour (4.0 mph); the two-beat trot or jog at 13 to 19 kilometres per hour (8.1 to 11.8 mph) (faster for harness racing horses); the canter or lope, a three-beat gait that is 19 to 24 kilometres per hour (12 to 15 mph); the gallop, which averages 40 to 48 kilometres per hour (25 to 30 mph), but the world record for a horse galloping over a short, sprint distance is 70.76 kilometres per hour (43.97 mph).Besides these basic gaits, some horses perform a two-beat pace, instead of the trot. Sometimes "hot-bloods" are classified as "light horses" or "riding horses", with the "cold-bloods" classified as "draft horses" or "work horses". "Hot blooded" breeds include "oriental horses" such as the Akhal-Teke, Arabian horse, Barb and now-extinct Turkoman horse, as well as the Thoroughbred, a breed developed in England from the older oriental breeds. "Warmblood" breeds, such as the Trakehner or Hanoverian, developed when European carriage and war horses were crossed with Arabians or Thoroughbreds, producing a riding horse with more refinement than a draft horse, but greater size and milder temperament than a lighter breed.

Requirements

Python version 3.x and Natural Language Toolkit (nltk) library.

How to install NLTK

To install NLTK, Python pip can be used: pip install nltk.
Then, to import it, type in the Python interpreter: import nltk.
Finally, to install required packages from NLTK, it's downloader can be used with this command: nltk.download('punkt').

About

A software component that uses TF-IDF statistical analysis of the words in files to extract the 10 most important terms in a document and provide a short, 5 sentence summary.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages