Editor wiki

From GCD
Jump to: navigation, search

Last version before going to non-lasso site

Variant Issues

Dealing with the Error List

Current and past list of editors

Formatted version of the GCD Cheat Sheet

Information Storage Page - a place to put information for preservation

Reservations for series that have yet to be released

Duties of an Editor

Per a Board vote of 2012-09-04:

  1. An editor must join the editor mailing list to stay current with topics. While not required to participate, they must read the posting on the mailing list and follow the discussions with attention. Joining the policy list, while not required, is recommended.
  2. An editor must be committed to following and enforcing the formatting rules as currently set forth. Where the formatting documentation is not clear the editor should seek the advice of other editors to determine if data has been entered satisfactorily. Consultation of other editors can happen either on the Editor list or by placing an index in discussion mode, or both, depending on the circumstances of the situation.
  3. The duty of an editor is the approval of indexes and covers. As often as possible an editor should log into the pending queue and examine indexes for approval. Editors may also check the error list and make such corrections as they are able and willing.
  4. Editors should also be willing to help mentor new indexers.

Becoming an Editor

Per a Board vote of 2012-09-04:

  1. Indexer must have done enough indexing to have become a voting member of the GCD.
  2. Indexer has indexed some complete books, as opposed to just tiny changes to already existing indexes.
  3. Indexer has satisfactorily demonstrated that they follow the current indexing rules, so far as our "rules" are codified
  4. Indexer has either asked to become, or another editor has proposed them to be appointed as an Editor.
  5. Elections:
    • Require that all votes to grant Editor status must have a quorum of at least 50% plus 1 of the eligible Editors voting to be valid.
    • Require that all votes to grant Editor status must have at least 75% yes votes of those Editors voting on the question to be valid.

Approving Covers

Reviewing and Approving Covers

Approving Indexes

Go to the Pending tab after logging in. There are links to all the publishers/imprints/comics etc. that have been finished by an indexer but not yet approved by an editor. Clicking on the Name of the change will take you to a Change Point screen where the before and after of the change will be shown. Any field highlighted in yellow has been changed. At the bottom of the page are Assign and Add Comment buttons. Assigning will put the index into your Reviewing queue, ready for approval or rejection back to the indexer.

Things To Check When Approving an Index

  • Cover sequence includes the total page count for the entire issue.
  • Most (but not all) comics have a total GCD page count of 8n + 4. If a new indexer submits an index with a cover page count that is either an exact multiple of 8 or that is not a multiple of 4, the total page count should be confirmed before the index is approved.
  • Writer field need not be filled in the cover sequence. Editor field only needs to be in the cover sequence unless there is a change.
  • Check for required fields (or even entire sequences) that are missing. This can be hard to do sometimes, because most fields do not show up on the website unless they are filled in - so you have to remember to "look for what is not there" as well as looking at what has been entered.
  • Here are some places to look:
    • Cover sequence - should have 4 fields filled in above the Format information:
    • Publisher, Publication date, Cover price, Total page count.
    • If less than 4 of these are present, or the Format information is missing or inadequate, the indexer should be contacted for more information.
  • Stories/features table:
    • Interior sequences should have:
    • Page count - or explanation of missing count
    • Feature - unless a story is not part of an ongoing "strip", or the sequence is a minor Type like Advertisement or Promo
    • all Credits fields except Editor - with an exception for minor Types like Ads & Promos?
  • Use the "Series info" link to compare the SeriesBegan and SeriesEnded dates on the Series information page with the Publication dates of the first & last issues. If these do not match, contact the indexer to find out whether the Series or Issue date information is wrong.
  • Check the cover scan (if present). On recent comics, the credits printed on the cover are a good way to "spell-check" the indexed credits.
  • Add up the interior sequence Page count fields. The sum of these should be 1-20 pages less than the Cover Page count field (depending on whether or not Ads & Promos have been indexed).
  • Check that "Story" Type sequences are actually stories - since Story used to be the default Type, sometimes Text stories or other Types were indexed as a "Story" by accident. (If a "Story" has the "No Pencils" and "No Inks" boxes checked, this is a good sign that something is wrong.)



Is the site down?

PINGING THE SERVER At the command prompt, type "ping www.comics.org". The command prompt is reached, through Windows, by Start --> Programs --> Accessories --> Command prompt . ping reports whether or not a machine is reachable over the 'net.

If ping fails, it means either the machine is not running, or there is a problem with the network connection between you and it, or the machine's administrator has configured the machine to ignore ping (the latter is not the case with our server). If it succeeds, that means that the machine is up and there is a network path between you and it.

If ping succeeds but you can't access the main page, then that means there's a problem with the web service running on the machine.

If you can reach the main page, but can't access the database (the OI or the search pages), then the web server is running but either the database is down, the middleware is down, or one of the connections between the three is broken. The middleware (software that passes data from the web server to the database and back) in our instance is django.

Approval workflow for the new site

[Issue is not reserved]

1. Indexer makes change and submits.

[Issue reserved to Indexer and appears in Pending queue.]

2. Editor assigns a submitted change to himself for review.

[Issue still reserved to Indexer, but also in Assigned state.]

2. Indexer and Editor may go back and forth discussing, Indexer may make additional changes.

[Issue still reserved to Indexer but may be in either Pending or Assigned state.]

3. Editor either approves the change if Indexer has made appropriate changes, OR rejects the change if Indexer has refused.

[Issue changes are *live* on site if approved, OR are discarded if rejected.]


NOTE: If you, in the role of Editor, just want to comment on the change in a way that is visible in the change history but doesn't show up on the index page, there *is* a field for that that does *not* require assigning the issue to yourself. Only fields that display in the index page require approval, such as the regular Notes field.