Steven L. Dasinger

According to the Publishers website ( https://www.benitezproductions.com/product/lady-mechanika-tablet-of-destinies-4-white-cover/ ) there is a Cover W. Inside the issue it has: Cover A (Direct Edition) Joe Benitez, Martin Montiel, & Mike Garcia Attached are is a listing of the covers from inside Issue #5.

Mark, Dan might be talking about the CB software.

Delete or Rename Bk 1.jpg to MMPB.jpg From: Pictures\B\Boulevard\Daredevil- Predator's Smile Delete or Move 1-A.jpg From: Pictures\I\Idea + Design Works\G.I. Joe Saturday Morning Adventures To: Pictures\I\Idea + Design Works\G.I. Joe- A Real American Hero-Saturday Morning Adventures Delete or Rename 1.jpg to 2.jpg then Move From: Pictures\S\Scholastic\I Survived The Shark Attacks of 1916 To: Pictures\S\Scholastic\I Survived Delete or Move 1.jpg, 2.jpg, & 3.jpg From: Pictures\V\Viz\Punch! To: Pictures\V\Viz\Punch! (Viz) Delete or Move 1-F.jpg, 1-G.jpg, & 1-I.jpg From: Pictures\I\Image\S\Spawn- Scorched To: Pictures\I\Image\S\Scorched, The Delete or Move ALL (1..jpg through 1-C.jpg) From: Pictures\M\Marvel\S\Star Wars- Halcyon Legacy To: Pictures\M\Marvel\S\Star Wars- The Halcyon Legacy Delete or Move HC.jpg From: Pictures\H\Houghton Mifflin\The Hobbit - 50th Anniversary Edition To: Pictures\H\Houghton Mifflin\Hobbit-50th Anniversary Edition, The Delete 4-F.jpg From: Pictures\M\Marvel\A\Alien (Marvel) (Duplicate of 4-C but 4-F is larger so you may want to rename it) Delete 1-F.jpg From: Pictures\A\Awesome\Youngblood (Vol. 3) (Duplicate of 1-E.jpg) Delete TPB.jpg From: Pictures\M\Marvel\C\Captain America- The Death of Captain America Prose Novel (or rename MMPB.jpg and replace the smaller MMPB.jpg already there).

HC had a server shutdown earlier. This may have caused your problem. It has been restarted.

(Sorry. Meant to reply to this sooner but I got busy and forgot about it...) A Field used with Sets is SetID. There are others (i.e. one that has the Set Description name but I don't know it/them). An Issue can only belong to one set. If you try to add issues already in a set, it will let you but it is deleted from the old set. (i.e the SetID changes to the new set number). (Side Note: Should there be a warning when adding an item to a set when it already exists in another set?) SetID is a Number that is automatically incremented. The first set created would be 1, the second 2. If Set 1 is disbanded, the next set would be 3. There is no way to know what number refers to what set (beyond 'random' searches for numbers to find a particular set of issues (well, I guess you can look for a SetID and (record the number but that would be a lot of work)).

No it is not. If a variant as limited to 100, Only 100 copies of that variant were created. What 1:100 means isn't about what is produced. It is what is ordered. If a retailer orders 100 copies of the Regular issue, they will receive (or can order) 1 copy of the Variant.

What happens with all Updates is a copy of the Master Database is sent to your computer, then compared to the Local Database. Any differences get applied to the Local database (based on preferences and settings). So, you can't reapply updates 1 week at at time and get information at that level. It is updated from the last time you updated to current Update (whether that was 1 week ago or 1 year ago ( or more).

I don't think there was any regular issue. Just the 250 numbered ones (and 25 Artist's proofs).

Whichever method is used, it would apply to all Issues (1 & 2 at 250 + 25) and the 3 new entries I just added (3-5 at 100 + 25).

That makes sense. On the back covers, they are also numbered with the max number being 250, which would mean there would be an additional (unnumbered?) 25 Artist's Proofs. If that is the case, would there be cause for both a 1 (limited to 250 and 1/A (or some other variation) for the Artist's Proofs?

For 3, I don't know the difference. I read it as either 25 separate "Artist's Proofs", or (more likely to me) 25 illustrations of "Artist's Proofs" inside the issue. Either way, just the Issue is listed. (see attached for the text) For 6, If the column allows (and Notes does), I always check AA to see what the Master Database has. Possibly, you have 'Lock item notes' checked on the Update options (or something else happened).

1) Black Cat (Marvel) #1/V41 Limited to 1500. (submitted correction) 2) Lady Death: Treacherous Infamy #1/HC Limited to 666 This is correct (although not sure the number of backers relevant). 3) Moebius Ashcan Comics 1 & 2. The information is correct (and printed on the back cover). Only one issue of each is needed. 4) The Pantheon Project Limited to 25 (numbered) The fact this is #2 (of 25) should be in the individuals (local database) Notes or Grading Notes and not the Master Database. From Kickstarter site: Pledge $55 or more Limited edition VARIANT COVER for The Pantheon Project #1. The Black & White Variant cover will be the original pencils done by Leila Del Duca. We are only printing 25 copies. They will be individually numbered 1 through 25 and signed by all members of the creative team. 5) Vampi #15/A I believe it is limited to 1500. (submitted correction) 6) Van Helsing vs. Dracula's Daughter #1/J My database and AA (along with what is printed on the cover) just have 150 (which is the correct amount).

