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
Currently, the link between Zimfarm recipe and CMS title is pretty weak: CMS doesn't know which Zimfarm recipe(s) is (are) supposed to create ZIMs for a given title.
Consequences are :
users can't easily switch from Zimfarm recipe to CMS title or vice-versa
we can easily end-up where Zimfarm recipe changes the ZIM name (user update of recipe configuration or scraper update), CMS editor assumes a new title needs to be created (instead of updating existing one) and creates a new title with new ZIM name, which ultimately leads to duplicate ZIMs in the catalog
corrolary of previous point is that CMS cannot help editors when ZIM name changes by suggesting updating the existing title name when it is already associated with same Zimfarm recipe (like say "hey, I have a new ZIM whose name is "xyz" ; the Zimfarm recipe creating this ZIM was previously associated with title "abc" ; do you wanna update "abc" title to "xyz"?)
CMS cannot detect ZIM name conflicts: two Zimfarm recipes creating ZIMs with same name (and flavour if used) (would solve Detect conflict of ZIM names across recipes zimfarm#1037 when CMS is in use ; pretty sure we have another issue about this topic but I fail to find it)
Currently, the link between Zimfarm recipe and CMS title is pretty weak: CMS doesn't know which Zimfarm recipe(s) is (are) supposed to create ZIMs for a given title.
Consequences are :