How to effectively manage sales rights and territory statements in book metadata through ONIX. Part 2 of 2. Watch Part 1 here: https://booknetcanada.wistia.com/medias/3ozlj9a9z1
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
BNC Webinar: Sales Rights & Territory in ONIX - Tom Richardson
1. Sales Rights and Territory in ONIX
Part 2 EDItEUR’s Perspective
Based on two posts made by Graham Bell to the
ONIX_IMPLEMENT email list early September 2016
September 14, 2016
2. Typical problems EDItEUR is aware of:
• Publisher systems that track product sales rights aren’t
integrated with systems producing ONIX
• ONIX 2.1 feeds have been inconsistently supported in
describing sales rights, markets, suppliers
3. Describing Territory in ONIX 3.0
Territory statements build clearly defined areas by positive
lists of countries or regions. For example:
<Territory>
<CountriesIncluded>CA MX US</CountriesIncluded>
</Territory>
defines a geographical area covering the three North
American countries added together.
4. You can also include parts of countries
<Territory>
<CountriesIncluded>US MX</CountriesIncluded>
<RegionsIncluded>CA-NB CA-NL CA-NS CA-PE</RegionsIncluded>
</Territory>
• Defines all of Mexico and USA, plus the four Atlantic
provinces of Canada.
• No double booking. You can’t “include” a Country
and “include” its sub-regions in the same territory
statement.
Including US and including US-AK (Alaska) makes no sense.
5. You can define a geographical area
through subtraction
<Territory>
<CountriesIncluded>CA US MX</CountriesIncluded>
<RegionsExcluded>CA-QC</RegionsExcluded>
</Territory>
• Defines Canada, USA and Mexico minus the
Canadian sub-region (province) of Québec.
• Subtract a subset to define a clear positive area.
You can’t “exclude” something that hasn’t been
“included” in the composite.
Excluding region code CN-53 (Yunnan, a province of China) makes no
sense in this composite
6. You can start with WORLD
<Territory>
<RegionsIncluded>WORLD</RegionsIncluded>
<CountriesExcluded>CA MX US</CountriesExcluded>
</Territory>
Everywhere outside of North America
<Territory>
<RegionsIncluded>WORLD</RegionsIncluded>
<CountriesExcluded>FR</CountriesExcluded>
<RegionsExcluded>CA-QC CN-53</CountriesExcluded>
</Territory>
Everywhere except the country of France
and the provinces of Québec (Canada)
and Yunnan (China).
7. Within the <Territory> composite
There are four possible country and region tags
<CountriesIncluded>
<RegionsIncluded>
<CountriesExcluded>
<RegionsExcluded>
Order of the XML tags matters
• Inclusions always come before exclusions
(It’s always a clear, positive statement of an area)
• Countries come before regions
(Regions Included=WORLD would always start a list
because you can’t add countries to the WORLD)
8. Only certain combinations make sense
within a single Territory Composite
You always start with something…
Either of the “included” tags can exist on their own
• Countries Included (CI) on its own
• Regions Included (RI) on its own
Starting from Regions Included=WORLD (cannot be combined with CI)
• RI with Countries Excluded
• RI with Regions Excluded
• RI with CX and RX (RX cannot be a sub-region of a named CX)
Starting from Countries Included
• CI with Regions Excluded (the RX must be a sub-region of a named CI)
• CI with Regions Included (RI cannot be WORLD or a sub-region of a named CI)
• CI with RI and RX (The same rules apply to RI and RX as above)
9. Complimentary Territory Statements
<Territory>
<CountriesIncluded>BE BF BI BJ CD CF CG CI CM DJ DZ FR GN HT
KM LU MC MG ML NE TD</CountriesIncluded>
<RegionsIncluded>CA-NB CA-QC</RegionsIncluded>
</Territory>
Francophone markets
<Territory>
<RegionsIncluded>WORLD</RegionsIncluded>
<CountriesExcluded>BE BF BI BJ CD CF CG CI CM DJ DZ FR GN HT
KM LU MC MG ML NE TD</CountriesExcluded>
<RegionsExcluded>CA-NB CA-QC</RegionsExcluded>
</Territory>
Everywhere but Francophone markets
10. What are Sales Rights in ONIX?
It’s not the ‘Publishing Rights,’ defined loosely as the
rights publishers obtain from an author against their work.
Sales Rights in ONIX
• are the rights publishers pass to their distributors,
wholesalers and retailers
• are where the publisher chooses to make the product
available – that portion of their publishing rights that a
publisher chooses to exercise
• apply to the specific product defined in the record
Sales Rights are a subset (sometimes the same) as the
Publishing Rights.
11. Describing Sales Rights in ONIX 3.0
<SalesRights>
<SalesRightsType>03</SalesRightsType>
<Territory>
<CountriesIncluded>CA MX US</CountriesIncluded>
</Territory>
</SalesRights>
This rights statement means
the product is not for sale (Sales Rights Type 03)
in North America (CA, MX, US)
12. A Sales Rights composite means what it says
<SalesRights>
<SalesRightsType>03</SalesRightsType>
<Territory>
<CountriesIncluded>CA MX US</CountriesIncluded>
</Territory>
</SalesRights>
Not for Sale codes imply nothing about where
the product IS for sale.
For Sale codes imply nothing about where the
product IS NOT for sale.
You tell them more in a second and likely complimentary
statement.
14. but it’s typical to start with where it is
For Sale
and complete the statement with where it is
Not for Sale.
The order of Sales Rights composites
does not matter
15. 01 Product is for sale, based on the publisher holding exclusive publishing rights
02 Product is for sale, based on the publisher holding only non-exclusive
publishing rights
03 Product is not for sale (for any reason)
04 Product is not for sale (the publisher holds exclusive publishing rights,
but has chosen not to exercise them)
05 Product is not for sale (the publisher holds non-exclusive publishing rights,
but has chosen not to exercise them)
06 Product is not for sale (because the publisher does not hold the
relevant publishing rights at all)
There are six options for <SalesRightsType>
17. Is the WORLD region included in a sales rights composite?
if no, <ROWSalesRightsType> is always required, even if
you believe you have exhaustively listed all the ISO country
codes separately. It will act as a fallback if you have
inadvertently omitted a country, or if a new country code is
added to the ISO list;
if yes, see Step two;
Using <ROWSalesRightsType>
Step one
18. Are there any <CountriesExcluded> or <RegionsExcluded>
elements?
if no, <ROWSalesRightsType> must be omitted;
if yes, see Step three;
How to use <ROWSalesRightsType>
Step two
Within a <SalesRights> statement that includes WORLD
19. Are all those excluded countries and regions included in other
<SalesRights> composites?
if no, <ROWSalesRightsType> is required. It may be used to
specify the rights that apply in the remaining countries or
regions that you left out;
if yes, <ROWSalesRightsType> must be omitted.
How to use <ROWSalesRightsType>
Step three
Within a <SalesRights> statement that includes WORLD
21. References
• EDItEUR: Implementation and Best Practice Guide
http://www.editeur.org/files/ONIX%203/ONIX_for_Books_Release3-
0_html_Best_Practice+codes_Issue_34_v1-3-1.zip
• BISG/BNC: Best Practices for Product Metadata
https://bisg.site-ym.com/store/ViewProduct.aspx?id=6972807
• BNC Blog post: ONIX 2.1 to 3.0: Sales Rights
http://www.booknetcanada.ca/blog/2015/8/17/onix-21-to-30-sales-rights