BASICS FOR DEVELOPERS: WHAT TO RECORD IN A DATASET
...
Related Pages
Thema Subject Codes
Thema Basics: Subject Catgories, Qualifier Codes, National Qualifier Lists
Thema ONIX Sample
BISAC to Thema Translator
What needs to be recorded in a dataset – basic guidelines for developers
What does your inhouse system or ONIX-specific software need to support Thema? This is an outline and you must consult the full ONIX Specifications and Best Practices as well as the North American Best Practices for business rules around the support. I'm restricting this to North America practice, but please note: BIC is transitioning their subject system to Thema so confirm with your trading partners if you need to continue to support BIC.
A Main Subject
One of the Thema Subject category codes and one of the BISAC Subject Codes is designated as a Main Subject. All other subject and related codes list here appear as a "regular" subject. See Thema ONIX Sample for a fuller explanation.
ONIX Code List support for List 26 Subject Scheme Identifier
Within North American trade publishing these are supported by most Canadian publishers:
- Thema subject category code 93 and Thema qualifiers, codes 94 through 99
- BISAC subject heading code 10, BISAC regional code 11 and BISAC merchandising code 22
- Keywords code 20
ONIX 2.1 software needs to
- Support for both the “Main Subject” composite (ONIX Code List 27 -- with identical numbering in these sections as List 26 above) and the “Additional Subject” composite (ONIX Code List 26)
- Allow for at least two instances of Main Subject to provide support both Thema and BISAC (or three instances if you're maintaining BIC Subjects as well. Note: BIC is transitioning their subject system to Thema so confirm if you need to continue to support BIC).BISAC
- Allow for multiple instances of the Additional Subject composite. Thema often needs
- For complete coding Thema may need to support two codes values where one will do in BISAC.
- Supporting both systems may means the ONIX 2.1 <Subject> composite might need to support as many 10 <Subject> composites
- in addition to any other need like
- Keywords.
...
While BASICMainSubject element is provided for BISAC (and there one for BIC main subject as well) there is no unique ONIX 2.1 element to support a Thema Main Subject as there is now for BISAC or BIC and migrating probably should include . Your only option is to use the Main Subject composite. Your trading partners may prefer to load all their data from the Main Subject composite, so you should consider supporting BISAC within the Main Subject composite. The The safest course may would be to provide an identical BISAC main subject in both BASICMainSubject and as within a Main Subject compost MainSubjectSchemeIdentifier code "=10 " (BISAC Subject) in a Main Subject composite. You .
You should always check with main trading partners to ensure that they can support any changes you're making to the data.
...
ONIX 3.0 is a simpler implementation in that the Subject composite is the only one used, with a Main Subject . Main Subjects are identified by including an extra empty set <MainSubject/> tag within the composite. The only point to stress might be that
- being able to support multiple instances of
...
- the Subject composite is required
...
- and you need to support the <MainSubject/> empty set tag appropriately.
Main Subject
The three "trade book" subjects, Thema, BISAC and BIC, all require use of "Main Subjects". These are all used identically in that only one Subject – a single code for each system, Thema or BIC subject category or BISAC subject code can be designated "main." Within the record, all other codes within each of those systems are provided within the regular <Subject> composite. That would include, BISAC Subjects, its Regional or Merchandising codes, and any additional Thema Subject Category or any List 1 to 6 Qualifier Code, are provided using the appropriate Subject Scheme Identifier within the <Subject> composite. One Main subject per scheme – the rest are just Subjects. See Thema ONIX Sample
Transitioning to Thema
...
Transitioning to Thema
The BISAC to Thema Translator can provide a start on Thema codes for backlist titles, but it’s most important for publishers to familiarize themselves with the Thema Subject list and start applying values from this list to their bibliographic records. The next step is to supplement the Subject list values from the Qualifier lists as necessary.
It is important to take the time to learn how to use the lists in a way that will give retailers the information they need to maximize sales. This means using codes with focus—some might say sparingly, but always effectively.
We have suggested that publishers begin by running to recommend that run Thema and BISAC subject lists at the same time, and we strongly encourage you to start this transition as soon as possible. If . The US market will likely remain BISAC driven indefinitely and Canadian retailers still use that system. If you run into problems with the system or conflicts with retailers over your usage of the system, let us know at biblio@booknetcanada.ca.
Remember, at this stage there’s no right or wrong way to implement Thema—just Thema — just expected use and talking to trading partners is the best source.
...
Avoiding duplication with ONIX
BookNet Canada strongly encourages publishers and retailers to continue to use and support the current ONIX structures for Audience, and to use Audience Ranges to support Education values for North America.
...