Keydate: Difference between revisions

From GCD
Jump to navigation Jump to search
(Flesh out examples based directly on approved text. Add backlink.)
No edit summary
Line 31: Line 31:


Definition approved by the Senior Editors (May 2, 2008)
Definition approved by the Senior Editors (May 2, 2008)
Current Schema: Issues table, Key_Date field


Comments from the discussion on the Editor's list after this was released: Could use Classics Illustrated as another example of weird keydates, "Books of a series that list only the year are not mentioned.  I know that I am in the minority but our rule of we should be able to index the issue in hand makes using the issue number very effective for sorting and would only affect the most anal of chronologists.  This is how I do Femforce.  I have no desire to look up dates that really do not matter.", "Maybe the wording could be tweaked a bit to make clear that the key date is always based on the publication date, rather than the shipping or on-sale date.  Recently discussed exceptions (not mentioned in this summary) can occur with books that give a publication year only (such as annuals or books); where I believe it was agreed that we could(*) add a publication month if known. (*)I don't recall if we discussed whether this was simply an option (could be done) or a desire (should be done).  I also don't recall if a consensus was reached on whether "enhanced" publication dates should reflect shipping month or same publishing month as monthly books from the same publisher released at the same time.  I would assume that if you "enhance" the publication month, then the key date should be based on your enhanced publication month."
Comments from the discussion on the Editor's list after this was released: Could use Classics Illustrated as another example of weird keydates, "Books of a series that list only the year are not mentioned.  I know that I am in the minority but our rule of we should be able to index the issue in hand makes using the issue number very effective for sorting and would only affect the most anal of chronologists.  This is how I do Femforce.  I have no desire to look up dates that really do not matter.", "Maybe the wording could be tweaked a bit to make clear that the key date is always based on the publication date, rather than the shipping or on-sale date.  Recently discussed exceptions (not mentioned in this summary) can occur with books that give a publication year only (such as annuals or books); where I believe it was agreed that we could(*) add a publication month if known. (*)I don't recall if we discussed whether this was simply an option (could be done) or a desire (should be done).  I also don't recall if a consensus was reached on whether "enhanced" publication dates should reflect shipping month or same publishing month as monthly books from the same publisher released at the same time.  I would assume that if you "enhance" the publication month, then the key date should be based on your enhanced publication month."
----
----
back to the [[Formatting Documentation]]
back to the [[Formatting Documentation]]

Revision as of 07:27, 1 March 2010

  • Required.
  • A 10 character code in the form YYYY.MM.DD, unique to every distinct issue in a series and used to represent the publication date of the comic for sorting purposes. This field is required for easy chronological sorting of issues, but is not shown in searches on the website.
  • The YYYY represents the four-digit year the issue was published. If the publication date spans two years (e.g. December 1968-January 1969), use the first year.
  • The MM represents the month. For bimonthly publications that list more than one month in their indicia (e.g. January-February 1955), the Keydate should be based on the first month. For quarterly publications, "Spring" issues should be indexed as "04", "Summer" issues should be indexed as "07", "Fall" issues should be indexed as "10", and "Winter" or "Holiday" issues should be indexed as "01" or "12", depending on whether they were published early or late in the year. If the month of publication is not known, either "00" or "13" may be used for MM. "00" is used for an issue published before issues for which a month is known, "13" is used for an issue published after issues for which a month is known.
  • The DD represents the day. If the exact day of publication is known, it should be included here. Otherwise, for a monthly series DD is represented as a standard value of "00". For comics with a frequency greater than monthly where the exact day of publication is unknown, "10" and "20" should be used on biweekly books, "10", "20", and "30" should be used on biweekly comics where the comic has three issues published during a month and "10", "20", "30", "40" and up to "50" should be used on weekly comics.
  • Some series such as Dell's Four Color have the keydates entered in by pattern, since the months of the individual issues are generally unknown. If the keydate for an issue is already filled in and doesn't match the published date for the comic, the indexer should contact an editor to investigate whether it is one of these special patterns.
  • Making sure that the issues in a series sort in the correct order is the most important thing in establishing the Keydates, but trying to get as close as possible to the actual publication date of a comic makes searching across series by date more likely to be correct
  • Examples:
* 1980.02.00 (for February 1980)
* 1945.01.00 (for January 1945)
* 2002.06.09 (for June 9, 2002 or 9 June 2002)
* 1960.00.00 (for unknown date in 1960 or unknown date in the 1960s)
* 1953.04.76 (for Four Color issue #476)
* 1941.01.00 (for Winter or Holiday 1940-1941, published in 1941)
* 1941.04.00 (for Spring 1941)
* 1941.07.00 (for Fall or Autumn 1941)
* 1941.12.00 (for Winter or Holiday 1941-1942, published in 1941)
* 1990.09.10 (for first bi-weekly issue in September 1990)
* 1990.09.20 (for second bi-weekly issue in September 1990)
* 1990.09.30 (for third bi-weekly issue in September 1990)
* 2001.10.10 (for first weekly with no day in October 2001)
* 2001.10.20 (for second weekly with no day in October 2001)
* 2001.10.30 (for third weekly with no day in October 2001)
* 2001.10.40 (for fourth weekly with no day in October 2001)
* 2001.10.50 (for fifth weekly with no day in October 2001)
* 1960.00.00 (for 1960 or [circa 1960] or [circa 1960s])
* 1960.00.13 (for 1960 or [circa 1960] published after a 1960 issue with a known date)

(end of definition)


Definition approved by the Senior Editors (May 2, 2008)

Comments from the discussion on the Editor's list after this was released: Could use Classics Illustrated as another example of weird keydates, "Books of a series that list only the year are not mentioned. I know that I am in the minority but our rule of we should be able to index the issue in hand makes using the issue number very effective for sorting and would only affect the most anal of chronologists. This is how I do Femforce. I have no desire to look up dates that really do not matter.", "Maybe the wording could be tweaked a bit to make clear that the key date is always based on the publication date, rather than the shipping or on-sale date. Recently discussed exceptions (not mentioned in this summary) can occur with books that give a publication year only (such as annuals or books); where I believe it was agreed that we could(*) add a publication month if known. (*)I don't recall if we discussed whether this was simply an option (could be done) or a desire (should be done). I also don't recall if a consensus was reached on whether "enhanced" publication dates should reflect shipping month or same publishing month as monthly books from the same publisher released at the same time. I would assume that if you "enhance" the publication month, then the key date should be based on your enhanced publication month."


back to the Formatting Documentation