-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZIM filename does not match requirements #43
Comments
I see two paths forward on this issue:
I prefer option 2 since:
|
youzim.it filenames have already been debated a lot. @Popolechien have been very insistent on the filenames being user-centered given those are not in the catalog. Including the unique ID (so we can safely store them in a flat folder) required some convincing. Additionally, the period makes zero sense in the context of youzim.it: it's creation is manual and not periodic and this month-period would only bring confusion. I thus think option 1 is more practical. I don't recall how wp1 filenames are constructed. They might not fit the pattern neither |
WP1 is not impacted from what I looked after because we validate only output, description, long description and other basic range / oneOf validations. OK for option 1 if this is what fits you. |
@Popolechien can confirm whether it still makes sense to him |
yes. |
I've opened upstream issue since nothing has to be done in zimit-frontend in the end: openzim/zimfarm#867 (and I will work on it tomorrow) |
When creating a schedule, the provided filename does not match our convention and is refused by the Zimfarm since openzim/zimfarm#865 has been merged.
The text was updated successfully, but these errors were encountered: