Short version of the situation is that I have an old site I frequent for user written stories. The site is ancient (think early 2000’s), and has terrible tools for sorting and searching the stories. Half of the time, stories disappear from author profiles. Thousands of stories and you can only sort by top, new, and 30-day top.
I’m in the process of programming a scraper tool so I can archive the stories and give myself a library to better find forgotten stories on the site. I’ll be storing tags, dates, authors, etc, as well as the full body of the text.
Concerning the data, there are a few thousand stories- ascii only, and various data points for each story with the body of many stores reaching several pages long.
Currently, I’m using Python to compile the data and would like to know what storage solution is ideal for my situation. I have a little familiarity with SQL, json, and yaml, but not enough to know what might be best. I am also open to any other solutions that work well with Python.
Based on my experience…
Yeah, don’t use YAML for storing serialized data. It’s intended to be hand-written.
Did not know that. I’ll keep that in mind.
@Bubs @Ephera YAML is also a superset of JSON, so if you generate JSON tools that handle YAML will be able to use it still.
Don’t know the limits of Yaml, especially for large chunks of data, but I do like its easy readability and similarity to Python. I’ll probably try out a bit of yaml as well as some of the other recommendations other have given me.