SQL vs PYTHON
The new data collection process was fruitful compared to the previous ones. This latest approach made me realize that the main goal is to get the books from a particular era, not to get the publication date of the book. As a reminder, our latest method was based on a list of authors that one of my supervisors provided. The list is a metadata containing a list of multiple authors and the period during which they published their work. The period we are looking for is the Romanticism period from 1780 to 1837. So I started from with that list, filtered the authors who published their works during the period we are looking for. we create a new metadata for these authors. Then we take the new metadata of the authors and the project gutenberg metadata, then we join the them based on the name of authors. In the end we end up with a new metadata containing the British authors and the books they have published during the romantic period.
All the task described above was done via SQL query, a language that I used for the first time during this project. I started this internship with a very limited knowledge of SQL, and despite the book that I read and the tutorials I have watched, I have never really used SQL in a project before this one. So, I had to learn a lot while doing the work, I had to google pretty much any idea I had in mind to find out if SQL had it. I was surprised to see that the SQL syntax shares some similarities with Python, a language that I use a lot. The similarities mostly occur in the conditions where both languages use "and" and "or". I assume that these similarities made it easier for me to learn SQL and complete work with it despite my lack of prior experience.
Comments
Post a Comment