I find CLZ staff to be highly responsive in making corrections/revisions to core entries when issues are raised via CLUB CLZ, which is great… Questions though.. when I amend, correct or expand an entry via ‘Submit to Core’ how do you assess my (or anyone’s) submissions for accuracy/credibility? Are subscriber amendments accepted at face value? Is there any verification process? Just trying to understand why some corrections/amendments that I submit are adopted and some are not? Is there any way we could be notified once a suggested amendment to core data has been adopted?
I’m afraid I can’t delve into that information, but if you have a submission that did not go through, feel free to post about it on the forum and one of my colleagues can check it out, or report the error through our forum of course.
Is there any way we could be notified once a suggested amendment to core data has been adopted?
There is not. But feel free to post on the Club as we will reply here!
Ok, but can you please explain the reasons why you are unable to answer my (very straightforward) questions. I am failing to understand the apparent need for secrecy. It should not be controversial to explain how you process subscriber-supplied data. What am I missing here?
Book Submissions are best used for missing information and small corrections.
Given the large number of books and submissions we receive, we scan the incoming submissions and process most of them automatically. In general, everything gets accepted, but we do reject some submissions from time to time. For example, when titles are written entirely in ALL CAPS, or when additional information has been added to the title field that doesn’t belong there.
So, in short: the submit option is best used for missing information and minor corrections.
If something is actually incorrect in the database, it’s better to report it here in the Club. We can then make sure it gets corrected in CORE for you.
Thanks, this is both enlightening and, frankly, disappointing. So, as I understand it, if I make a submission to the core with a book title in ALL CAPS (exactly as it is printed on the book itself) that accurate information would be rejected? And that would be the case with a new book title submission or a correction to an existing record? I am now troubled for the credibility of the core tbh…
I am sorry to hear you are worried about the credibility of the CLZ Core database.
I don’t there is a big problem at all.
As we said, for a case like the ALL CAPS titles, just let us know on the forum and we will take care of it.
Ok, but if you are happy to make ALL CAPS corrections via the forum, why is there a core default reaction to reject such submissions / corrections in the first place? Does the core similarly reject book titles that are in all lower case?
If the title is the only issue, you can simply fix it in your own database.
The main point is that if you notice other database errors in the book, you can report those on the forum. If you choose to display the title in ALL CAPS, that’s of course completely up to you., but there’s no need to submit them. You can just make the change directly in your personal database.
That is because in 99.9% of cases of ALL CAPS titles, it is a user that is submitted careless, bogus entries.
Does the core similarly reject book titles that are in all lower case?
Core doesn’t reject anything automatically. But yes, out content managers may reject all lower case titles in the same way.
PLEASE, let us worry about our CLZ Core, and then you worry about your local database only.
Thanks, understood. I thought I was being just a little bit helpful to other CLZ users by submitting accurately composed titles, but anyway…
You definitely are. There is no reason to stop doing that.
But please, let US worry about how we handle those submissions as efficiently as possible.