Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/1/2021 in all areas

  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. You are doing nothing wrong. It is a little quirk in the system. To get around it what you need Type until you get where it is different, press the space bar, then backspace to delete the space. This will un-highlight any of the suggestions allowing you to type in the name you want. So, in your example, Type 'Magician ' (note the space after Magician) the press the backspace. This will leave just 'Magician' (without space) and no item in the list highlighted.
    1 point
  18. Hi mark,done it again and updated fine,and the program is much smoother than cb2022
    1 point
  19. Apple i think has this kinda of tech. We'll suggest it to the programming team.
    1 point
  20. Mark, I've submitted the corrections for the B&V Friends Forever titles (Archie and Friends was already done). I did note that B&V Friends Forever: Halloween Spooktacular was not yet deleted as a title
    1 point
  21. The problem you are having with the pictures (not the speed) doesn't sound like it should be happening. You might give support a call and see if there is something that can fixed.
    1 point
  22. I don't recall reading about anyone trying this before (they may have but just never mentioned it). You can definitely place all the Pictures and Media on the NAS. For the Archive Edition, this takes up the most space. You can locate the actual database file on the NAS. As for the actual executables, during the installation process, there is a path for the location of the install. But I am not sure if parts would be installed in normal Windows locations (some of which are Windows 'hidden' folder) on your C drive. Consider that A) the actual executables don't take up much space and B) HC doesn't have a problem with installing CB on two computers (think desktop/Laptop but I am not sure if they have a limit on how many other computers or not).
    1 point
  23. While they are very different in the type of correction, they're not different at all to the user with those titles in stock. One is a fix of typographic errors that border on unnoticeable, the other is a fix to titles that were entered using a variety of methods over a long period of time creating difficulty for users. Both require the user to either move their entries to the new title or miss out on the benefits included with CB. Either way, the decision is made that one is worthy of an end user having to make a tweak to their database while the other is not. It's absurd to me that having users move entries for a deleted space is acceptable while leaving series with the same title a complete mess for fear of confusing the users is a good idea. Additionally, these flaws are not just a difficulty for CB users, they become a difficulty for Atomic Avenue users as well. While weeding through Metal Men, one is likely to come across the title they are looking for within a very short time. If one searches for Avatarex, they are very likely going to find it with or without the space after the ellipsis. If looking for the Justice League Spectacular (as mentioned in another thread) a new CB user will have considerable difficulty if they find it at all. If looking to purchase the book, many potential Atomic Avenue customers will likely stop looking pretty quickly, costing sellers potential buyers. When pushing for a fix on these series' titles, I'm not even saying it needs to be done my way. It does need to done in some way that is quickly and easily recognizable to the newest user. I am quick to recommend CB when people ask for a way to catalog their collection but I do it with the caveat that the titles don't always make sense and that one may have to search a bit to find the correct title for their book.
    1 point
  24. So what is the threshold for it being "okay" to change a title? This week, I had two come back as Unrecognized Comic Titles. They were "Avatarex (Grant Morrisonā€™sā€¦ )" and "Night Terrors: Graveyard Moon (John Carpenterā€™sā€¦ )". They were changed to "Avatarex (Grant Morrisonā€™sā€¦)" and "Night Terrors: Graveyard Moon (John Carpenterā€™sā€¦)". I'l wait while you find the difference. SPOILERS BELOW.... Did you find it? Did you find that a single space after the ellipsis in each title was removed? A SINGLE SPACE. We changed two titles for a single space in the title. How is this acceptable but it is somehow not acceptable to change titles as mentioned in this thread to fix them so that they make some kind of sense? We have discussed how it might inconvenience some collectors and prevent them from getting updates to the titles that they own. Why inconvenience some collectors for the sake of a single space in a title but not others to make huge corrections to make the db follow some sensible order?
    1 point
  25. I'm glad it's working for you now. Steve is really the go to guy and has helped me numerous times.
    1 point
  26. I just had an interesting time finding this issue. There is no title entry for Justice League Spectacular as it's indicated in its indicia and it was published too early for it to have a barcode. I couldn't believe that it hadn't been indexed, so how did I find this comic? Search by writer and artist? No, it's Dan Jurgens so that would have brought back too many issues. So I ended up searching the StoryLines field, hoping that the story title had been added to that field. Luckily, it had. The issue ended up being indexed under Justice League America as Item # SP 1/B. Obviously, someone decided that this issue should be buried under a different title. Is there a chance that this can be pulled out, and have its title created? Again, I love ComicBase, but I find this aspect of using it frustrating as it just slows me down from entering my very large collection. I hope that these criticisms are being taken in the spirit they are given -- to help, in some small way, to better ComicBase.
    1 point
  27. Good points, I'll mention your reply to the programming team for them to have in mind. At the moment, there are no plans to tweaking the Add by Barcode process.
    1 point
  28. Hi, Mark-- Thanks for your response but that's actually the problem. Let's say I have a batch of 100 comics I'm Adding By Barcode and I unwittingly happen to have a something that's comic-sized in the bunch but classified as a magazine in ComicBase, I'm basically SOL when I save (this is what happened to me). If I have to look up all my comics up front to see if I happen to have a comic-sized item that's a magazine, it seriously defeats the purpose of Adding By Barcode. The Add By Barcode dialog does not show the category type of the top item and even if it did, it would still be mostly useless as anything that's miscategorized will trip up the Saving of the list. It also doesn't matter what you're currently looking at in the title view. I can add anything and since I don't know how it's categorized, I might be in for a rude surprise when I save, and that's bad since I want to update some custom fields. It seems to me that each issue must have a type (book, comic, or magazine) that should be accessible through title. If it can be looked up and added, then its type should be available and displayed. Or based on you comment, if the first thing you scan is a comic, it should reject anything that's not based on that type. I actually prefer this approach. I also hope my criticisms are taken in the spirit they're given. I like ComicBase. These suggestions are only to help it be better and more user-friendly. Best, Walt
    1 point
  29. quick reports aren't available to be uploaded to the mobile app. I'll mention it to our programming team for a feature suggestion.
    1 point
  30. 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
  31. I don't fully understand this statement but I believe it follows with my earlier comment about an identifier on each title that was not the title itself. Again, I'm not a database guy but what if the titles as they are now were to become the "foreign key" on some titles? It would only need to be done on titles that are being updated. I seriously doubt we are doing presenting anything that hasn't been looked at before but sometimes this kind of discussion is what it takes to come up with a new solution.
    1 point
  32. It's a shame that there will be no action on this as there are remedies to fix titles. I was stunned to learn that the foreign key that links titles and items together is the title itself and not a unique identifier of some kind. I understand this is a legacy problem and sympathize but it seems strange that the answer is inaction especially for a product that emphasizes organization. At worst, a new title field could be implemented that is curated by ComicBase following a well-defined standard and that could be activated via a preference. Until then, if ever, I guess we'll have to live with the existing disorganization. ā˜¹ļø
    1 point
  33. Thank you, I appreciate it very much!
    1 point
  34. 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
  35. Yes. With CB closed, you can use File Explore to rename any CB database or backup file to any name you like (just leave the extension the same). Since CB will try to open the last database that was in use, you should double click on the newly renamed database to get CB to open it directly. PS you can also copy a backup file to another location and rename it so you have the original backup, if you need it.
    1 point
  36. Currently only Collection Report and Item Checklists, Price List, and Wanted List have the ability to display Custom Fields (You can make a request for this to be different under Feature Suggestions.) However there is a way to get what you want with a few extra steps. This is to use the Marked box (you can't be using Marked for other things at the same time, though). 1) Run the find like you want. 2) Select All Items (CTRL+A is one easy way to do this). 3) Right-click and select Quick Change. 4) Change: 'Marked' To: 'Is Checked' Once the items are Marked you can: 5) Use Report-> (report type) where Report type is one of the Reports that allow Custom Fields (Collction Report or Item Checklists are probably the best) 6) On the Report window, check the boxes for 'List Only Marked Issues' and teh various 'Custom Fields' you want. (You can make other selections but you need to check at least these) 7)Run the Report. NOTE: You will need to Find the Marked Issues and change then to 'Unchecked' to clear the Marked field before using it for anything else that would look for Marked being Checked.
    1 point
  37. My experience has been that they are slow to ship, ship the wrong items, and then are impossible to contact. They do occasionally hit upon a good idea, though. John Romita Sr. and Alex Ross have done some sketch covers for them and both are near impossible to get sketches from at all. If I'm getting anything produced by them, it's definitely going to be on the secondary market.
    1 point
  38. Thanks for the info, Scott. I didn't know all of that about them.
    1 point
  39. removing the wrong spelled title listing. Looks like its already listed under the proper name 'Aquaman/Justice League: Drowned Earth Special'
    1 point
  40. 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
  41. I am not sure who manages the forums but I sent Pete a message on Slack about it.
    1 point
  42. Again, we're in agreement, you're just more eloquent in stating it.
    1 point
  43. Yes, that's what I was getting at. The sketch variant for Antoine Sharp: The Atheist was only released signed and graded. The problem arises when somehow, books marketed through DF and Midtown wind up in here when there is no actual variation. They take a standard issue or variant, grade it, and charge a premium for it. I don't have a problem with the business model but it has never met what I would consider to be a threshold for a "variant" in and of itself. My understanding that this label was a one-off for CGC strictly for this book, so no, we can't send one in and get that one. And yes, we're on the same page here, these are the only two exceptions that I am aware of in CGC actually making a book a "variant," although one could argue that it didn't really happen with the Atheist book since there was no special label. Once cracked out, unless it's with a CGC Witness, it's just a signed book at that point. Nothing on the book or label mentions the limitation.
    1 point
  44. I just checked and everything seems to be working again with Sidekick.
    1 point
  45. I think HC takes the week between Christmas and New Years off so I don't think there will be an update this week.
    1 point
  46. this one will be added with the upcoming content update.
    1 point
  47. Until this feature is implemented (if it is), here is one work-around. Do a Find for Qty in Stock >= 1. Once the results are displayed, select / hi-light multiple issues. Right-Click and select Download covers from the pop-up menu. NOTE: There is a limit (not sure what it is) on how many covers you can download at one time. Depending on the number of Items you have, you may have to do this several time.
    1 point
  48. 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
  49. 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
  50. Last week was Hell Week for the message board servers and a few other things, so there was no livestream while those things received maintenance. I havenā€™t heard anything about this weekā€™s livestream, but I *assume* that it isnā€™t happening since no link has posted yet only 12 minutes before the usual showtime.
    1 point
×
×
  • Create New...