This is the second part of a series. The first part can be found at https://booknetcanada.atlassian.net/wiki/spaces/MKTUserDocs/pages/1259765857/Product+metadata+for+born+accessible+content. The third part can be found at https://booknetcanada.atlassian.net/wiki/spaces/UserDocs/pages/1259929698/ONIX+code+lists+and+context+for+born+accessible+content.
...
That data is no help for identifying accessibility functionality, so what data is using the recommended version Code 15 in ONIX 3.0? The strongly recommend code list–based data? Nothing. No use.
...
A code and its associated value are usually serving a unique purpose and your database may provide a slot. Do you know which code from which list is being used in the ONIX record? Software developers and IT departments should be making that clear and available. If you don't know why you're doing something, follow the data by looking at the codes and their definitions. If something doesn't make sense, read the notes. If it still doesn't make sense: Ask us!
...
This originally appeared on the BNC Blog at https://www.booknetcanada.ca/blog/2019/7/5/improvement-is-possible-accessibility-and-using-product-form-feature. Subscribe the the blog RSS at https://www.booknetcanada.ca/blog?format=rss.