Skip to content
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.

steve state #18

Open
willkg opened this issue Jul 15, 2014 · 1 comment
Open

steve state #18

willkg opened this issue Jul 15, 2014 · 1 comment

Comments

@willkg
Copy link
Member

willkg commented Jul 15, 2014

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:

  1. use a sqlite3 db to store status on things
  2. (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".

@AvdN
Copy link

AvdN commented Sep 4, 2015

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants