Assets naming issues
blackgear opened this issue · comments
Daniel Zeng commented
I'd like to proposal some variants:
- sha256_digest.mp3
- numeric_id.mp3
- dialogue_text_in_roma.mp3
- dialogue_text_in_english.mp3
3 and 4 may suffer from same dialogue in different sources. 4 also invoke some translation problems....
We can put all metadata in assets.json, including source uri and clip timing point.
Outvi V commented
Agree. I'd go for numeric id or a shorter digest (since sha256 is too long and we don't really to verify the integrity).