Multiple Database Resource improvement ideas #54
Description
Add disclaimer that Database data is not live - it is curated and added manually.
@NYTEMODEONLY made this suggestion on Discord. This could pull double duty - explain to users how it works under the hood, may incite them to want to help get more data or help with future automation possibilities, and is a safety valve in case we have outdated data living in the database.
Add sourcing information, even if it's a blank box, indicating that the source info needs to be updated. Or maybe a hover-over?
This could be a 10K, 10Q (for the shares outstanding), the edgar profile for a company (for CIK, CUSIP, member number, etc). If we set a standard for which datapoints are often accessible where, that may incite more to submit the missing info.
Document when the last time a piece of data was updated / submitted
Data could be accurate once, but not any more. In addition to the above we should make clear what time the public disclosure data we're using is from. Trying to track all data over every year seems like it would be pretty difficult to me, but it'd be a shame to delete outdated data when looking at things over time is commonly done. Either way, I think we should label what year / quarter the data was collected and verified, and maybe add a disclaimer if anything reaches a certain age.
Ask for specific help with scraping / data collection
Would it be a good idea to detail what kind of contribution help we're looking for on the GitHub, a sentence or two around the Contribution section? At this point the frontend is near-perfect and the database data is well organized and responds quickly. Other kinds of help would be with setting up more scraping info and trying to automate more data and source collection so we can keep more updated in a general sense.