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.
I would stay away from YAML (almost at all costs).
What’s your reasoning for that?
At this point, I think I’ll only use yaml as the scraper output and then create a database tool to convert that into whatever data format I end up using.
https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
JSON is a much simpler (and consequently safer) format. It’s also more universally supported.
YAML (or TOML) is decent for a manually read and written configuration. But for a scraper output for storage and follow-up workflows being through code parsing anyway, I would go for JSON.
That’s an interesting read. I’ll definitely give json a try too.
Very wise idea. And if you want to up your game, can validate the yaml against a schema.
Check out strictyaml
The author is ahead of his time. Uses validated yaml to build stories and weave those into web sites.
Unfortunately the author also does the same with strictyaml tests. Can get frustrating cause the tests are too simple.
Gonna be honest, I’ll need to research a bit more what validating against a schema is, but I get the general idea, and I like it.
For initial testing and prototypes, I probably won’t worry about validation, but once I get to the point of refining the system, validation like that would be a good idea.
Curious to hear your reasoning as to why yaml is less desirable? Would think the opposite.
Surprised me with your strong opinion.
Maybe if you would allow, and have a few shot glasses handy, could take a stab at changing your mind.
But first list all your reservations concerning yaml
Relevent packages I wrote that rely on yaml
pytest-logging-strict
sphinx-external-toc-strict