Description
Currently, the history.json file only stores lists of contentIds for previously downloaded screenshots and gameclips. Other interesting metadata about the media (date/time of capture, URI, etc.) is either lost or embedded in the filename, which isn't immediately accessible. This could be improved by splitting the history into two files, screenshots.csv and gameclips.csv that represent pandas DataFrames storing all the relevant metadata about downloaded entries.
As an aside, this may also help with the long-term goal of minimizing the number of API calls as described in #3.
Can you help develop and maintain this feature?
Yes.
Description Currently, the
history.jsonfile only stores lists ofcontentIds for previously downloaded screenshots and gameclips. Other interesting metadata about the media (date/time of capture, URI, etc.) is either lost or embedded in the filename, which isn't immediately accessible. This could be improved by splitting the history into two files,screenshots.csvandgameclips.csvthat represent pandas DataFrames storing all the relevant metadata about downloaded entries.As an aside, this may also help with the long-term goal of minimizing the number of API calls as described in #3.
Can you help develop and maintain this feature? Yes.