Corrected and submitted corrections. FYI, 23/F is 75 and 45F is 100 for circulation.

Is the correct cover scan you are replacing larger than the incorrect one that automatically downloads? If it isn't, this could be the problem. If it is, you may need to contact support to see why this wasn't fixed for you.

What version of CB do you have installed? This was a problem but was fixed (at least for me and another customer) recently. I am currently on b1557.

I am only talking about the one column: Item Description. This is the only one where (currently) data not containing certain keywords will have that information deleted. Notes is related only in that those same keywords will move information from it to Item Description (via the Rebuild List). But anything that Rebuild Lists moves will be, by definition, valid information for Item Description and not deleted from Item Description with a Rebuild Lists. It is only when you manually enter something to Item Description that you take a chance it won't be 'valid' (for lack of a better word) and get deleted. All other columns work as you would expect (changes/additions/deletions accepted will be added to the Master Database and the Update will make these changes to all Local Databases.

Do you have a backup from before the update that you can compare? If you do, screen shots of the before (non-NM condition) and After (NM condition) could help?

No, I understand completely. And agree that the deletion of the data from Item Description is not a good idea that should be fixed. But that is how it currently works. And why it can be frustrating trying to enter Item Description strings (or entering Note strings that WON'T get moved). As far as I know, an Item Description string needs to have 'Cover', 'Variant', and/or 'Edition' to NOT be deleted. (Note: a 'string' is one or more words separated by a semi-colon.) This has been tweaked as 'Covers' will now be deleted or not removed from Notes (in an effort to remove certain entries, I believe). There may be other tweaks I am not aware of at this point or that may be added in the future.

If this can actually be shown, it sounds like a good idea. The topic was mentioned at least once but not in great detail. In general: If a change to an existing Publisher/Title/Issue # (which uniquely identifies an item) is sent and not part of the unique items), the process can compare the submission with the Master Database and display the differences (with changes high-lighted in some fashion, I believe). If a change is a new submission, there would be nothing to compare. This is important because if a change is made to anything that is needed to uniquely identify an entry (Publisher/Title/Issue #), it will look like a new submission since it can't be found in the Master Database. These types of changes would need to be brought to HC's attention through an email to Support, on Slack (if you can) or here in the forums.

You are missing the point. HC runs the Rebuild Lists (the same one you can) before the Update is created This means it is NOT in the Master Database after the Rebuild LIsts. Steps: 1) Information is added to Item Descriptions (possible removing it from Notes) on a Local Database. 2) It is submitted to HC. 3) HC approves it and it is added to the Master database. 4) HC runs Rebuild Lists before the Update and the information is deleted from the Master Database (as it doesn't match the information it looks for). 5) When an Update on a Local Database, the Item Description is changed to match the Master Database (which no longer has the information) and the Item Description information in your (and everyone else's) database gets deleted (along with the information that was moved out of Notes (depending on Update settings)). Or 3) HC rejects the change. 4) When an Update on your Local Database is run, it reverts back to what you had (Information not in Item Description (but Notes still retains it) and nothing changes in other Local Databases.

I guess I should have added a little more detail. Before they push an update HC runs a Rebuild list. Even if what you submitted was approved and made it to the Master Database, the act of running Rebuild Lists (before the Update is pushed) could delete what was submitted/approved from the Master Database. So, to see if what you submit will get deleted or not, you can run Rebuild Lists before submitting. Depending on what you entered in Item Descriptions could make a difference. For example, if you added 'Dynamic Forces', it will (probably) get deleted. If you added 'Dynamic Forces Variant', it would (probably) be kept. (I say probably because I haven't tested this out but it should be what happens.) I am guessing that getting what is kept in Item Descriptions is an on-going process and will be tweaked over time to be a little more tolerant of other things. PS Also, I would prefer if something IS deleted from Item Descriptions by the Rebuild LIsts, that it gets added to Notes instead of deleted so information isn't lost (although this may cause duplication or near duplication in Notes).

For changes to Title name (and/or Publisher and/or issue number), you do need to let HC know (as you did here). Otherwise, they will just look like a new Title (or issue) submission and the one it is supposed to replace will still be in the database (unless it gets caught amidst the thousands of changes being processed (not very likely...)).

If you make the change to the Title description before you submit a correction for an issue in that Title, the information is sent to HC. Whether or not they keep/approve it is another matter. I would test a couple first to see what happens.

I think I did mention to be careful what you put in Item Description. HC is trying to keep tighter control on this column so it doesn't turn into another Notes. I don't know all the parameters related to the column but words like Cover (but not, I think, Covers), Variant, and Edition are the ones I know of. There may be others but whatever doesn't pass the cleanup process gets deleted (not moved anywhere). You can check ahead of time by running Rebuild Lists for Item Information as it is what does the cleanup.

Have you tried opening Notepad and scanning into that? If that does work, try downloading the most current version of CB (b1515, I believe) if you don't already have it.