New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query tables from plain text files #8
Comments
I'd be happy to help you take this on. I've faced similar data inconsistencies when building tooling for real estate projects |
@ahiddenproxy I have assigned you, please let me know if you need any additional context! Thank you! (Sorry for the late reply) |
I should also mention, you don't need to worry about the pedantic details of the source code, if you don't wish to. I can point you to the function where text input is given as a table, and you can work from there on creating a function that returns structured data. As long some sort of querying function is created to turn the table into structured data, I can implement said function into the code so it works with everything else properly. |
Here is the relevant code.
The link may be slightly different then the provided code, as some reliability edits have been made |
The most recent addition to wallstreetlocal was the ability to query XML files along with HTML files. The only format remaining to code in now, is plain text (TXT).
The SEC's XML and HTML stocks were barely structured enough to be queried accurately, but TXT provides an even harder challenge. The problem is the inconsistency. While tables in TXT can be read fairly easily by human eyes, they are too disimilar to query effectively.
Here are some minified examples.
The column sizes, names, and overall formatting of each table changes too often for any meanginful code to be written. Without writing a gargantuan amount of code, or using AI (which is expensive), there doesn't seem to be much way to query stocks like this.
There should be a better, more effective method to taking the TXT tables, and creating usable, structured data. If you are taking on this issue, there is no need to create pull requests. Instead, submit some code samples that can be used, and I will transfer you to the back-end repository where you can submit your changes.
The text was updated successfully, but these errors were encountered: