The BISAC Subject Codes provide a standardized way of categorizing book content, improving efficiency for publishers and their downstream partners in cataloging, buying, merchandising, and aiding discoverability. They are maintained by the diverse volunteers who make up BISG’s Subject Codes Committee. Chaired by Connie Harbison (Baker & Taylor), the committee responds to industry requests and cultural changes to produce a new edition of the BISAC codes each fall.
BISG recently conducted a survey and a series of interviews with industry stakeholders to determine whether current methods of identifying teen fiction and non-fiction are meeting industry needs. After evaluating the results, the Subject Codes Committee is proposing changes to the juvenile codes to allow for the classification of young adult content.
These changes are significant and will impact members across the supply chain who send or receive metadata, assign or maintain subject codes, and support or manage metadata and systems. The changes will affect people in editorial, marketing, sales, operations, IT, and business departments at publishers, wholesalers and aggregators, retailers, and libraries.
Meeting serves as an exploratory, fact finding mission. This initial meeting may not result in an agreed upon choice.
A number of potential scenarios, as discussed by the Subject Committee, will be presented. If you do not see the scenario you had in mind, this is the forum to present it. Those presented here are based solely on the understanding of the issue by the committee.
The goal of this meeting is to answer questions at hand and decide on the next steps.
We would like to reach a consensus by an agreed upon date regarding which are the most viable scenarios and then a final decision by a later agreed upon date.
What is the real issue that this change will resolve? Is there a problem within the industry that this change will address? We want to understand what the real issue is and the concrete benefit(s) of making a change.
Will making this change create a set of new problems that do not exist in the present structure?
What is to be gained by making a change to these sections? What is the ROI for making this change?
Does any gain outweigh the time and man hours that companies will possibly need to commit to a migration?
Do the suggested changes to this section diverge from the real intention of the subject codes (which is to describe content)? Why is this change needed when other fields in the ONIX record convey this information? Should the subject code convey everything?
Is the change being requested simply because there is an objection to the term “Juvenile”?
How will age range distinction between Children and Young Adult be set? Who will set it? Should be an industry standard.
Will publishers ensure that the BISAC they provide matches age range and audience provided in age range composite? What if they are out of sync? Who is then responsible for changing the data (and how is it to be determined which piece is incorrect)?
Will publishers ensure that the BISAC they provide matches age range and audience provided in age range composite? What if they are out of sync? Who is then responsible for changing the data (and how is it to be determined which piece is incorrect)?
What if a title spans the “cut-off” between Children and Young Adult (e.g., the Harry Potter series or Robert Sabuda titles)?
Any changes discussed may result in massive recoding and migration issues for both publishers and data aggregators. What if the change is met with resistance and failure to adopt?
If literals change meaning, parties using different versions will be providing data with a different meaning than intended.
The change may enable publishers to do more accurate sales analysis, but only if the industry’s migration is solid.
There is risk involved in that failure to migrate properly will corrupt data.
Migration must be done at once – you cannot send part of your list in one edition and part in another edition.
The migration from one edition to the next may be more important than the change depending on the scenario selected.
Though this change may increase sales for publishers, failure to implement the changes in a timely and accurate manner could actually result in lost sales.
Changes to existing sections.
The literal of JUV018000 would be changed by JUV039020 would be inactivated and all titles moving to new YA Code.
The literal of JUV018000 would be changed by JUV039020 would be inactivated and all titles moving to new YA Code.
This is a massive scope change as we are redefining the JUV and JNF codes.
This is a massive scope change as we are redefining the JUV and JNF codes.
This is a massive scope change as we are redefining the JUV and JNF codes.