PubGizmoSysop: Claude re-edit

2026-06-05T17:48:55Z

Claude re-edit

← Older revision		Revision as of 13:48, 5 June 2026
Line 3:		Line 3:
	The Editions sheet records each published format of a title — paperback, hardcover, ePub, audiobook, etc. Each row represents one edition.		The Editions sheet records each published format of a title — paperback, hardcover, ePub, audiobook, etc. Each row represents one edition.

	== ~~Column Notes~~ ==		== Columns ==

	=== Title ===		=== Column A — Title ===
	'''~~MATCH WARNING:~~''' This must exactly match the title as entered on the [[Onboarding Import: Titles\|Titles]] sheet. Use the title only — do not include the subtitle.		<span style="color: #E6A817;">'''Match Warning'''</span> — This must exactly match the title as entered in Column A of the [[Onboarding Import: Titles\|Titles]] sheet. Use the title only — do not include the subtitle.

	=== ISBN ===		=== Column B — ISBN ===
	Import will accept valid ISBN-13s with or without dashes.		Enter the ISBN-13 for this edition. Import will accept valid ISBN-13s with or without dashes.

	=== Edition Format ===		=== Column C — Edition Format ===
	To simplify data entry, PubGizmo uses '''Royalty Groups''', which each cover a subset of Edition Formats. The default out-of-the-box definitions are:		To simplify data entry, PubGizmo uses '''Royalty Groups''', which each cover a subset of Edition Formats. The default out-of-the-box definitions are:
	{\| class="wikitable"		{\| class="wikitable"
Line 28:		Line 28:
	You can fully customize Royalty Group and Edition Format names and groupings to suit your press's needs. Your import sheet should reflect your definitions. '''Please let us know how you plan to set these up before we import your data.'''		You can fully customize Royalty Group and Edition Format names and groupings to suit your press's needs. Your import sheet should reflect your definitions. '''Please let us know how you plan to set these up before we import your data.'''

	Entries in ~~the '''Edition Format'''~~ column must exactly match the names as defined in your PubGizmo instance (or the defaults above, if you are not customizing them).		Entries in this column must exactly match the Edition Format names as defined in your PubGizmo instance, or the defaults above if you are not customizing them.

	=== Units Sold to Last Statement ===		=== Column D — List Price 1 ===
			Enter the primary list price for this edition as a number, without a currency symbol (e.g., ''26.95'').

			=== Column E — List Price 1 Currency ===
			Enter the three-letter ISO currency code for List Price 1 (e.g., ''CAD'', ''USD'').

			=== Column F — List Price 1 Region ===
			Enter the region for which List Price 1 applies. Use the region names defined on the [[Onboarding Import: Contracts\|Contracts]] sheet (e.g., ''Canada'', ''World'', ''CA Foreign'').

			=== Column G — List Price 2 ===
			Enter a second list price if this edition is sold at different prices in different markets (e.g., a separate US price). Leave blank if the edition has only one list price.

			=== Column H — List Price 2 Currency ===
			Enter the ISO currency code for List Price 2 (e.g., ''USD'').

			=== Column I — List Price 2 Region ===
			Enter the region for which List Price 2 applies.

			=== Column J — Publication Date ===
			Enter the publication date for this edition in '''YYYY-MM-DD''' format.

			=== Column K — Units Sold to Last Statement ===
	Royalty rates that include an escalation clause are based on cumulative units sold. If PubGizmo is not receiving historical sales data via import, it needs to know how many copies were previously sold in order to compute escalation correctly.		Royalty rates that include an escalation clause are based on cumulative units sold. If PubGizmo is not receiving historical sales data via import, it needs to know how many copies were previously sold in order to compute escalation correctly.

Line 40:		Line 61:
	If you are importing historical sales sheets, leave this column blank — PubGizmo will calculate the cumulative total from those records.		If you are importing historical sales sheets, leave this column blank — PubGizmo will calculate the cumulative total from those records.

	=== Net Sales to Last Statement ===		=== Column L — Net Sales to Last Statement ===
	The cumulative net revenue earned by this edition up to and including the last royalty statement completed before onboarding. This is the dollar-value counterpart to '''Units Sold to Last Statement''', and is used ~~alongside it~~ when a contract requires PubGizmo to carry forward a pre-existing royalty balance.		The cumulative net revenue earned by this edition up to and including the last royalty statement completed before onboarding. This is the dollar-value counterpart to '''Units Sold to Last Statement''' (Column K), and is used when a contract requires PubGizmo to carry forward a pre-existing royalty balance.

			Apply the same rule as Column K: fill in only if both conditions are met (escalation clause applies, and you are not importing historical sales data). Leave blank if you are importing historical sales sheets.

	~~Apply~~ the ~~same rule as above: fill~~ in ~~this column only if both conditions~~ are ~~met (escalation clause applies~~, and ~~you are not importing historical sales data)~~. ~~Leave blank if you are importing historical sales sheets~~.		=== Column M — Effective Date ===
			The date through which the values in Columns K and L are valid — in other words, the last day of the most recent royalty period completed before onboarding. PubGizmo uses this date to determine where inherited totals end and where its own tracking begins. Format: '''YYYY-MM-DD'''.

	~~=== Effective Date (for Units Sold~~ and ~~Net Sales columns) ===~~		Leave blank if Columns K and L are also blank.
	~~The date through which the values in the two preceding columns~~ are valid — in other words, the last day of the most recent royalty period completed before onboarding. PubGizmo uses this date to determine where inherited totals end and where its own tracking begins. Format: '''YYYY-MM-DD'''.

PubGizmoSysop: Claude conversion from PG site

2026-06-04T23:24:11Z

Claude conversion from PG site

New page

''Part of the [[Onboarding Import: Introduction|Onboarding Import]] series.''

The Editions sheet records each published format of a title — paperback, hardcover, ePub, audiobook, etc. Each row represents one edition.

== Column Notes ==

=== Title ===
'''MATCH WARNING:''' This must exactly match the title as entered on the [[Onboarding Import: Titles|Titles]] sheet. Use the title only — do not include the subtitle.

=== ISBN ===
Import will accept valid ISBN-13s with or without dashes.

=== Edition Format ===
To simplify data entry, PubGizmo uses '''Royalty Groups''', which each cover a subset of Edition Formats. The default out-of-the-box definitions are:
{| class="wikitable"
!Royalty Group
!Edition Formats Included
|-
|Print
|Paperback, Hardcover
|-
|Electronic
|ePub, PDF, MOBI
|-
|Audio
|Audiobook
|}
You can fully customize Royalty Group and Edition Format names and groupings to suit your press's needs. Your import sheet should reflect your definitions. '''Please let us know how you plan to set these up before we import your data.'''

Entries in the '''Edition Format''' column must exactly match the names as defined in your PubGizmo instance (or the defaults above, if you are not customizing them).

=== Units Sold to Last Statement ===
Royalty rates that include an escalation clause are based on cumulative units sold. If PubGizmo is not receiving historical sales data via import, it needs to know how many copies were previously sold in order to compute escalation correctly.

Fill in this column if '''both''' of the following are true:

# The applicable contract includes an escalation clause, '''and'''
# You are '''not''' going to import previous sales data.

If you are importing historical sales sheets, leave this column blank — PubGizmo will calculate the cumulative total from those records.

=== Net Sales to Last Statement ===
The cumulative net revenue earned by this edition up to and including the last royalty statement completed before onboarding. This is the dollar-value counterpart to '''Units Sold to Last Statement''', and is used alongside it when a contract requires PubGizmo to carry forward a pre-existing royalty balance.

Apply the same rule as above: fill in this column only if both conditions are met (escalation clause applies, and you are not importing historical sales data). Leave blank if you are importing historical sales sheets.

=== Effective Date (for Units Sold and Net Sales columns) ===
The date through which the values in the two preceding columns are valid — in other words, the last day of the most recent royalty period completed before onboarding. PubGizmo uses this date to determine where inherited totals end and where its own tracking begins. Format: '''YYYY-MM-DD'''.

Onboarding Import: Editions - Revision history

PubGizmoSysop: Claude re-edit

PubGizmoSysop: Claude conversion from PG site