Fred Slota

Spring Sale announcement has left the News page...

More information is better.

Suggestion - Bill Mantlo's name should be moved to a note, something like "Bill Mantlo incorrectly credited as writer (per letters page of issue #10"

My post was meant to describe the action that had already taken place by that self-same latest build. I had updated the software and just completed scanning new books right before Pete made his announcement on last weeks stream.

Or, you could just tweak the existing interface to actually show the downloaded pictures as you scan new books... Thanks.

Submissions haven't been included in the most recent update.

How about adding a "Refresh Thumbnails" button to the "Add by Barcode" window as a manual workaround to the timing issue for fresh cover scans when adding by barcode?

Well, I feel better about bringing it up after it seemed like it was a simply a non-enabled setting.

Always curious to know what happened when the program announces that it's updating the database.

Question - since I've (and maybe others've) held off on this update, can we get a posting when the next week, successfully-updating-comic-book update is posted? "Others've"... huh...

Thanks for the update.

Thank you for the update.

Is there going to be/has there been a correction to the update that add new comic books? Or should I wait for next week's update?

Any updates on this issue?

Topic re-re-request, too late for tonight's show... I would like to see what the process of new data submission looks like from their point of view, with examples/screencaps/video... What info does or doesn't get sent? What does a CB editor see when looking at a wholly new entry? What steps do they do when processing a new entry before committing it into the master database? What does a CB editor see when looking at an updated submission? Do they only see the old/new field side-by-side, is the specific change highlighted? Updates are probably continually processed, but do they process submissions as single events, or do the look at things in batches? I know I tend to submit similar updates in a batch... do they look at batch submissions to speed up common corrections? I'd imagine for newly entered issues, they get multiple submissions with the same type of info, do they process some updates all for the same issue at once? Would also be interested to see the steps taken at the weekly level when preparing the weekly update.

Thank you. Was just looking for the feedback of "it's on the list" vs. "it's fine , nothing to see here".

Thanks.

Primarily was wondering if there was any intention to do anything... I understand there would be scheduling, development, testing if so, just didn't know if the programming team had mentioned anything back.

Okay. Thanks.

Yes.

I feel better about this then. I just always pictured that when I do a "submit update", the entire database entry is sent, changes and constants.

Just submitted m first round of updates identifying connected covers in the Item Description field, mostly Ptych covers, but some twin and overlapping covers, too. This update identifies 1,389 issues across 410 separate sets, including both the individual covers and the full image covers that I found. I will post the collected oddities for this round (sets with unidentified pieces, sets with inconsistent Cover Artist attributions, etc.) after they get accepted, as it will be easier for others to help when the set identifications are available to all. There are still Notes and Item Descriptions that include notations that may or may not be identifying additional cover sets; I decided to process what I had and submit before continuing.

1) While it is possible, these issues are otherwise random. Do people (other than me) really submit updates on many random issues? 2) If that is what is happening, it is disappointing that editorial does not notice these incorrect entries getting let in. Ah well, it just adds more free submission points to my total.

Cleaned scans. Thanks

Rotated. Thanks