How do I enter Multi-Title Trade Paperback Issues?
Realms allows you to enter multi-title trade paperback (one where the issues included come from several different titles) in several ways, varying by the amount of detail you wish to enter for the issues contained in the TPB.
Below is an explanation of what I call the Summary Version of the TPB Entry process (intermediate level of detail - allows for tracking of TPB contents, but no detail beyond that). You also have the option of using use the No Detail version (least amount of entry, but no issue specific info), or the Detail Version (most detailed entry, where TPB contents are entered just like regular issues, with some minor differences to insure data accuracy of your collection).
TPB Entry - Summary Version:
Let's use, as an example, the Uncanny X-Men: Mutant Massacre TPB from Marvel. You can also use this window to enter single Title TPBs that you enter as their own title, for example, the Preacher TPBs - click here for details on how these differ from the multi-title TPBs.
On the issue detail window, there is a TPB issues field, where you can enter the issues included in a trade paperback (1 - 6, for example). This works fine for TPBs where the included issues are all from the same title (Preacher, for example).
If records already exist for the TPB, they will display under the TPB Issues field when you click on it or tab to it, if the data is too big to fit in the field itself.
When the TPB includes issues from multiple titles, to enter this information, click the TPB Issues button. This will bring up the Multi-title TPB issues window (see below), where you can enter the titles and issues included (BTW, the Mutant massacre example may not be accurate as I don't actually own this TPB).
The Multi-Title TPB issue works a little different than most in that the entries are made directly into the list. There is no "properties" window, so to speak. I chose to do it this way because of the limited information entered for each issue. It just seemed like overkill in this case to have a separate properties window for data entry.
NOTE: The Missing Issues report will include these records in it's determination of missing issues if you turn the Include in Missing Issues check box on. The MI report sorts these records by Part Number, then by the numeric value of the Issue Number. So, for the report to use these accurately, the part numbers must be in the correct order. In edition, single title TPBs entered as their own titles must be entered a little differently to get the MI report to work properly.
Single Title TPBs entered as their own titles
Many people, myself included, enter TPBs as separate titles, instead as issues of the title they contain. For example, I have Preacher entered as a title, and I also have Preacher: Gone to Texas (TPB) entered as a separate title. If I want the issues contained in Preacher: Gone to Texas (TPB) (issues 1 - 7) to be used in the Missing Issues report for the title Preacher so that issues 1 - 7 will not show up on the report, I can use the Multi-Title TPB window to do that.
But, because of the sorting, you must enter the issues a s a range (1-7) as opposed to entering individual issues with separate part numbers. Otherwise, if you have several TPBs for the same title (again Preacher is a good example), the issues will not appear in the correct order, and the MI report will be incorrect. For example, if you also own Preacher: Until the End of the World (TPB), which contains issues 8 - 17, and you enter just one record in the Multi-title TPB window for each of the two TPBs, one with a range of 1-7 and the second 8-17, you can leave the part numbers as 1 on each and everything will be correct.
If you enter them as separate records (7 records for Preacher: Gone to Texas (TPB) and 10 records for Preacher: Until the End of the World (TPB), you would have to make sure the part numbers also kept that numbering, otherwise they would be sorted in the following order: 1, 8, 2, 9, 3, 10, etc.
Bottom line is for single title TPBs, enter the issues as a range. As of version 5.0.99d, this should actually be fixed, but I still think you're better off doing it this way.