Yep, we changed the rules again. In this forum section, you can now report ANY missing comic again, recent or older, big publishers or small ones.
We really thought that using “Submit to Core” for the older or more obscure comics would help to get them added to Core more efficiently… but… we were wrong. It may be more efficient for us, the CLZ crew, but it is simply asking too much from you all, the users.
When using Submit to Core for missing entries, you have to:
use Add Manually to create an entry in your app, entering all details manually or by duplicating an existing entry
Submit that entry to Core
Wait until we process your submitted entry, without getting any feedback on that, without knowing if and when it is processed.
Then use the CLZ Cloud site to Link to manual entry to the new Core entry
On the other hand, when reporting on this forum:
you can just let us know what is missing
the CLZ crew adds the missing comic to Core for you (and lets you know!)
you can just use the Add Comics screen to add it from Core, resulting it a linked entry immediately
So we changed our mind and we are back to the normal “anything goes” rule for reporting missing comics.
Of course, we will still prioritize based on recency and popularity. Thanks for your understanding.
Is the preference that we do this in the forum, or can we still use Submit to Core? I’m already using “Add Manually” when I run into books that aren’t in the system, so the only issue I ever really have with that is the lack of feedback re: processing.
I’m happy to do whichever, just clarifying whether this is “you can submit via forum again” or “return to only/primarily submitting via forum.”
Then use the CLZ Cloud site to Link to manual entry to the new Core entry
A suggestion - if someone does a Submit to Core, maybe it can create a temporary Core entry that the manual entry is linked to, and then once the submission is processed then either:
the temporary Core entry is updated and made to be the permanent Core entry.
the temporary and new Core entries are merged together.
on the next Sync, the temporary Core entry redirects to the new Core entry and deletes the temporary.
Either way, the manual entry would always be linked to some Core entry that would eventually have the latest info automatically, no need to go to the Cloud account to link manually.
Not sure about that one. Many submitted entries are rejected and never actually enter our Core. Also many submitted entries for assumed missing comics are not actually missing and already in Core.
That’s why it would be a temporary entry. Maybe in a side database to avoid burdening the main Core.
Just something to think about…
If rejected, flag the temp entry on the server, and the next Sync deletes it from the server. Attach a reason explaining why. if the reason is because the book already exists in Core, update the user’s local entry with that Core ID, and pull down the latest book details per the user’s Sync rules. Tell the user why the submission was rejected.
If accepted, flag the temp entry on the server, and the next Sync deletes it from the server and updates the user’s local entry with the new Core ID, and pulls down the latest book details per the user’s Sync rules. Tell the user the submission was accepted.
If the server entry isn’t updated by staff or Synced by the user for a period of time, delete the temp entry from the server, and the next Sync reports to the user to resubmit if they still want to. This way, you don’t clutter the server with stale entries.
Getting feedback on submissions is something I’ve seen requested many times. This feels like a simple way to do it.
That’s fine. The temporary entry would simply be rejected as a duplicate, and the next Sync would update the local entry with the existing Core ID.
