Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/2/2021 in Posts

  1. Mark, I just did the Friday update. It added 300MB to my dB for all the new Magazine entries. How many of your existing customers have a use for all 5,000 issues of The Daily Telegraph from Australia? This is just bloating the dB and making the updates take a lot longer. I would really, really encourage you to allow all of us existing users to CHOOSE whether we want all the Magazines in our local dB or not. And if you start bloating the dB with 'Books', then please add the same option there too. I subscribe to ComicBase to manage my Comics. Nothing else matters to me.
    4 points
  2. Instead of creating a new title, porting over a user's existing stock, and then deleting the old title, I think that there might possibly be another way to accomplish the same thing. CB could issue a program update that (for example) looks to see if the user has the title Star Wars (1st series) in their database(s). If they do, the update says something like: "This update will rename your existing title Star Wars (1st series) to Star Wars (1977 series). All of your inventory and issue data will be preserved, only the title will be changed to match to master database. Click "yes" to continue. If you click "no", this update will keep your existing title and create a new, separate Star Wars (1977 series)." For the users that click "yes", the updater will execute the "Modify Title" function to change the series title to Star Wars (1977 series). I imagine that something analogous could be done to change the Media Category for titles as well. I believe that the weekly content updates only import data into your database, so this kind of solution would almost certainly have to be done via a program update.
    3 points
  3. It is 'Captain America (1st Series)' #Anl 2.
    2 points
  4. Hi, @Steven L. Dasinger Thanks for your reply. It's not that that titles have to change, it's that they can change. What #1 shows is that titles can change even for something as simple as a stray space or to correct an article placement, while #2 seems to be locked in amber especially for something like the Metal Men mini-series -- even though changing it would make it easier for all collectors to find. While I would prefer the year of release in the title rather than Series 1, Series 2, etc., I'd be find with it just to bring consistency. Don't get me wrong, I applaud the grammar and article corrections of #1, but I find it baffling that there is a reluctance to apply organizational standards to titles in a program designed to organize a comic book, book, or magazine collection. I think that this is the main frustration of myself and my fellow users. Thanks for listening, Walt
    2 points
  5. In addition to slowing things down, without the knowledge I now have from digging all over for information on these books, it doesn't make any sense. The original title was "Justice League" in 1987 but that became "Justice League International," which changed titles in 1989 to "Justice League America." The trouble is that the books in question were placed under Justice League America, throwing a word into the title that is nowhere on these books. I understand that these two have the same writer/artist as was on the main title at the time but finding it would be near impossible without knowing that or looking for the title.
    2 points
  6. Hi, Randall-- I get it and, unfortunately, I'm learning to live with it, too -- but it really SLOWS things down when you have to stop and wonder đŸ¤”, where is this thing going to be found in CB? Let's go on a scavenger hunt!
    2 points
  7. Although ComicBase is an amazing program and the defacto standard for cataloging a comic book/magazine/book collection, it suffers from a major defect and that is how titles are created, named, and maintained especially if a title ends and is restarted with a new number one adding it as part of a series. A classic simple example of this is DC Comics's Metal Men, e.g. Metal Men Metal Men (3rd Series) Metal Men (4th Series) Metal Men (Mini-Series) In the example above, Metal Men (Mini-Series) would ideally be Metal Men (2nd Series). However, there is an underlying decision that makes renaming Metal Men (Mini-Series) problematic, as described by Pete, and that is that the title name is used as the foreign key in, what I presume, is the Item table. This defect can make it difficult to locate a specific title, organize titles in order of their publication and often results in additional titles added for titles that already exist. Based on the comments of @Peter R. Bickford in the live stream of 4/13/2022, it seems that it is unlikely to change. I think that's a shame since organization is the major component of a database application. After giving this just a little bit of thought, I think this may be a starting point of a solution that could solve the problem. Caveat: I'm suggesting this without knowing the intricacies of the DB structure and would welcome input. I expect that moving forward with this will not only take time to mull over but to implement as well, but ultimately will make ComicBase an even greater product than it already is. Here's my take: Create a new field called DisplayTitle in the table that contains Title. Copy the values of the existing Title field into DisplayTitle. Use this DisplayTitle for searching and display. When a new title is created either by CB or a user, copy that value into the DisplayTitle field as well. If a DisplayTitle needs to be changed, CB verifies the new display title, changes it and voila, after the next update, the title can be found and sorted correctly. This would allow the implementation of a title naming standard perhaps using the indicia, year, and even the publisher of the title. Something like Metal Men (1993 Series) (DC) The benefit of this is if the standard changes, titles can be easily updated. This solution addresses some of the problems that @Peter R. Bickford brought up in the live stream. It doesn't violate the foreign key constraints between Title and Item. It easily allows for renaming the DisplayTitle if the indicia changes between solicitation and publication of the title. There is no requirement to shift data around in the tables and potentially mess up a user's data, since it's simply a DisplayTitle change. I'd love to see something like this implemented. --Walt
    2 points
  8. I'm wondering if newspapers could be spun off to their own section, separate from the Magazines section. As I mentioned earlier, I don't want to exclude magazines entirely. I would, however, exclude newspapers if I could. I can see where tracking all of that stuff in Human Computing's master database might be worthwhile for them, but I doubt many of us want to house a mega-database on our own systems. As ComicBase grows and expands well beyond comics, there may be a need to devise more ways for users to select the portions that meet their needs and exclude those that don't. I've got plenty of magazines related to comics and entertainment, but I don't need a newspaper index. I've got plenty of books, but I don't need an index of romance paperbacks or theological volumes.
    2 points
  9. Thanks for the catch! We've revved the setup sheet for the scanner here to remove any extra spaces that get inserted: https://www.comicbase.com/Support/CB_Wireless_Scanner_Easy_Setup.pdf The latest build of ComicBase (build 1669) also handles the issue. -Pete
    2 points
  10. There's also an additional benefit to this approach... it allows a user to define his own display name. It a setting is added to not override DisplayName, a user could easily maintain their own names.
    2 points
  11. That's my feeling as well for the same reason.
    2 points
  12. I think it's a great idea, I'm just afraid this is going to die on the vine and I'll be complaining about it again the next time I come across a crazy title.
    2 points
  13. It's worth noting that the confusion over incorrect and inconsistent titles in ComicBase cascades over to Atomic Avenue as well. So while we ComicBase users can figure things out and learn to work with them as they are, random shoppers using Atomic Avenue may not have a clue. It requires a bit extra to find issues of Donald Duck published by Gladstone, for example, if you don't realize that they will be listed under the title Donald Duck (Walt Disney's...) where the publisher is listed as Dell. I'm not yet selling on Atomic Avenue, but I imagine that more clarity and accuracy would positively affect sales. There are also seemingly random titles that are sometimes assigned to specials and FCBD comics. I've had difficulty finding some of those in the database. My most recent example: I just picked up a copy of a Doctor Who comic book that was exclusively released for the 2015 San Diego Comic Con. The cover logo only says Doctor Who, with 2015 Exclusive San Diego Comic Con International in the bottom corner. The indicia says Doctor Who: San Diego Comic Con Exclusive. I didn't find this among the existing Doctor Who entries, so I added it with the title from the indicia to my database. Only later did I accidentally stumble upon its existing entry: it's under Doctor Who: The Twelfth Doctor as #0. There are a few problems with this: (1) There is no "#0" anywhere on the actual comic book; (2) The San Diego comic does not precede the publication of #1--it came out around the time of #10; (3) Although the San Diego comic features the twelfth Doctor and is related to that series, the words The Twelfth Doctor appear nowhere in its title, unlike the series; and (4) While I might understand an argument for keeping the San Diego comic under this series as a Special Edition instead of #0, other Doctor Who convention specials are listed under their own titles, not as special editions of regular series, so there would still be a lack of consistency. It's a problematic, hard-to-find entry, yet I don't think it can be fixed without screwing up someone else's existing inventory. Publishers have definitely made a mess of things to untangle, and they are not themselves consistent, so discrepancies are bound to occur. I only wish they were easier to correct when pointed out, with some mechanism to transfer users' existing quantities to the corrected title or issue number. I understand that there are technological limitations in place, and circumventing them is well beyond me, but I hope someday this can be worked out.
    2 points
  14. I'm not sure if this was covered in an earlier video, I haven't watched the whole back catalog, but I think a good topic I would like to see a couple of examples of what a reviewer of submissions sees when reviewing submissions and how they process them. A couple of examples would be helpful - a wholly new issue, an edited Title description, an edited Notes, a newly-supplied Cover Artist, etc. What kinds of things are easily recognized, what kinds of things are best warned about ahead of time (and how to bring them up, and to whom).
    2 points
  15. Both the AA and the mobile app functions are pretty important, actually, especially as more items that were tracked in the original "single category" configuration of ComicBase get moved into the Magazine and Book categories.
    2 points
  16. Here is a first draft of information about the Advanced Find. Let me know if something needs to be added, deleted, modified, or explained better. ******************************************** I believe the database currently used by CB is SQLite. Here is a link to the SQL (Structured Query Language) for SQLite Select. https://www.sqlite.org/lang_select.html Here is a link to the Built-in Scalar SQL Functions https://www.sqlite.org/lang_corefunc.html Because of the limits put on Advance Find, a lot (most) of the SQLite documentation is of no use but it will get you the syntax for the ones you would use. (NOTE: I am supplying these links in case they help someone. Personally, I would use them as examples of how NOT to write a manual. I know what I am doing with SQL and I find these (while accurate) are to read/follow.) ******************************************** The Query functionality in the Advanced Find is limited to just the WHERE clause. You can't control the Select (what columns are returned), the From (the tables involved), or the Group By (used with Aggregate Functions like Sum, Count, Average, etc.). The main reason for this business decision is that every row returned has to be unique to allow them to be updated (changed) individually. Below are sections that are explained in more detail below: Data Types Comparisons Order By Random Notes ******************************************** DATA TYPES: To make it simple, there are just four Data Types (there are actually sub-types for some of these). Text: This is character data and can contain any alpha/numeric/special characters. All Text searches are case-insensitive (ignores case of letters). The constant compare value needs to be contained in single 'tick' marks (double 'tick' marks also work but single is the more standard way). I.[Title] = 'batman' This will return just the one Title 'Batman" as it is an exact match (and shows that Case doesn't matter) Date: This contains Date information. It has to be a valid date. (i.e. Feb 31, 2021 is NOT a valid date). Despite the display of the date in CB as m/d/YYY, the date in SQLite is in ISO standard format of YYYY-MM-DD. This is important because... I.CoverDate = '2020-12-01' will return rows (assuming there is data with that value). I.CoverDate = '12/1/2020' will NOT return any rows. Also it has to be an exact match as all the digits are important: I.CoverDate = '2020-12-1' will NOT return any rows. And like Text, Date constants need to be contained in single 'tick' marks. Number: This contains Numeric information (Integer or Decimal). I.QtyInStock = 2 I.IssueNum = 0.5 I.IssueNum = -1 Binary: This is represented by a Check-box. It is a True/False or 1/0 value. As you can see it has two states. Basically, it translates to 'Is Checked' or 'Is Not Checked'. These are equivalent and will return rows where the CustomCheck2 check-box IS Checked I.[CustomCheck2] IS True I.[CustomCheck2] = 1 And, as you might guess, change to False or 0 to find if a check-box Is Not Checked. ******************************************** COMPARISONS: When using the Where clause, you are normally comparing a Column value to a constant to find something. Some comparison operators are: = Equal To <> Not Equal To < Less Than > Greater Than <= Less Than or Equal To >= Greater Than or Equal To These work as you would expect: I.Title = 'Batman' (Finds Only exact match) I.Title <> 'Batman' (Finds All except 'Batman') I.Title < 'Batman' (Finds All from !Gag! (Harrier) to Baticomic) I.Title > 'Batman' (Finds ALL from 'Batman & Robin (Panini Deutschland)' to '…One to Go') I.Title <= 'Batman' (Same as < but also includes 'Batman') I.Title >= 'Batman' (Same as > but also includes 'Batman') BETWEEN: Syntax is BETWEEN x AND y It is inclusive (meaning the value of X and Y will be included in the results). It is equivalent to using the >= and <= together. For example, these produce the same results: I.IssueNum BETWEEN 5 and 10 I.IssueNum >= 5 AND I.IssueNum <= 10 Either of these will find all IssueNum values of 5, 6, 7, 8, 9, and 10 (assuming only integer values and the value exists). Note: X has to be Less than (or equal) to Y for it to work. This is easier to see if you use the >= and <= I.IssueNum BETWEEN 10 and 5 is equivalent to I.IssueNum >= 10 and I.IssueNum <= 5 There can't be a value that is both Greater than 10 and Less than 5 IN: Syntax is IN (value1, value2,...) Searches for a list of possible value instead of just one. It is equivalent to using multiple = comparisons. For example, these produce the same results: I.IssueNum IN (5, 8, 25, 32) (Note: the values can be in any order) I.IssueNum = 5 OR I.IssueNum = 8 OR I.IssueNum = 25 OR I.IssueNum = 32 Either will find all IssueNum values of 5, 8, 25 and 32. IS: This one is a little different it only has a couple formats: IS True IS False It is mainly used for Binary Data Types. (NOTE: there is also an IS NULL but that should rarely be needed. What is does is check to see if a column contains NULL. NULL is nothing. It is not a 'space' or an empty-string. Rarely, you may need it if a column in CB allows NULL and you need to find them.) LIKE: Syntax is I.Title LIKE 'Batman%' This will find values but uses wild-card symbols to allow finding non-exact matches. The wild-card values are Percent ( % ) and Underscore ( _ ) where a % represents zero to many characters and _ is one and only one character. (NOTE: You can use multiple _ in a row to indicate a specific number of characters.) Examples: I.Title LIKE '%Batman%' will find anything that contains 'Batman' in it (NOTE: Just because % is at the beginning doesn't mean that there has to be something in from of 'Batman' in the Title.) I.Title LIKE 'Bat%Man' will find anything that starts with 'BAT' and ends with 'MAN' and may or may not have other values between them. I.Title LIKE '_Batman' will find anything that that starts with a single character before 'Batman' (NOTE: There has to be a value as this will NOT return just 'Batman') I.Title LIKE '_atman' (one underscore) will return anything that starts with some single character and ends with 'atman' (i.e. 'Batman', 'Catman, 'Ratman') I.Title LIKE '__man' (two underscores) will return anything that starts with two characters and ends with 'tman' (i.e. 'Batman', 'Catman', 'Hitman', 'Ratman') I.Title LIKE '______' (six underscores) will return anything with 6 characters (i.e. '10 Gen','Action', Batman', 'Zordon', etc.) (There are also some NOT versions, like NOT BETWEEN, NOT IN, and IS NOT but NOT logic is best left to Expert Advanced users (or insane ones...). Having said that, they can be useful on occasion so I am at least mentioning them) Boolean Logic Expressions: The Where clause uses Boolean Logic Expressions. Besides the more familiar operators (<, >, =, etc.), it also includes AND, OR, and NOT. They are used to concatenate single comparisons into more complex comparisons. For the Where clause, the comparisons have to end up as TRUE to return rows. With AND, all comparisons have to be True for the Where clause to evaluate as True and return a row. With OR, at lest one comparison has to be True for the Where clause to evaluate as True and return a row. Here is a list to show how this works (the values True and False are being used as the comparisons to emulate the result of comparisons): AND- All have to be True: 'True' AND 'True' evaluates to TRUE , row returned. 'True' AND 'False' evaluates to FALSE, row NOT returned. 'False' AND 'True' evaluates to FALSE, row NOT returned. 'False' AND 'False' evaluates to FALSE, row NOT returned. OR- At least One has to be True: 'True' OR 'True' evaluates to TRUE , row returned. 'True' OR 'False' evaluates to TRUE , row returned. 'False' OR 'True' evaluates to TRUE , row returned. 'False' OR 'False' evaluates to FALSE, row NOT returned. This is also the case for more that two comparisons: 'True' AND 'True' AND 'True' evaluates to TRUE, row returned. 'True' AND 'True' AND 'False' evaluates to FALSE, row NOT returned 'True' OR 'False' OR 'True' evaluates to TRUE, row returned. 'False' OR 'False' OR 'False' evaluates to FALSE, row NOT returned. You can use both AND and OR in the same Where clause but you need to be aware of the Order of Precedence (the order the expressions are evaluated in). AND is processed before OR. To make it easier on you, it is best to use Parenthesis to control the order the comparisons are done. Consider this: I.Title = 'Batman' OR I.IssueNum = 2 AND I.Printing = 2 OR I.Variation = 'HC' I.Title = 'Batman' OR (I.IssueNum = 2 AND I.Printing = 2) OR I.Variation = 'HC' At first glance, the first one is hard to tell what is going to happen. The second one, with parenthesis, is what it actually being done. With the parenthesis, it is easier to see that it will return Any Batman rows, along with Any rows with IssueNum 2 & Printing 2, along with Any rows that have a Variation of HC. While it is still a complex query, it should be easier to understand what will happen. Here is another similar comparison where the only difference is the ANDs and ORs: I.Title = 'Batman' AND I.IssueNum = 2 OR I.Printing = 2 AND I.Variation = 'HC' (I.Title = 'Batman' AND I.IssueNum = 2) OR (I.Printing = 2 AND I.Variation = 'HC') Again, while both will return the same rows, with the parenthesis, it is easier to see that this will return Any Batman with IssueNum 2, along with Any row that has Printing 2 and Variation HC. ******************************************** ORDER BY: There isn't much to say about the Order By clause. It pretty much does what you would expect. Sorts the resutls as requested. The one thing not obvious is you can control the direction of the ordering with ASC (the default value) or DESC. I.Title ASC would sort A-Z and/or 0-100 (ASC is the default and you don't need to add it) I.Title DESC would sort Z-A and/or 100-0 You can mix and match the use of ASC and DESC I.Title ASC, I.IssueNum Desc I.Title Desc, I.IssueNum Desc, I.Variation ASC Keep in mind the Data types when doing sorts. Number and Dates sort as you would expect. Text sorts characters from left to Right. If you have what looks like numbers in a Text field, the sort order would be 1, 10, 100, 2, 20, 200, etc. It would not be 1, 2, 10, 20, 100, 200. The following will sort the results the same way (or at least very similar) to the way CB sorts its display: I.Title, I.IssueNum, I.ItemType, I.Variation, I.Printing ******************************************** [start 2022-01-14 addition] DATA TYPES: Strftime: Strftime allows you to access a date in different ways. The basic syntax is: strftime(format, column-name) Some of the more useful formats are: %m month: 01-12 %d day of month: 00 %w day of week 0-6 with Sunday=0, Saturday=6 %Y year: 0000-9999 NOTE: the format character is case-sensitive. Use upper/lower case as shown. The Month format is probably the most useful as it can be used with both CoverDate and StreetDate. While Day of Month and Day of Week can be used with either, most CoverDate Day values are 1 (excepting items put out multiple times a month) and wont' really get you useful results. While the Year function does work, it is not as efficient as using BETWEEN: strftime('%Y', I.CoverDate) = '2002' takes 23 seconds to process I.CoverDate BETWEEN '2022-01-01' and '2022-12-31' takes 1.75 seconds to process You can also combine this with the BETWEEN function to limit the year ranges for a result. Some examples: Find all items with a day of '15': strftime('%d', I.StreetDate) = '15' Find all items with a day of '15' for years 2000-2009: strftime('%d', I.StreetDate) = '15' AND I.CoverDate BETWEEN '2000-01-01' AND '2009-12-31' Find all items with a day of Wednesday': strftime ('%w', I.StreetDate) = '03' [end 2022-01-14 addition] ******************************************** RANDOM NOTES: What is Item # and why not to use it in Order By: While Item # is the displayed value, it isn't the best field to do Finds with, in most cases. Item # is composed of 4 other columns. They are, in order, ItemType, IssueNum, Variation, and Printing. Item # 1/HC-2 is composed of: ItemType: none used (or regular issue but don't try to find regular issue in ItemType as it is only a display item) IssueNum: 1 Variation: HC Printing: 2 If you try to use Item # in the Order by, it will sort all ItemTypes first. Also, Item # is a Text field and NOT a numeric. You will also get 1, 10, 100-109, 11, 110-119, 12, 120-... This is why it is better to use the various components of the Item # instead of Item # itself when sorting to match CB order: I.Title, I.IssueNum, I.ItemType, I.Variation, I.Printing ====== Use of [] in Column names: Some of you may be curious what the brackets ( [] ) around column names are for (and why I don't use them). If the creator of a Table use a column name with a space (i.e. 'Issue Number') then it is required to enclose it in brackets ( [Issue Number] ) when referencing it so the database sees it has a 'single' name. If there is no space (i.e. IssueNumber), then the brackets are optional. Since the SQL processor adding the columns doesn't know if there are spaces or it, it defaults using brackets, just in case. It doesn't hurt to have them and not need them. However, to me, they just clutter up the display of the query (the less I have to look at and ignore, the better) so I never type them in when I write a query. A similar point could be made for parenthesis. Most SQL processors put way too many, unnecessary parenthesis in their statement. Don't get me wrong. As I showed above, parenthesis can (and sometimes must) be used to make the query either easier to understand or do what you want. But the over-use of them can make for a cluttered query. (Okay, my pet peeve part of this manual is over (for now...)) ====== [end 2021-12-30 addition to cover different Types and Columns] How to use Publisher Title columns in Advanced Find: One thing you may notice, is that only ISSUE columns are available in Advanced Find in the drop-down box. In the old days (pre-CB 2020) there used to be "I" (Issue tables) and "T" (Title tables) where you could access Publisher in Advanced Find. The "I" and "T" were qualifiers to indicate which table a column is in. --- Quick aside (geek alert)... The "I" in I.Title is the qualifier (or identifier) of a Table as defined in a From clause (since the From clause has not been displayed, you can see it directly). It is only really needed if you have more than one Table in the From and you Join them together (i.e. Issue table and Title table). The syntax would look like this: From Issue_Table I inner join Title_Table T on I.Title = T.Title The only thing you need to get from this is that the column Title is in both Tables. Because of this it needs to be qualified when reference (i.e. I.Title for the one int the Title_Table) --- Sadly, with CB 2020, only "I" table columns are (readily) available. However, there is a second way to qualify a column and that is with the actual Table name. So, while you can't select Publisher from the drop-down box, you CAN use it by qualifying it with the actual table name like this: ComicTitles.Publisher = 'Marvel' BookTitles.Publisher = 'Ballantine' MagazineTitles.Publisher = 'Time' ComicTitles.[CustomCheck1] IS TRUE BookTitles.[CustomCheck1] IS TRUE MagazineTitles.[CustomCheck1] IS TRUE NOTE: This is a non-supported feature which may or may not work in future releases of CB. (Maybe HC will make Title columns available in the Advanced Find in the future (hint, hint, hint, please...?) [start 2021-12-30 addition to cover different Types and Columns]
    2 points
  17. I have found this to be a pretty good site for books: https://isfdb.org/cgi-bin/index.cgi I also do some searches on Amazon and Ebay to see If I can see any inside information. PS Very good series, by the way. I would have got to it eventually but i have several hundred books to get through (and I started a Z and am working backwards to A as I rearrange my bookshelves...
    1 point
  18. Sorry, I meant to end sentences. they are valid in Name.
    1 point
  19. When the new CB2023 comes out (which is very very soon, according to the most recent Livestream), you could change the Media Type for the prop keys to be Newspaper. Then, when you do weekly content updates, make sure that your settings are for the Newspaper category to be not updated. Not the most elegant solution, I know, but it should work for you. Perhaps the best solution would be for CB to add a Media category of "Other" that *NEVER* has anything in it in the master database, but users can use it for whatever other stuff they collect (e.g., DVD/Blu-Rays, trading cards, statues, prop keys, etc). Since the master database wouldn't ever have anything in that category, the content updates would never disturb whatever individual users decide to track there.
    1 point
  20. @Mark J. Castaneda, this could actually be a good candidate for one of the new CB2023 features...
    1 point
  21. The 1972 date tells me that is almost certainly not an issue of Captain America but is actually a reprint book of some type (possibly Marvel Super Action or Marvel Triple Action). Edited to add: I have been able to verify that what you have is a copy of Marcel Super Action #2, which contains a reprint of Captain America #101.
    1 point
  22. Due to our Fiber installation for better internet last week; incoming emails we're either bouncing or being delayed. Adjustments have been made over the past few days to rectify it all.
    1 point
  23. Since you seem to have problems with connections, I went ahead and added the title 'Weird Western Tales (UK Edition) with issues 45-47 and 50-70 (not sure that 48 or 49 exists or not. Two sources I checked did list either). Hopefully, it will be in the next Update.
    1 point
  24. I had no idea all this stuff was being added to my database. What's the rationale? I did notice a paperback Tolkien novel in my database recently, and wasn't sure it was supposed to be there or not. IMO books should only be included if they relate to comics.
    1 point
  25. I love Add by Barcode but if I'm scanning a bunch of stuff and I accidentally scan different types in the same session, the resultant Save list won't show everything due to different types. This is a colossal pain, if I've scanned a whole bunch of stuff. For instance, I scanned a whole bunch of comics and unwittingly scanned a a comic-sized book that was typed as a magazine. The Saved results only showed the magazine. --Walt
    1 point
  26. I don't know what that means but I think we both want some way to better organize titles. The answer from CB shouldn't be "We're not going to do anything."
    1 point
  27. But, of course, that requires one to properly match your understanding of which type of item you are scanning with how it is currently entered in ComicBase...
    1 point
  28. I understand that. What I am looking for is that same ability to exclude Magazines.
    1 point
  29. Today I've run into another mess of titles that should be changed. I'm adding issues of Angel (the spin-off of Buffy the Vampire Slayer) to my database. ComicBase has six series of Angel listed, plus a magazine. Several of these are disparate titles that should be titled with their publisher names rather than as "1st series" or "4th series" or whatever. Right now we have: Angel - Published by Titan. Though listed under Comic Books, it belongs under Magazines (or possibly Books). The description says it collects articles from the Angel magazine about the TV show. Angel (1st Series) - A kid comic published by Dell in the 1950s. Angel (2nd Series) - The first Dark Horse run of the Buffy spin-off. Angel (3rd Series) - The second Dark Horse run of the Buffy spin-off. Actually a 4-issue miniseries. Angel (4th Series) - An unrelated manga title from 2003. Angel (5th Series) - An unrelated indie comic from 2004. Angel (6th Series) - The IDW series of the Buffy spin-off (which took over the numbering from Angel: After the Fall). Angel (Boom!) - The first Boom series of the Buffy spin-off. Angel (Boom!, 2nd Series) - The second Boom series of the Buffy spin-off. What a tangled web. Disregarding any desired changes to how series are named (using the year of first publication, etc.), this is all screwed up under the existing ComicBase guidelines. It should be more like this, if I have it right: Angel should not be in the Comics section. Angel (1st Series) should probably be Angel (Dell). Angel (2nd Series) should probably be Angel (Dark Horse, 1st Series). Angel (3rd Series) should probably be Angel (Dark Horse, 2nd Series). Angel (4th Series) should probably be Angel (Tokyopop). Angel (5th Series) should probably be Angel (Hi-Horse). Angel (6th Series) should probably be Angel (IDW). Presently, most of this can't be changed, so we have the implication that a kid comic, a vampire comic, a manga publication, and a black-and-white indie all belong to one group of series. It's messy and kind of bizarre.
    1 point
  30. I haven't moved on to putting my own titles in but moving the FCBD issues doesn't matter much. Thankfully the FCBD issues don't see a lot of action in their pricing. There are a few that have climbed a little but the vast majority stay at "cover price." I get what you're saying though. The lack of pricing would be a complete nightmare especially on long runs. The FCBD issues that make me really crazy are the ones that reprint some or all of a regular issue. The first one I remember finding (or not finding, technically) was Savage Dragon #148. I may even have submitted the FCBD version as a correction a few times. I understand that it has #148 on the cover but it's a FCBD issue. I listed mine as FCBD #2009.
    1 point
  31. I often consider putting the correct titles in my own database and just letting them stick out as "unrecognized" titles and issues when updates happen, but then my corrected titles and issues would never get updates, as they would no longer match Human Computing's master database. As one of my reasons for cataloguing my comics is to get documented value information for insurance (and also my curiosity), I want my values to be updated, so I stick with the ComicBase standard, even when it makes me cringe a little. I'll never be able to watch or participate in a livestream as it happens, but I've been catching up on the archived versions. This does at least have the benefit of allowing me to fast-forward the occasional conservative monologue, which I often find off-putting (no prizes for guessing that my views tend to fall toward the other end of the spectrum). Other than that, I've enjoyed the livestreams and learned a few things. I would like to see a discussion of these titling problems.
    1 point
  32. Sorry, that one makes me giggle every time. So yeah, I agree with everything above and have been bringing it up from time to time. My personal fix has been moving the various FCBD books (the actual ones) into their respective titles, entering them as FCBD 2017 or whatever year they were released. An alternative that I originally came up with was creating a "Free Comic Book Day" title for each year, putting all the titles in alphabetical order and then entering them 1, 2, 3,... I'm really glad I didn't do that now as the individual issues in their respective titles works really well. Additionally, I make it a point to add "Free Comic Book Day 20xx" to the notes so I have a fighting chance to locate all of the individual books for any given year. I've been working on pulling together every FCBD book and have been grouping them by year in my collection. I've struggled with Atomic Avenue as well. I'm frustrated with myself for never thinking of trying to add it in order to make my case.
    1 point
  33. I definitely expected as much but I still think it's sad since ComicBase is the defacto comic book database. I realize that CB is nearing 30 years old but there is so much mess in it that it makes finding some things near impossible. One has to constantly think how some might have cataloged a title. Did they: Lop it on to the same title from another publisher (eg. Blondie) Throw multiple different titles under the same pot (eg. ... Spider-Man Comics Weekly #1-157 Super Spider-Man with the Super-Heroes #158-198 Super Spider-Man and the Titans #199-230 Super Spider-Man and Captain Britain #231-253 ( no title, number or date in the indicia) Super Spider-Man #254-310 Spider-Man Comic #311-333 The Spectacular Spider-Man Weekly #334-375 Spider-Man and Hulk Weekly #376-424 Spider-Man and Hulk Team-Up #425-449 Super Spider-Man TV Comic #450-499 Spider-Man #500-552 Spider-Man and His Amazing Friends #553-578 Spider-Man #579-633 The Spider-Man Comic #634-650 Spidey Comic #651-666 All this leads to is someone creating a new title because they can't find an existing one (e.g. Super Spider-Man and The Titans) Ignore the indicia and add it to the bottom of a different title. Not pay attention to how other titles were organized. In the case of Metal Men or Star Wars or titles that have multiple series, scroll through the list hoping that the logo on the comic associated with the title is representative enough that you choose the correct before trying again. One of the selling points that Pete, himself, makes is how labeling your comics makes it easier to organize and find them -- that may be true for a few titles but this lack of consistency makes that claim nearly preposterous in quite a few cases. Not know the start of a title and just guess locking the first issue in stone and making the addition of previous issues impossible (e.g. DC Coming Comics) And those are just a sample of the cases that I've come across. I have a monstrous collection that I want to organize and these inconsistencies make it difficult to do so. I can't believe that these issues can't be resolved in a database (which is really the point of a database and that is to resolve inconsistencies). I'm hoping the ultimate answer is not "well it's set in stone now" so we can't do anything about it. Because then everyone is at the whim and mercy of whomever enters a new title and all everyone can do is hope that they enter it correctly. That seems like the worst possible answer. --Walt
    1 point
  34. There are several titles that work the same way and it makes me crazy too. Wait until you look at Star Wars. The first listing is Marvel from 1977 and makes perfect sense. The following title listing is Star Wars (2nd Series) from Marvel, 2015-present although it ended in 2020. The third series is also Marvel and started in 2020. Never mind those pesky Dark horse series with the same titles that ran 1998-2006 and 2013-2014. I know CB and how to find the series I'm looking for....most of the time. Imagine a newb looking for a book though. There are a total of 15 series titled just "Star Wars" (16 if you count Dark Horse's "The Star Wars") with 5 of them being published by Marvel when you throw in the Canadian Edition and the Newspaper Strip books. Granted, Metal Men is different in that they all came from DC but ultimately it's the same inconsistent cataloging. Personally, I would prefer the title followed by the year. My second choice is the title with the publisher in parentheses and then the year. More than once I have tried to enter what I sincerely believed to be a new title only to later learn that those books were already in CB just under a different publisher from the one actually listed in/on the book. I'm struggling to name any now other than "G.I. Joe, a Real American Hero" which was Marvel's baby from #1-155. IDW took the reins at #155.5 but it's still listed under the Marvel title. Then you have Fantastic Comics (Image) is was literally created with the intent of being the next issue of Fantastic Comics (Fox) but received its own listing even though it was #24. Crack Comics has two entries, one from the original Quality series and a second titled "Crack Comics (2nd Series)" even though it was the same thing that Fantastic Comics (Image) was, a part of what they called the "The Next Issue Project." They also did Silver Streak the same way as Crack calling the single issue from Image the 2nd series. I prefer the way CGD does it with each new publisher getting a new entry with a notation in the previous publisher's title to the effect of "numbering continues in Title X from Publisher Y."
    1 point
  35. I would contact support about this item. It has been reported a few times (that I know of) but I am not sure of any specific fix. You can try typing I.ItemDescription in the Where box to get it to return results until you can get a fix. PS Way back when 2022 first came out, I had to create a new database then export/import my data into it to get Item Description in the list. Hopefully there is a better solution. PPS In the mean time, maybe an Uninstall (of both CB and CB Resources) / Re-Install could help.
    1 point
  36. If you're using CB2022, you're running the latest build (22.0.1.1622)? If not, download/install it from your online account here: https://www.comicbase.com/mycb/Registrations.aspx If that doesn't work; please screenshot you're selling settings so we can have a look what you got set.
    1 point
  37. The best way to do this is to use one of the Custom Date fields (there are 2 fo them) and update it with the date you bought the items. Then do a Find (or Advanced Find) to find the range of dates you are looking for. The Advanced Find could include the sorting. For Advanced Find, use something like this: Where I.CustomDate1 BETWEEN '2022-01-01' AND '2022-03-31' Order By I.CustomDate1 DESC (If you want to sort in the opposite direction, leave out DESC) If you just do a Find you will need to click on the column heading to sort the Custom Date column. After that, select some or all of the rows, Right-click and from the pop-up menu select Quick Report. Note: Quick Report is (I think) the only way to get a report sorted the way you want. Any of the standard reports will sort by Title/Issue nunber.
    1 point
  38. I thought they were cool 20 years ago too. I literally have a short box full. Then I realized they manufacture their own exclusivity and hype. Very VERY few if any of their books have ever held value let alone increased. And if they did increase it was the book itself and not DF Certificate that had anything to do with it. I found 3 of their signed books that were limited to 75 copies in the $3 boxes at my LCS just 2 weeks ago. PLUS, they started marketing CGC Books. I found out the hard way they were not CGC Exclusive or DF Variants, but just regular old A covers of a book. So basically $80 to get a 9.6 of a book on pre-order. In most cases the books aren't worth $80 in 9.8. Rant over. If you see them for $5 or less go ahead and nab them. Just remember some poor schmuck paid a minimum of $20 for it at some point. I don't remember seeing any DF release under $20.
    1 point
  39. I don't want to have to re-learn the purpose of the established fields. The field names are fine as they are.
    1 point
  40. Way back in the day, this thread on the old msg boards took a look at suspect valuations in the database for some of Warren's magazines. Eventually the prices on those issues were "right sized" (more or less) but over the years since then unusual drift on some of those issues seems to have returned. Particular issues that I would suggest get a second look at pricing would include: Creepy (Magazine) #3, #5, #8, #11, #17 (holy cow!), #64 (because it is too low rather than too high), #71 (wow!), #78, #80 (!!!), #81 (!!!), #82, #84, #89, #96, #123. And probably also #12, #15, #16, #39, #72, #92, #103, #108, #132, #133, #137, #138, #142. I am less certain of the current market values for #1 and #2, so truly high grade copies of those issues might fetch the prices shown in the database. Eerie (Warren) #3, #7 (too low), #9, #28, #38, #39, #48, #63, #79, #81 (too low). And probably #13, #15, #17, #23, #25, #42, #47, #67, #68, #71, #73, #75 through #78, #90 (too low), #116, #118 though #120, #122, #123, #138 (too low). Similar comment re: issues #1 and #2 as for Creepy. Vampirella (Magazine) #3 (priced higher than #1?), #50, #68 (too low), #96, #100, #104 (too low), #111 (too low). And probably #14, #15, #19, #30, #70, #73, #92, #102, #103, #106, Annual #1. If #113 is truly valued at $2.7K, why in the world is #113-A only valued at $5.00? If Special Edition #1 is valued at $255, how is it that Special Edition #1 HC is only valued at $12.50?
    1 point
  41. Looks like some adjusting took place. Thank you.
    1 point
  42. good eye catching this one, we'll look into the pricing and adjust. Use the 'request price check' option in the software's internet menu next time you notice a price needing adjustment; it's the best way to get our attention for stuff like this.
    1 point
  43. The downside of this decision is that I can't enter nor scan covers for prior issues that I have unless, by some miracle, a first issue is discovered for a title that doesn't have issue numbers nor indicia. The current starting item number of this title in ComicBase is 1 with a cover date of June 1988. I have seen online scans dating as far back as April 1985 (over 3 years earlier). If the current decision stands, I'm basically at a stand still entering this title and, quite frankly, it doesn't give me a lot of confidence going forward when I next hit a similar road block. I've already run into a situation in ComicBase where I had issues of a title (without indicia) whose numbering continued from another title yet was indexed under the original title. I had to research outside of ComicBase to discover what the original title might be -- which seems crazy. It was Super Spider-Man and Captain Britain which were indexed under Spider-Man Comics Weekly because that's where the numbering originated. A note says "Title sometimes known as Super Spider-Man". I don't know how that helps. At any rate, I'm feeling a little frustrated here.
    1 point
  44. Well, THAT only took almost a year instead of "a week or so". Unfortunately, there were some changes to the exported reports used as input data that requered some redesign, and it took waaaaaaaay longer than expected. Shows what shrinking free time will get you... @Fred Slota, I've uploaded the fixed version here: Thanks for your patience, and I hope it fits your needs. Adam
    1 point
  45. The current CB value is $11,500. Mostly due to a Fine issue offered for sale at $4,300 on AA. Right now on eBay you can buy a CGC 9.6 for $250. This is EXACTLY why you shouldn't use an 'offered for sale' price on a thinly traded issue. It completely skews the value of the comic for everyone. Can you fix this pricing issue? https://atomicavenue.com/atomic/item/249771/1/Weird-War-Tales-64
    1 point
  46. Correct. I like functions and was glad you posted about it. I was just writing something up on that... While the Year component may not be as efficient, it can be used for Month, Day of Month, and (possibly) Day of Week. For example If you want all items put out in a particular Month (January in the example): strftime('%m', I.CoverDate) = '01' You can also constrain it to a Year range (Month January between 2010 and 2019): strftime('%m', I.CoverDate) = '01' and I.CoverDate Between '2010-01-01' and '2019-01-01' The Day of Month and Day of Week are probably most useful for Street Date as Cover Dates normally have Day of 1 (with bi-monthly or weekly being some exceptions) Not sure if they are useful or not but if you need them: All items with a Day of '15': strftime('%d', I.StreetDate) = '15' All items that came out on a Wednesday (Sunday = 0, Saturday = 6): strftime('%w', I.StreetDate) = '3' NOTE: the % value is case-sensitive. %m works. %M does not.
    1 point
  47. Also, in the screen shot where you type 'WEB', the drop down list of suggestions are NOT Titles (they are characters). Assuming the gray text in the box before you typed had 'Title name or barcode', try using the Find drop-down next to the box and select another item (i.e. Publisher) then select 'Title name or barcode'. (sometimes it loses what it is set for. PS The list of suggestion makes it appear that you have one of the appearances selected.
    1 point
  48. That would work. If you have an example of a case where it didn't go through or get accepted, send in a correction then email our team at support@comicbase.com and we'll take look at it.
    1 point
  49. First, I would be careful about adding Publishers. For example, 'Dream Weaver Press' would just be 'Dream Weaver' CB usually leaves of common endings for a Publisher. These include (but are not limited to) Press, Meida, Publishing, ext. Sometimes they are added if there are Publishers with similar names. If you do enter an 'incorrect' (from HC's perspective), and they catch it, they well change it. What this means is the next Update will add a New Title in your database with the 'correct' publisher which will be a duplicate of the one you entered. This should show up on the Unmatched Items list that is part of the Update. Not saying I agree with this but it is so ingrained in CB that it is not likely to change. PS I just check and CB already has Publisher 'Dream Weaver' (2 titles) in the database. How many Items are you importing? If it is a small amount, I would just import the minimum need to get the entry into CB This would be: Title, Item#, Condition, and Qty and either let CB fill in the info with Updates or manually enter it. If you have 'thousands', again, do as little as possible. Now for your questions. A) New Title not in CB. Double Click an issue to bring up the Edit window. In the top right corner should be an Edit Title Information button. Click it. Type in the Publisher. As you type suggestions for Publisher will be displayed. Either select the one in CB or finish typing in the New Publisher name. Save the change then Cancel or Save the Issue Edit window. B) Is the same as A. IF the Title is in CB and the name you have matches, it will go to that Title. If not, it will be imported with Unknown Publisher. C) No, there is no way to Import Publisher.
    1 point
  50. I love being able to check my collection on the go using the app, but I have a pretty long wish list and a ton of titles in my collection so sometimes I really need to scroll a lot to get to the title I am interested in. A drop-down list allowing you to jump directly to a title or being able to search would make the reports much easier to use. Is this doable?
    1 point
×
×
  • Create New...