=========
Distiller provides convenient auto-extraction of document key words
based on term-frequency/inverse-document-frequency (TF-IDF) and word
positioning.
Distiller handles all of the pre-processing details and produces final
statistic reports in JSON format.
Requirements
------------
Distiller uses the [Natural Language Toolkit](http://www.nltk.org/)
You will need to download a couple of NLTK packages:
>>> import nltk
>>> nltk.download()
Downloader> d
Download which package (l=list; x=cancel)?
Identifier> maxent_treebank_pos_tagger
Downloader> d
Download which package (l=list; x=cancel)?
Identifier> stopwords
Installation
------------
Installation using pip:
$ pip install Distiller
Usage
-----
Typical usage from within the Python interpreter:
>>> from Distiller.distiller import Distiller
>>> distiller = Distiller(data, target, options)
Arguments
---------
### data
Path to file containing the document collection in JSON format.
{
'metadata': {
'base_url': 'The document's source URL (if any)'
},
'documents': [
{
'id': 'The document's unique identifier (if any)',
'body': 'The entire body of the document in a single text blob.',
}, ...
]
}
###target
Path where Distiller will output the following reports:
keywords: A list of words and the frequency with which they were detected as being keywords of documents.
bigrams: A list of word pairs and the frequency with which they were detected as being key pairs in documents.
trigrams: A list of word triples and the frequency with which they were detected as being key pairs in documents.
docmap: A mapping of document IDs to their respective keywords, n-grams, and other statistics.
keymap: A mapping of keywords to the documents they appear in.
###options
An optional dictionary containing document processing arguments in this format:
{
'normalize': True, # normalize tokens during pre processing
'stem': True, # stems tokens during pre processing
'lemmatize': False, # lemmatize during pre processing
'tfidf_cutoff': 0.001, # cutoff value to use for term-freq/doc-freq score
'pos_list': ['NN','NNP'], # POS white list used to filter for candidates
'black_list': [] # token list used to filter out from candidates
}
Metadata
Release files for Distiller 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Distiller-0.1.2.tar.gz | 9.1 kB | Without provenance | Details for Distiller-0.1.2.tar.gz |
Release files / Distiller-0.1.2.tar.gz
| Download URL | Distiller-0.1.2.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da39278ec9a88ef5d529bbc165775c431afa04818f278960a38138b43cc9c366
|
|
BLAKE2b-256 checksum How to use checksums |
a601cf449be1cd09e817e8bb9a9dd310fb7a0c3d493ecf6a1f62f7099e574fa4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Distiller 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.