Editing Twitter Analysis DB
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
= Goal = | = Goal = | ||
− | This document | + | This document is new, the software is alpha but "works" Look at history tab to see what is going on. |
Twitter Analysis DB is a Python open source, program and an accompanying database, running in a Graphical User Interface tool ( and/or database creation tool ) for the analysis of a body of tweets. Currently the program is in early alpha and its design goals are evolving at least as fast as the code is being written. | Twitter Analysis DB is a Python open source, program and an accompanying database, running in a Graphical User Interface tool ( and/or database creation tool ) for the analysis of a body of tweets. Currently the program is in early alpha and its design goals are evolving at least as fast as the code is being written. | ||
Line 32: | Line 32: | ||
* Overall structure seems sound and extensible. | * Overall structure seems sound and extensible. | ||
* Should be relatively easy to add additional queries, joins, columns, select criteria, without massive coding effort. | * Should be relatively easy to add additional queries, joins, columns, select criteria, without massive coding effort. | ||
− | * But.... it is full of | + | * But.... it is full of rough edges. Almost nothing has been polished up. Cited for improvement: |
− | ** Clean up tweet in the database build stage. | + | ** Clean up tweet in the database build stage. Much "junk" like odd Unicode characters need to be managed. |
** User interface is evolving but still not as user friendly as I would like. | ** User interface is evolving but still not as user friendly as I would like. | ||
− | ** | + | ** Report == Selects are more demos of what is possible than what is truly useful and informative. |
− | ** | + | ** Biggest db so far has 300K words and only Trump tweets for this year. Need to do a bigger db load, see how sqlite holds up. |
− | ** No database optimizations yet.... I run on ram drive for speed | + | ** No database optimizations yet.... I run on ram drive for speed |
− | ** Report formatting is basic, but workable. Nicest overall format for human readability is probably "html", best to pass to other applications is probably "csv", most responsive in time is "msg" -- sent to message area | + | ** DB is about 20 MBytes so not so bad |
+ | ** Report formatting is basic, but workable. Nicest overall format for human readability is probably "html", best to pass to other applications is probably "csv", most responsive in time is "msg" -- sent to message area ( implementation delayed due to unicode problems ) | ||
** Not sure what area of work is most useful, have been driven lately by programming challenges need to focus for a bit on improving usefulness. | ** Not sure what area of work is most useful, have been driven lately by programming challenges need to focus for a bit on improving usefulness. | ||
− | ** Still printing | + | ** Still printing lots of junk used in debugging, remove most... if output is needed send to py_log |
'''What technical knowledge should users have ( and How ):''' | '''What technical knowledge should users have ( and How ):''' | ||
Line 127: | Line 128: | ||
| get your own log files ... all typically named xxx.py_log | | get your own log files ... all typically named xxx.py_log | ||
| | | | ||
− | | --> input | + | | --> input --- input files used to build the database. |
− | | --> output | + | | --> output --- files produced by the database selects. |
− | | --> images | + | | --> images --- image files, mostly screen shots, icons... or what ever, not important for the code. |
− | | --> wiki_etc | + | | --> wiki_etc --- various files documenting program, including at least some of the material from this wiki |
− | | | + | | also some sample output files |
− | | --> help | + | | --> help --- help files, documentation for various selects |
− | |||
Put them in your system making "....whatever" anything convenient for your Python installation ( that is move the files to where you keep your Python source, not your installed module location ). | Put them in your system making "....whatever" anything convenient for your Python installation ( that is move the files to where you keep your Python source, not your installed module location ). | ||
Note that there may be a certain amount of left over, dead code, in the directories I am cleaning out bit by bit, someday it may be nice and neat. For now if you want to tinker look at the design info below first. | Note that there may be a certain amount of left over, dead code, in the directories I am cleaning out bit by bit, someday it may be nice and neat. For now if you want to tinker look at the design info below first. | ||
− | |||
− | |||
== Run == | == Run == | ||
− | Run it until it stops complaining about dependencies ( in the console ), after that ( and perhaps even before ) the GUI should come up. You are installed. | + | Run it until it stops complaining about dependencies ( in the console ), after that ( and perhaps even before ) the GUI should come up. You are installed. |
− | I have run the program on both Windows 10. It should work in most OS's | + | I have run the program on both Windows 10 and Rasperian on a RPi. It should work in most OS's. Let me know about issues. |
= Configure to Run = | = Configure to Run = | ||
Line 206: | Line 204: | ||
*[[Python Desk Top Applications]] | *[[Python Desk Top Applications]] | ||
*[https://github.com/russ-hensel/twitter_analysis_db GitHub Repository] | *[https://github.com/russ-hensel/twitter_analysis_db GitHub Repository] | ||
− | |||
<!----------- | <!----------- |