Adam Sternberg

This title (https://atomicavenue.com/atomic/TitleDetail.aspx?TitleID=89402&M=1) is incorrectly named. Instead of Fantastic Four Fanfáre, it should be Fantastic Four Fanfare. I've tried to submit this change directly, but I'm posting here as well.

The data updates I'd submitted last week for this have been reverted by this week's update, so hopefully, the updates will be adopted soon.

This should be removed, as it looks to be the same as issue 22/A (both have the same item description of Marvel Universe Connect M Cover)

I discovered this is still a problem. These titles (Archie and Friends (2nd Series) and B&V Friends Forever) are still being mis-categorized as individual one-shots. The UPCs and indicias make it clear these one shots are really part of the appropriate series. For example, the UPC for Archie & Friends: Level Up! 1 is 76281622336201911 and the indicia reads "Archie and Friends, No. 1 (#19), June, 2025". These titles are causing several duplications in the database. FYI, @Mark J. Castaneda

I'm still seeing the mis-capitalized 'DC' as of today (Feb. 22, 2025)

Using version v25.5.1.2236, backup files are disappearing when being compressed. Worse, if automatically saving to cloud, the upload process gets hung (with nothing to upload). However, if I turn off auto-compression, and compress it manually to 7Zip, it works fine. For what it's worth, I do have a recollection of seeing this before, but have no idea how it was corrected.

The various "What If...? Galactus Transformed..." titles are wrong. The indicia for the Hulk title that came out this week is "What If...? Galactus: Galactus Transformed Hulk?" (note the "Galactus:" and the question mark at the end). I've tried to submit a content correction, but I'm posting here as a backup

Side note: The cover artist on 1/B is listed as "Mr. Garcin". Is that correct, or should it be "M.R. Garcin"?

This title is incorrect. The correct title according to the indicia is Sam Wilson: Captain America. I will edit the title and submit as a correction, but I'm not sure that trick always works, so I'm alerting folks here as well.

Excuse you? I didn't use "the same scripted BS reply"; i quoted what was stated before, and I invite you to read a reply thoroughly before you attack the person making the comment

Is this why there are some many "skipped variants" in the database (for example, some title one week having 11/A, 11/B, 11/D, and 11/E issues, but no 11/C)? I have to admit that's one of my biggest pet peeves, and I'd almost think it's not worth entering placeholders in the database until they're actually in-hand (but I get that's not practical given the scale of what comes out each week...)

I had searched by UPC, but maybe not when I asked the last question. I will update, thank you both.

@Mark J. Castaneda, this is still showing up as a unrecognized title for me. Was there a final decision on how it should be cataloged?

Just putting my engineering hat on... Could the value ranges be based on NM value, but the issue in question has a lesser grade (which is reflecting in the other columns)?

I didn't (yet) dig it out, but did look it up on GCD. The issue in question is https://www.comics.org/issue/1739387/ (still named Batman Day Special Edition). It's called out there as a reprint of Batman (3rd series) 16 (as Mark surmised), which is here: https://www.comics.org/issue/1671798/#1984648. One thing I note is that the page count for the story is the same (20 pages), so until I can dig it out of my stacks, I'd wager it is a full reprint.

I'd have to dig to find it, but the curious thing is that it WAS in the database under the old title. Seems it may have just been removed rather than corrected as a reprint.

After last week's update, it was reported that Batman Day Special Edition was an obsolete title. However, I can't find where the issue (2017) went to. The UPC number is 76194135344900111. A generic online search came up as Batman Day Special Edition 2017, so that's no help. Any ideas? Thanks.

What Gregory said! 😁 If you're not sure the search is working right, you can take a UPC you know is right that's already in ComicBase and copy-paste it into the search box. You should definitely get a hit doing that, and it'll also help confirm the expected format for a UPC

Another suggestion is to search for an issue by UPC number, to see if it got under a different title for some reason.

I believe this is a duplicate of The Amazing Spider-Man (6th Series) Annual #1 2024/A and should be removed https://atomicavenue.com/atomic/item/1403962/1/lta-hrefquothttpsatomicavenuecomatomicseries729121TheAmazingSpiderMan6thSeriesquotgtThe-Amazing-Spid

This is the wrong title, according to the indicia; it should be Initiation instead of Invitation. I've submitted a title change as well.

It's how I get a sizeable portion of my submission points! 😁

Yes, I can see the exported data (in both a text editor and a spreadsheet), and nothing looked out of the ordinary. For what it's worth, I did try to limit the export to "personal" data, such as custom field, qty in stock, wanted, grade, etc.

No bueno. Not only did the rebuild not help, but exporting into a brand-new database didn't either. I exported only a few fields (see list below), rebuilt all lists except for pictures, and updated content on the new database alone using Sidekick: Title Item # Condition Qty In Stock Custom Field 1 Notes Wanted Price Cost One thing to note is that I cheated a bit with Sidekick: I exported from the old database called "Database", created the new database called "New Database", imported into New Database, renamed "New Database" to "Database", and updated content in Database using Sidekick. I'm not sure whether Sidekick works under the covers using file pointers (that would follow a rename) or it would use the filename.

@Mark J. Castaneda, The update just now finished running in Sidekick, and I was watching it. I have good news, good news, and bad news. Updates to two of my databases were clean, but the third one still showed the error at the top of Sidekick. That database ID is 236c2c0a-0dff-44ba-bbd9-362efc0937fe. I'm pretty sure I'd done so, but I can try a full Rebuild Lists on it one more time; otherwise, I'm thinking there may be some corruption in that database?