Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 5/18/2021 in all areas

  1. 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
  2. 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]
    3 points
  3. 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
  4. 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
  5. 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.
    2 points
  6. 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
  7. That's my feeling as well for the same reason.
    2 points
  8. 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
  9. 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
  10. 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
  11. 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
  12. I would put your collection in some kind of order first. It can alphabetical, divided by publisher, divided by character, whatever works for you. Putting the books into CB won't be an overnight process and having some system in place will make it a lot easier to step away whether it is for a day or two or a few months and get right back into the groove when you return. Creating a space is a great thing to do if you can. Setting up on the dining room table is fine until you have to clear it off for dinner. If you can have some little corner to yourself, you can bring in a box at a time and get them entered. Assuming you are using regular comic boxes, whether the long ones or short ones, find a divider of some kind. I taped two backing boards together so they stood out above the books by a couple of inches. Put that divider at the back of the box, behind all of the books, then as you enter books, move them behind the divider. This keeps the books in a single box and in the order you started with while making it clear what has and has not been entered. Bar code scanner or no, if you're having trouble finding a book in CB, you can enter the UPC numbers by hand. It may be slow but if it's only for the random difficult to find book, it works really well. Given that your collecting took off in the 80s and 90s, it is possible that you will have some small press stuff that is either not in the system or is difficult to find. That's a great time to post on the forums to ask where they might be. Don't get discouraged! That's a lot of books to enter and will take time a regular life pushes comics out from time to time. You will get it done!
    2 points
  13. It would be interesting (to me at least) to have a better understanding of how database corrections are processed when they are submitted through CB via the "Submit New or Corrected Data" feature. Filling in an empty field seems pretty straightforward, but what if the correction is deleting duplicate or extraneous information? If someone thinks they have found a new title, is it appropriate to create an entry in CB first and submit it that way, or would that be better for the message board? How much headache do I cause when I upload a correction, immediately realize that I left something out or spelled something incorrectly, and then upload a corrected correction? What happens when I am trying to submit a corrected or larger cover image without any other data changes, and the CB software doesn't ask me for my cover? Did I just submit a "correction" that matches the master database 100%, and does that cause any confusion? Even if not, what is the best way then to get that cover-only correction to the team? I think having a better idea of how the corrections are processed or compared against the master database could help users decide whether it's best to submit something through CB, take it to the message board, or send a direct e-mail, and do so with the minimum amount of confusion for the CB team having to figure out the intent of the user while wading through multiple and duplicate submissions.
    2 points
  14. 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
  15. 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
  16. 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.
    1 point
  17. Yeah, that is normal. Shiny foil and scanners don't play well together and the result is usually a darker image.
    1 point
  18. I echo Joel's suggestion. The magazines and books in my collection are so few, I'd prefer to manually add those titles from the db and live without the thousands of other books and magazines. r/ Mike
    1 point
  19. I understand that. What I am looking for is that same ability to exclude Magazines.
    1 point
  20. Thank you for this. I'm not a computer guy so I get lost in the jargon. I believe what you are suggesting is exactly what I have in mind. That said, it concerns me a bit that I had the same thought because HC has people trained in this and that have actually built all of this. Wouldn't they have already hit on it?
    1 point
  21. After giving this just a little bit of thought, here's a solution that could solve the problem. Caveat: I'm suggesting this without knowing the intricacies of the DB structure. 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 changes it and voila, after the next update, the title can be found and sorted correctly. This would require a fairly strict naming protocol using the indicia and year of first publication as the name... something like Metal Men (1993 Series) although even if it gets messed up, it can be easily changed. This solution addresses some of the problems that @Peter R. Bickford brought up in the call yesterday. 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. 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
    1 point
  22. 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
  23. I *think* that in current practice the difference is that there is a function in the ComicBase program that allows you to change the media type of a title that you are viewing. This has the effect of allowing the user to shift their existing inventory for the old title that was in the incorrect media category to the new title that is in the correct media category. I suspect that this is relatively easy to program because the title name doesn't change at all, just the media category in which that title resides. For titles that get renamed, it's a little more complicated b/c you'd need to have a simple way for the user to point their inventory in the old version of the title to the new version since there are thousands of titles in the database... this is why I suggested that it might be easiest to do the inventory shift during the content update that actually adds the new version of the title. This isn't to say that the problem can't be solved, only that I am guessing that this is the reason why changing a title's name is more complicated than changing a title's format. (If I'm way off base on that, I am sure that @Peter R. Bickford can set the record straight!)
    1 point
  24. 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
  25. Maybe I am missing something here, but won't the settings shown in Don's screenshot result in reducing the price of his inventory by another 25% every day? Also, what happens if he wants to end the reduced price sale? Is there a way for him to bump up his prices by 133.33% (which is what it would take to restore his original prices prior to dropping them by 25%)?
    1 point
  26. 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
  27. 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
  28. Doesn't matter, ComicBase stills needs to catalog their stuff. 🤷‍♂️ 🙂
    1 point
  29. 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.
    1 point
  30. Dynamic Forces is EVIL. Enough Said. LOL.
    1 point
  31. You assumption is correct. Since the cover scan was manually deleted (outside of CB) it has no reason to change the value. I would still contact support and see if they can figure out why your original database isn't updating the Picture Information.
    1 point
  32. I have the same problem and have mentioned this to Pete. Here is what I sent to him "I think the reason you haven’t seen most folks post about the problem is that no one checks to see the backup. Sidekick looks looks like uploading to cloud was completed". Hopefully it will get resolved soon.
    1 point
  33. 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
  34. Barcodes aren't consistent between databases. If they're two entirely separate databases that like correspond to comics that are clearly delineated, then that's fine. But if you have an issue in the "sales db" that you sell and want to remove from the other db, or something like that, it can be tricky. Anyway, I actually know of another couple potential workarounds. So first of all, when I try to print something with qty > 1, then I get this prompt when I click "Print" or "Preview": Speaking of Preview, the preview window actually lets us export the print as a file. That highlighted button in the top left there allows you to export the "report" to an Excel or Word document, among other things. You need to be careful, as the margins might not be perfect or something. I'd recommend a test print on normal paper. I tried to delete some labels in LibreOffice and that proved to be a pain; it could be better in MS Word proper. But this might be a potential way to manipulate labels.
    1 point
  35. 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
  36. 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
  37. Go into your Sidekick settings General Tab. Review the database(s) you have listed. Make sure the db(s) you mainly use is listed. *We think you might another db you don't use in the list; select and hit the 'minus' button to remove it from the list. See if Sidekick messages you afterwards.
    1 point
  38. It would be extremely helpful if you would provide instructions as to how to change the folder that Comicbase uses to store the database. My old database file wasn't in my OneDrive folder, but Comicbase kept copying it over into OneDrive. Of even greater utility - when you pop up the warning message about saving into OneDrive perhaps you could have a dialog box that asks the user where they would like to have their database stored. You have options to redirect where the backups should be stored, it should be as easy to setup where the user wants the main database stored. Thanks!
    1 point
  39. 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
  40. I had to drop off a few minutes before the Livestream ended last night but I went back to see what I had missed later in the evening. I just thought I'd mention that the entire video was still available and nothing had been cut. I'm not sure when you plan on making the cuts but I thought I would flag it for you. Although I must admit I'm glad that nothing has been cut yet otherwise I would have missed the final announcement!
    1 point
  41. 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
  42. If the variants have different paper, usually that also resulted in a different cover price and that would automatically qualify those variants as trackable in CB as separate items. Personally, even if the cover price was the same, I would recommend that the variants be tracked separately if the paper stock is different. Maybe it is worth bringing this up at this week's Livestream?
    1 point
  43. uninstall your CB2021 edition AND the CB2021 resource file from your App list Next, refer to this article on what to do next:
    1 point
  44. you need to fully highlight the issues so any greyed out options become select-able.
    1 point
  45. I would suggest getting a barcode scanner (assuming you don't have one or that you can afford one). Barcodes started in the mid-70's. However, at the beginning, they used the same numbers over every year (i.e. the number used for Feb 1978 would be the same number used for Feb 1979). By the 80's, I believe, they were using the longer, more unique codes. CB has a lot of these already in the system (but not all, by any means). By using a barcode scanner, assuming the number is already in CB, with the 'Add by Barcode' menu item, it will find the issue being scanned, even if it is a non-intuitive location. If you don't have/want a barcode scanner, you will need to find each issue and change the Qty (in Stock) from 0 to 1 (or more if you have duplicates). If you know the Grade of the issue, you can change it on the 'Add by Barcode' window. Or you after entering the issues, you could use the 'Grading Item' menu option to get a general idea of the grade. If you have the Pro or Archive Edition, you can set up Custom Fields for thing like Location (box number). If you can't find a particular Issue, post information (and a cover scan would be helpful) and someone may be able to help you find it.
    1 point
  46. 1 point
  47. I second, this suggestion.
    1 point
  48. I'd also like to have the ability to use the original UPC barcode...A number of comics either don't include the barcode (older direct sales) or have the barcode on the back of the issue, which is obviously not visible when bagged.
    1 point
  49. Just finished watching the livestream #43 where Pete asks for ideas for the picture for the front of the next version of comicbase. Previous covers have covered golden age horror, crime, sci fi, and super hero genres. The one category missing is romance. Many of the golden age publishers did romance titles. For example a cover based on for example any of the issues of Secret Love by Ajax or similar would be my shout. Take care folks.
    1 point
  50. It might be a good idea to add the Mark/Unmark back to the context menu as well. We omitted it since the menu seemed to be getting awfully long, but it'd likely be a good idea to put it back. (You never really know how much some features are being used until you try omitting them from a version!) -Pete
    1 point
×
×
  • Create New...