Difference between revisions of "Talk:Legion Publication History/2004-2006"
Craigopher (talk | contribs) (→How to handle multiple covers?: Thanks for the feedback) |
|||
Line 11: | Line 11: | ||
: X | : X | ||
: where "X" is a cover. -- [[User:Mgrabois|Omnicom]] 17:17, 1 October 2006 (PDT) | : where "X" is a cover. -- [[User:Mgrabois|Omnicom]] 17:17, 1 October 2006 (PDT) | ||
+ | |||
+ | ::Good suggestions all. We can create the XX scenario by breaking out a separate table for that issue - I'll give it a shot. | ||
+ | ::-- [[User:Craigopher|Gopher]] 18:57, 2 October 2006 (PDT) |
Revision as of 18:57, 2 October 2006
How to handle multiple covers?
First time I've run across this with covers I have uploaded so far, but there will be more instances of this coming (JSA classified, first Supergirl and the LSH issue). Justice League of America v2 #1 was published with three different covers. I have uploaded the initial image as JLAv2-01A.jpg, with the intention uploading -01B and -01C sometime shortly.
We can either represent this issue one time in the LPH, or three times with all three linking to the same issue page (or multiple pages I suppose). All three cover images would be included on the issue page (I'm thinking as a gallery). All three versions of this issue were published on the same date, but in the case of Supergirl & the LSH #16, the 2nd printing version was released on a different date than the original. In the case of multiple publication dates, I'm leaning toward multiple entries in the LPH; those with same the date I could go either way. Any thoughts? --Gopher 15:17, 1 October 2006 (PDT)
- I think SLSH #23 has a variant cover, too. My thoughts: include each one in the LPH as it occurs, so you'd have 2nd and 3rd printings in consecutive months, but only once for variant covers (like JLA #1). For the multiple covers in one month case, maybe display the covers next to each other, so you'd have something like this:
- X
- X
- XX
- X
- where "X" is a cover. -- Omnicom 17:17, 1 October 2006 (PDT)
- Good suggestions all. We can create the XX scenario by breaking out a separate table for that issue - I'll give it a shot.
- -- Gopher 18:57, 2 October 2006 (PDT)