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, e.g. the Kulke importer creates separate image objects for each event even if the image URL is identical.
This results in spamming of identical images in the backend; also, as a side effect, the superevents will not have an image at all, as the importer does not recognize images with different ids to be identical even if the URL is the same.
Hence, consider making image URL field a unique field. Any duplicates (images with the same URL) should be combined into a single image object, with perhaps a n_events field telling the user how many events use this particular image.
The text was updated successfully, but these errors were encountered:
Currently, e.g. the Kulke importer creates separate image objects for each event even if the image URL is identical.
This results in spamming of identical images in the backend; also, as a side effect, the superevents will not have an image at all, as the importer does not recognize images with different ids to be identical even if the URL is the same.
Hence, consider making image URL field a unique field. Any duplicates (images with the same URL) should be combined into a single image object, with perhaps a
n_events
field telling the user how many events use this particular image.The text was updated successfully, but these errors were encountered: