You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.
We need to be able to keep track of the state of video metadata in arbitrary ways. I was thinking we could do one of two things:
use a sqlite3 db to store status on things
(ab)use the existing json files and add some code that lets us store additional steve-specific data in them using keys with steve_ at the beginning that get ignored when pushing/updating richard instance via the api and get ignored during verification
I kind of like item 2 since it's "fast-and-loose".
The text was updated successfully, but these errors were encountered:
There is both global (per project) and state for each json file. The global state cannot be meaningfully stored in the individual files.
sqlite3 has the disadvantage of not easily being edited
you could store the global state and the state for individual files in a YAML file structured:
# status file for yaml
yaml:
last_sync: 2000-01-01 00:00:00
files:
0152_Fabio_PligerOier_Beneitez_-_Welcome:
check_language: true
check_length: true
i.e. have a key entry based on the filename (without .json/.yaml extension)
and have the tools (e.g. steve-cmd verify) merge in relevant data.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to be able to keep track of the state of video metadata in arbitrary ways. I was thinking we could do one of two things:
steve_
at the beginning that get ignored when pushing/updating richard instance via the api and get ignored during verificationI kind of like item 2 since it's "fast-and-loose".
The text was updated successfully, but these errors were encountered: