Aug-15-2017, 12:28 AM
(This post was last modified: Aug-15-2017, 12:28 AM by Mike_Marino.)
Hello! I’m a music composer and am looking to try to build an organizational database to keep better (and more in-depth) track of the music I create. I got referred to Python code by a friend of mine a couple of weeks ago. I’ve watched a lot of tutorials online (Sentdex’s youtube page) and am working through the “Automate The Boring Stuff with Python” e-book. I’ve been following along with the e-book and youtube tutorials in IDLE Python 3.6.2. as well as DB Browser for SQLite (3.9.1, Qt 5.7.1, SQLCipher 3.11.0). I’m on a Mac; OSX 10.9.5.
I’d like to build a piece of software that does the following:
* Displays info for each track: running track count, track titles, track metadata (i.e. genre, duration, tempo, key, music library/publisher, etc)
* I’d like the ability to either enter this information in manually (using a separate window to enter the info into) or to scrape the info from a CSV or PDF, which would then populate the table(s).
* Keeps track of all royalty/revenue earned for each music title.
* I’d like the ability to either enter this information in manually (using a separate window to enter the info into) or to scrape the info from a CSV or PDF, which would then populate the table(s).
* Run a bunch of different reports on all of this information.
* Has a very simple gui that is agile with searching, sorting, and reporting.
While I’m pretty confident I can find a lot of answers to my programming questions here on the forum and via Google and Youtube, my biggest question is: What should my order of operation be with putting something together of this size? Should I be starting with building out tables of information first, then move to a gui, then work on the pop-up ‘add info’ windows, then fork in being able to scrape info from other forms to populate the table(s), then work on programming different reports, etc?? I don’t know what order my creative steps should be in.
So I’m asking you all to weigh in so that I have a better idea of which way to head first. Thanks for any insight you can offer me…and please let me know if you need more info.
Thanks!
- Mike
I’d like to build a piece of software that does the following:
* Displays info for each track: running track count, track titles, track metadata (i.e. genre, duration, tempo, key, music library/publisher, etc)
* I’d like the ability to either enter this information in manually (using a separate window to enter the info into) or to scrape the info from a CSV or PDF, which would then populate the table(s).
* Keeps track of all royalty/revenue earned for each music title.
* I’d like the ability to either enter this information in manually (using a separate window to enter the info into) or to scrape the info from a CSV or PDF, which would then populate the table(s).
* Run a bunch of different reports on all of this information.
* Has a very simple gui that is agile with searching, sorting, and reporting.
While I’m pretty confident I can find a lot of answers to my programming questions here on the forum and via Google and Youtube, my biggest question is: What should my order of operation be with putting something together of this size? Should I be starting with building out tables of information first, then move to a gui, then work on the pop-up ‘add info’ windows, then fork in being able to scrape info from other forms to populate the table(s), then work on programming different reports, etc?? I don’t know what order my creative steps should be in.
So I’m asking you all to weigh in so that I have a better idea of which way to head first. Thanks for any insight you can offer me…and please let me know if you need more info.
Thanks!
- Mike