who updates publisher metadata and why? downstream vendors on what happens to metadata in the supply...

72
Who Updates Publisher Metadata and Why? Downstream Vendors on What Happens to Publisher Metadata in the Supply Chain

Upload: renee-register

Post on 22-Jan-2015

75 views

Category:

Technology


1 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Who  Updates  Publisher  Metadata  and  Why?  

Downstream  Vendors  on  What  Happens  to  Publisher  Metadata  in  the  Supply  Chain  

Page 2: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Moderator  and  Panelists  Moderator  •  Renée  Register,  DataCurate  LLC  

Panelists  •  Sam  Dempsey,  VP  of  Data  Management,  Baker  &  Taylor  •  Patricia  Payton,  Senior  Manager,  Publisher  RelaHons  and  

Content  Development,  Bowker  

•  Richard  Stark,  Director,  Product  Data,  Barnes  &  Noble  •  George  TaLersfield,  VP  of  Merchandising,  Ingram  Book  Group  

Page 3: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013
Page 4: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Downstream  Metadata  Survey  

1.  Which  metadata  elements  are  oQen  changed  and  why  are  they  changed?  

2.  Which  metadata  elements  are  oQen  added  and  why?  

3.  How  are  needed  changes  or  addiHons  idenHfied?  4.  What  processes  are  involved  in  adding  or  changing  

metadata?  5.  Where  does  vendor  metadata  go  aQer  changes  and  

enhancements  are  made?  

6.  What  are  the  benefits  of  changing  or  enhancing  publisher  metadata?  

Page 5: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Most  Common  Changes  

•  Title/SubHtle  •  Contributor  •  Series  

•  Subject  •  PublicaHon  Data  

•  Status/Availability  

Page 6: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Why  Change  Title/SubHtle?  •  Non-­‐Htle  informaHon  included  in  the  Htle  

field  is  moved  to  correct  fields  to  improve  display  and  search  

–  Common  examples:  •  EdiHon  •  Binding  

•  Series  •  Translated  Htle  

•  CapitalizaHon  is  standardized  

Page 7: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Why  Change  Contributor?  

•  Make  names  consistent  across  Htles  by  using  a  name  authority  file    

–  Standardize  variaHons  in  names    –  Ensure  that  Htles  are  associated  with  the  correct  

contributor  name  –  Some  contributor  work  is  automated  but  some  

must  be  reviewed  manually  

Page 8: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Why  Change  Contributor?  

•  Move  InformaHon  included  in  the  contributor  field  to  correct  fields  to  correct  fields  to  opHmize  search,  sorHng,  and  display  

–  Examples:  •  Degrees  (PhD,  etc.)  •  Titles  (Dr.,  Pope,  etc.)  •  Birth/death  dates.  

Page 9: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Why  Change  Series?  •  Move  series  names  from  incorrect  fields  to  the  

series  field    –  Allows  search  by  series  

•  Regularly  review  books  in  series    –  Ensure  they  are  connected  to  the  correct  series  

–  Ensure  consistent  informaHon  across  Htles  

Page 10: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Why  Change  Subject?  •  Replace  general  subjects  with  more  specific  

subjects  

•  Replace  sent  subjects  with  clearly  more  accurate  subjects  

–  Examples:  •  Title  is  coded  with  both  JNF  (Juvenile  non-­‐ficHon)  and  

JUV  (Juvenile  ficHon)  BISAC  codes  

•  Title  is  coded  with  both  HIS  (History)  and  FIC  (FicHon)  BISAC  codes  

Page 11: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Why  Change  PublicaHon  Date?  •  Vendors  work  closely  with  publishers  on  

publicaHon  date  changes    

•  May  update  a  publicaHon  date  to  reflect  the  actual  date  that  the  book  is  available  to  consumers  

Page 12: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Why  Change  Status/Availability?  

•  Vendors  regularly  compare  prices  received  in  metadata  files  to  actual  invoiced  prices  

Why  Change  Price?  

•  Updated  based  on  purchase  order  acknowledgements  and  other  supply  chain  messages  •  For  example,  physical  receipt  of  a  product  

may  cause  a  change  in  status/availability  

Page 13: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Common  reasons  for  changes  

•  Standard  quality  checks  idenHfy  changes  needed  –  Vendors  rouHnely  confirm  metadata  received  against  

the  published  book    

–  Publisher  metadata  moved  to  correct  ONIX  field  –  Periodic  data  reviews  are  also  common  and  aLempt  

to  ensure:  •  Consistency  across  different  formats  of  the  same  Htle  •  Consistency  within  a  series  

•  Consistency  and  standardizaHon  of  contributor  names  

Page 14: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Metadata  most  oQen  added  

•  EdiHon    

•  Series  •  Contributor  Biography  •  Awards  

•  Media  menHons  •  Bestseller  menHons  •  Title  linking  across  

formats  •  Age  and  grade  level  

•  Metadata  licensed  or  created  in-­‐house  

•  Reviews  

•  Tables  of  contents  

•  DescripHons  

•  Covers  

•  Proprietary  subjects  and  descriptors  

•  Dewey  Decimal  ClassificaHon  or  other  library  metadata  

Page 15: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Common  reasons  for  adding  metadata  

•  Known  informaHon  about  the  book  is  not  supplied  by  publisher  

•  Elements  are  added  to  enhance  user  experience  and  increase  discovery  and  sales  

•  Proprietary  data  for  the  vendor  is  added  •  AddiHonal  metadata  is  needed  for  the  library  

market  •  Formaing  is  added  to  allow  Htles  to  link  

automaHcally  

Page 16: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Ingram  Book  in  Hand  changes  made  (1600  Htles  tested)  

Changes made # Changes % Features Added 1389 86.8%

Illustrations Added 960 60.0% Page Count 917 57.3%

Image Scanned 623 38.9% Country of Manufacture Added 474 29.6%

Contributor Changed 374 23.4% Contributor Added 329 20.6%

Series Added 261 16.3% Title Changed 237 14.8%

Contributor Deleted 237 14.8% Subtitle 205 12.8%

Series Changed 166 10.4% Edition 161 10.1%

Page 17: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Examples  

Title  and  SubHtle  

Sam  Dempsey  

Vice  President  of  Data  Management  

Page 18: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

<Htle>  

           <b202>01</b202>  

           <b203>The  First  Phone  Call  From  Heaven  CD</b203>  

           <b029>The  First  Phone  Call  From  Heaven  CD</b029>  

 </Htle>  

ONIX  -­‐  Format  in  Title  field;  use  <b012>  -­‐  Title  repeated,  with  Format,  in  SubHtle  field  

Title  and  Sub8tle  

Page 19: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

<Htle>        <b202>01</b202>        <b203><![CDATA[This  Heart  Within  Me  Burns  –  From                  Bedlam  to  Benidorm  (Revised  &  Updated)]]></b203>        <b030><![CDATA[This]]></b030>        <b031><![CDATA[Heart  Within  Me  Burns  -­‐  From  Bedlam                    to  Benidorm  (Revised  &  Updated)]]></b031>  </Htle>  

ONIX  -­‐  SubHtle  included  in  Title  field,  no  SubHtle  field  included;  

use  <b029>  -­‐  EdiHon  values  included  in  Title  field;  use  <b056>  <b058>  

Page 20: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

<Htle>  

       <b202>01</b202>  

       <b203>IntroducHon  to  Documentary,    

                   Second  Edi8on</b203>  

</Htle>  

ONIX  -­‐  EdiHon  Number  in  Title  field;  use  <b057>  

Page 21: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

<Title>How  ODawa  Spends  Series,  Volume  33</Title>  

<Sub_Title>How  ODawa  Spends,  2012-­‐2013  :  The  Harper  

Majority,  Budget  Cuts,  and  the  New  OpposiHon</Sub_Title>  

Proprietary  XML  format,  not  ONIX  -­‐  Title  includes  Series  Name,  Volume  Number;  use  

<b018>  <b019>  -­‐  SubHtle  repeats  Series  Name,  includes  disHncHve  Htle  

elements  

Page 22: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Excel  -­‐  Series  and  Series  Number  in  Title  field  

ISBN   Title   Series  Title  

9781622861132  

Losing  Hope:  Book  One  of  the  Sienna  St.  James  Series   Sienna  St.  James  

Page 23: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Excel  -­‐  Series  Number  in  Title  field,  not  in  Series  Number  

ISBN   Title   Series  Title  

9780761368175  

#06  Sherlock  Holmes  and  the  Adventure  of  the  Sussex  Vampire  

On  the  Case  with  Holmes  and  Watson  

Page 24: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

<Htle>  

       <b202>01</b202>  

       <b203>Brief  Guide  -­‐  Global  Warming,  A</b203>  

</Htle>  

ONIX  -­‐  Lead  arHcle  appended;  use  <b030>  <b031>    

Page 25: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

<Htle>  

     <b202>01</b202>  

     <b203>Mas  Alla  Del  Escandalo</b203>  

     <b029>(Beyond  the  Scandal)</b029>  

</Htle>  

ONIX  -­‐  TranslaHon  within  SubHtle  tag;  use  <b203>  

with  <b202>06  

Page 26: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Metadata  inconsistent  with  Title  page  

Metadata  Title:    Dive-­‐Bomber  &  Ground-­‐ALack  Units  of  the  LuQwaffe    

Page 27: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Metadata  inconsistent  with  Title  page  

Metadata  Title:  An  Illustrated  History  of  India  Enterprise  

Page 28: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Best  PracHces  for  Title  

-­‐  Properly  field  elements:    

-­‐  SubHtle,  Series,  Series  #,  EdiHon,  EdiHon  #,  Volume,  Formats,    lead  arHcles,  etc.  

-­‐  Match  product’s  Title  page  -­‐  Make  consistent  across  formats,  ediHons,  series  -­‐  Watch  for  misspellings,  capitalizaHon,  abbreviaHons,  

truncaHons,  special  characters,  etc.  

-­‐  Send  “consumer/patron”  ready  

Page 29: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Examples  

Contributors  

Review  Quotes  

Richard  Stark,  Director  Product  Data    

Page 30: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Good  pracHce:    Contributor  names  

•  As  disHnct  fields,  the  least  you  can  do  is:  – First  name  –  all  names  preceding  the  indexing  name  of  a  person  (include  a  middle  name  here)  

– Last  name  –  the  key  or  indexing  name  of  a  person  

OR  

•  Corporate  Contributor  –  if  it’s  not  a  person,  don’t  use  the  fields  for  people,  use  this  instead.  

Page 31: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Good  pracHce:    Contributor  names    Titles  before  names  or  prefixes  to  en8re  names  

  Pope  John  Paul  II    Names  before  key  name  (includes  given  names  as  appropriate)  

  Robert  Louis  Stevenson    Prefixes  to  key  name(s)  

  Simone  de  Beauvoir    

  Key  name(s)  (usually  the  family  name)    Gabriel  García  Márquez    

  Names  a^er  key  name(s)  (including  given  names  where  appropriate)    Mao  Zedong    

  Suffix  a^er  key  name(s)    Reverend  Adam  Clayton  Powell,  Jr.    

  Qualifica8ons  and  honors  a^er  name(s)    Stephen  LaBerge,  Ph.D.    

  Titles  a^er  name(s)    Sarah  Ferguson,  Duchess  of  York    

Page 32: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Good  pracHce:    MulHple  contributors  

•  Support  for  three  to  five  contributors  is  a  minimum  in  trade  retail  records,  but  accurately  lisHng  everyone  associated  with  the  book  is  best.  

•  Support  sequence  numbering:  – Author  order  is  important  and  metadata  records  should  give  a  clear  order  for  display.  

Page 33: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Good  pracHce:    Contributor  role(s)  

•  You  need  to  specify  who  did  what  – “author”  is  code  “A01”  – “editor”  is  “B01”  – “illustrator”  is  “A12”  

•  If  one  contributor  fulfilled  two  roles,  repeat  the  contributor  and  assign  each  entry  its  own  role  code.  

Page 34: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Contributor  Name  Mapping  all  variants  to  an  authority  controlled  form  of  the  name  ensures  that  all  Htles  by  Leo  Tolstoy  will  be  grouped  together  rather  than  scaLered  across  

mulHple  versions  of  his  name.    

Page 35: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Contributor  Authority  Control    

Tolstoi  ,  Count  Lev  

Tolstoi  ,  Graf  Leo  N.  

Tolstoi  ,  León  Tolstoi  ,  Lev  Nicolaevici  

Tolstoi  ,  Lew  Nikolajewitsch  

Tolstoi  ,  Liev  Nikolaievich  

Tolstoi  ,  Count  Lvof  N.          

Tolstoj  ,  Lev  Nikolaevitch  

Tolstoy,  Count  Lev  N.  

Tolstoy,  Graf  Leo  

Tolstoy,  Leo  Nikolayvich  

Tolstoy,  Leo  Nikolaevich  

Tolstoy,  Graf  Lev                      

Tolstoy,  Lyof  N.    

Leo  Tolstoy  ISNI:    0000  0004  0006  2877    

Page 36: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

•  Each  Public  iden8ty  of  a  given  Party  gets  its  own  ISNI:  •  Lewis  Carroll  &  Charles  Lutwidge  Dodgson  get  separate  

ISNIs  

•  Separate  iden88es  that  are  the  same  person  can  be  linked  

•  Authors  of  the  same  name  get  dis8nct  ISNIs:  

•  Thomas  Wolfe  

•  Tom  Wolfe,  author  of  The  Bonfire  of  the  Vani/es  

•  Tom  Wolfe,  author  of  numerous  books  on  woodcarving  

ISNI:    Interna8onal  Standard  Name  Iden8fier  

Page 37: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

•  Günter  Graß,  Guenter  Grass  and  Guenter  Graß  are  character  set  variances  of  the  same  Public  Iden8ty  

•  Ciaikovsky,  Pjotr  Iljc  and  Пётр  Ильич  Чайковский  are  translitera8on  variances  of  the  same  public  iden8ty  and  also  receive  the  same  ISNI.  

•  Pyotr  Tchaikovsky  and  Peter  Tchaikovsky  are  linguis8c  variances  of  the  same  public  iden8ty  and  again  receive  the  same  ISNI  

Character-­‐Set  &  Spelling  Differences  Don’t  Change  the  ISNI  

Page 38: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013
Page 39: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Good  pracHce:    Review  quotes  <produc8den8fier>  <b221>03</b221>  

<b244>9780520262508</b244>  

</produc8den8fier>  

<othertext>  

<d102>08</d102>  <d104>A  gorgeously  produced  collec8on  of  maps  and  essays.</d104>  

<d107>Nikil  Saval</d107>  

<d108>The  Los  Angeles  Review  of  Books</d108>  

<d109>20101103</d109>  

</othertext>  

<othertext>  <d102>08</d102>  

<d104>Inven8ve  and  affec8onate.</d104>  

<d107>Lise  Funderburg</d107>  

<d108>The  New  York  Times  Book  Review</d108>  

<d109>20101205</d109>  

</othertext>  <othertext>  

<d102>08</d102>  

<d104>A  many-­‐layered  treat  for  any  San  Franciscan  who  thinks  she  knows  her  city.</d104>  

<d107>Danielle  Sommer</d107>  

<d108>KQED</d108>  

<d109>20101018</d109>  

</othertext>  

Infinite  City:    A  San  Francisco  Atlas  

by  Rebecca  Solnit  ISBN:  9780520262508  

<d102>  tag  idenHfies  the  type  of  text  provided.  Value  08  indicates  that  the  text  is  a  review  quote.  

<d107>  tag  idenHfies  the  author  of  the  provided  text.  This  tag  is  only  used  when  there  is  a  named  author/reviewer.  

<d108>  tag  idenHfies  the  corporate  source  of  the  provided  text.    The  publicaHon    where  a  review  appeared  would  be  placed  here.  

<d109>  tag  idenHfies  the  publicaHon  date  of  the  provided  text  (review).  

<d104>  tag  idenHfies  the  actual  text  of  the  review.  

Page 40: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Bad  pracHce:    Review  quotes  <othertext>  <d102>18</d102>  

<d104><![CDATA[<DIV><P>What  makes  a  place?  <I>Infinite  City</I>,  Rebecca  Solnit’s  brilliant  reinven8on  of  the  tradi8onal  atlas,  searches  out  the  answer  by  examining  the  many  layers  of  meaning  in  one  place,  the  San  Francisco  Bay  Area.  Aided  by  ar8sts,  writers,  cartographers,  and  twenty-­‐two  gorgeous  color  maps,  each  of  which  illuminates  the  city  and  its  surroundings  as  experienced  by  different  inhabitants,  Solnit  takes  us  on  a  tour  that  will  forever  change  the  way  we  think  about  place.  She  explores  the  area  thema8cally—connec8ng,  for  example,  Eadweard  Muybridge’s  founda8on  of  mo8on-­‐picture  technology  with  Alfred  Hitchcock’s  filming  of  Ver8go.  Across  an  urban  grid  of  just  seven  by  seven  miles,  she  finds  seemingly  unlimited  landmarks  and  treasures—buDerfly  habitats,  queer  sites,  murders,  World  War  II  shipyards,  blues  clubs,  Zen  Buddhist  centers.  She  roams  the  poli8cal  terrain,  both  progressive  and  conserva8ve,  and  details  the  cultural  geographies  of  the  Mission  District,  the  culture  wars  of  the  Fillmore,  the  South  of  Market  world  being  devoured  by  redevelopment,  and  much,  much  more.  Breathtakingly  original,  this  atlas  of  the  imagina8on  invites  us  to  search  out  the  layers  of  San  Francisco  that  carry  meaning  for  us—or  to  discover  our  own  infinite  city,  be  it  Cleveland,  Toulouse,  or  Shanghai.  </P><P>  “A  gorgeously  produced  collec8on  of  maps  and  essays.”  —Nikil  Saval,  <I>Los  Angeles  Review  of  Books</I></P><P>  “Inven8ve  and  affec8onate.”  —Lise  Funderburg,  <I>New  York  Times  Book  Review</I></P><P>  “A  many-­‐layered  treat  for  any  San  Franciscan  who  thinks  she  knows  her  city.”  —Danielle  Sommer,  <I>KQED</I></P></DIV>]]></d104>  

</othertext>  

Infinite  City:    A  San  Francisco  Atlas  

by  Rebecca  Solnit  ISBN:  9780520262508  

Using  CDATA  tags  is  bad  pracHce.    Data  providers  should  use  XHTML  to  provide  informaHon  on  formaing  the  text.  

Using  <DIV>    tags  is  bad  is  bad  pracHce.    SeparaHng  a  secHon  of  text  can  be  handled  using  a  <P>  tag.    

ConcatenaHng  review  quotes  at  the  end  of  the  jacket  copy  or  main  descripHon  is  BAD  pracHce.  

Page 41: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Examples  

EdiHon  

Series  

Patricia  Payton,  Senior  Manager  

Publisher  RelaHons  and  Content  Development  

Page 42: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013
Page 43: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

First  EdiHon  

<b058><![CDATA[First  EdiHon]]>  </b058>  

Page 44: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Numbered  EdiHon  

<Htle>  <b202>01</b202>  <b203>Bartending  101</b203>  <b029>The  Basics  of  Mixology,  4th  EdiHon</b029>  </Htle>  <Htle>  <b202>05</b202>  <b276>40</b276>  <b203>Bartending  101  (4E)</b203>  </Htle>  

<b057>4</b057>  <b058><![CDATA[Fourth  EdiHon]]></b058>  

Page 45: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

BISG  Best  PracHces  

Page 46: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Foreign  Language  EdiHon  

<Htle>  <b202>01</b202>  <b203><![CDATA[Quiero  a  mi  papa  Porque  (I  Love  My  Daddy  Because  English  /  SpanishediHon)]]></b203>  </Htle>  <language>  <b253>01</b253>  <b252>spa</b252>  

Page 47: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Special  EdiHon  

<Htle>              <b202>01</b202>              <b203>Harold  and  the  Purple  Crayon  50th  Anniversary  EdiHon</b203>          </Htle>  

Page 48: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

BISG  Best  PracHces  

Page 49: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Series  

Page 50: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

StandardizaHon  of  Series  Name  <series>  <b018>The  Haruhi  Suzumiya  Series</b018>  </series>  <Htle  textcase="02"  refname="Title"  >  <b202>01</b202>  <b203>The  DissociaHon  of  Haruhi  Suzumiya</b203>  </Htle>  

<series>  

<b018>Immortal    Beloved</b018>  

<b019>3</b019>  </series>  

<Htle  textcase="02"  refname="Title"  >  

<b202>01</b202>  

<b203>Eternally  Yours</b203>  

</Htle>  

Page 51: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Bowker  Best  PracHce  

Page 52: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Series  SubHtle  <series>              <b018>Let's-­‐Read-­‐and-­‐Find-­‐Out  Science  1</b018>  

       </series>  

       <Htle>  

           <b202>01</b202>  

           <b203>How  a  Seed  Grows</b203>  

       </Htle>  

Page 53: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

First  Book  in  Series  <othertext>  <d102>08</d102>  <d103>02</d103>  <d104><![CDATA[  "A  fantasHc  new  dystopian  series...LiLlefield's  compelling  wriHng  will  keep  

readers  turning  pages  late  into  the  night  to  find  out  what  happens  next.  Outstanding!"  Top  Pick,  4  1/2  stars<P>  -­‐RT  Book  Reviews]]>  

</d104>  </othertext>  

<othertext>  <d102>08</d102>  <d103>02</d103>  <d104><![CDATA[  <P>"A  series  starter  that  will  appeal  to  fans  of  Jeff  Kinney  and  Dav  Pilkey  .  .  .  A  treat  for  all  .  .  .  And  guess  what?  It  makes  for  good  tree  house  reading."  -­‐-­‐  <I>Booklist</I><P>"Fans  of  Jeff  Kinney&#8217;s  &#8220;Diary  of  a  Wimpy  Kid&#8221;(Abrams)  and  Lincoln  Peirce&#8217;s  &#8220;Big  Nate&#8221;  series  (HarperCollins)  will  be  drawn  to  this  book,  while  parents  will  enjoy  the  absence  of  snarky  humor."  -­‐-­‐  <I>School  Library  Journal</I>]]>  </d104>  </othertext>  

Page 54: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

InternaHonal  Titles  in  USA  Feeds  

<Htle>  

<b202>01</b202>  

<b203>The  Science  of  Discworld  IV</b203>  <b029>Judgement  Day:  It's  Wizards  Vs  Priets  in  a  BaLle  

for  the  Future  of  Roundworld</b029>  

</Htle>  

Page 55: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Examples  

Subject    

George  TaLersfield  

 Vice  President  of  Merchandising  

Page 56: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

•  As  a  general  rule  a  Htle  cannot  have  both  the  parent  and  child  of  a  specific  subject  tree  

•  We  aim  for  consistency  across  formats  •  We  try  to  assign  categories  based  on  content,  not  on  the  

merchandising  plans  of  the  publisher  

•  Juvenile  and  YA  books  both  get  JUV  or  JNF  subject  headings,  but  not  adult  headings  

•  A  book  cannot  be  both  ficHon  and  nonficHon  •  The  three  “  media  He-­‐in”  subjects  (FIC,  JNF,  and  JUV)  should    

never  be  in  first  posiHon  

•  We  try  to  avoid  the  General  subjects  

Main  reasons  for  changing  subjects  

Page 57: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

A  deep,  thought-­‐provoking  novel  of  love,  loss,  civil  unrest,  and  basketball.  It  is  1989,  and  Jim  KeaHng  has  hit  absolute  rock  boLom.  He’s  lost  his  wife  to  cancer,  his  house  to  bankruptcy,  and  his  job  as  a  college  basketball  coach  to  what  many  outsiders  believed  to  be  a  racially  insensiHve  career-­‐ending  decision.  He  has  also  just  about  lost  his  mind,  having  slipped  into  a  bout  of  serious  depression.  ALempHng  to  pick  up  the  pieces  and  start  life  over,  Jim  returns  home  to  Worcester  and  rents  a  small  apartment.  

 …  Soon,  Jim  finds  himself  in  Burundi,  Africa,  where  he  is  to  create  a  basketball  league  that  will  bring  two  warring  tribes—the  Hutus  and  the  Tutsis—together  peacefully.  

Example  1  An  African  Rebound:  A  Novel  by  Dan  Doyle  

FicHon  coded  as  non-­‐ficHon  

Page 58: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Hardcover   Ingram  BISAC  change  

Ingram    Regional  Theme  added  

HIS001010    History-­‐Africa-­‐Central    

FIC038000  FicHon  –  Sports    

Africa  

SPO004000    Sports    -­‐  Basketball    

Example  1  FicHon  coded  as  non-­‐ficHon  

Page 59: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

A  local  guide  leads  adventurers  on  safaris  into  three  surprisingly  varied  worlds:  the  bushveld,  a  river  and  a  desert.  Each  environment  brings  its  unique  flavor  to  the  adventure;  mulHple  images  (both  photos  and  illustraHons)  and  interesHng  text  introduce  the  region's  fascinaHng  wildlife  with  its  intriguing  habits  and  lifestyles.  Readers  are  encouraged  to  play  along  by  means  of  engaging  acHviHes,  games  and  quizzes,  with  answers  at  the  end  of  each  secHon.  Nature's  edible  treats  and  useful  props  are  ...    

Example  2  Ge<ng  Bushwise  on  Safari:  A  Young  Explorer’s  Guide  

by  Nadine  Clark  Juvenile  coded  as  adult  

Page 60: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Publisher  BISAC   Ingram  BISAC  change  

TRV002000  -­‐    Travel-­‐Africa-­‐General    

JNF051100  –  Juvenile  NonficHon  –    Science  and  nature  –  Environment    

NAT027000  –  Nature  -­‐Reference    

JNF051150  –  Juvenile  NonficHon  –  Zoology  

NAT037000  –  Nature  -­‐  Wildlife    

JNF003000  –  Juvenile  NonficHon  –  Animals  –  General    

Example  2  Juvenile    as  Adult  

Page 61: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

DAVID  BUSCH'S  CANON  POWERSHOT  G15  GUIDE  TO  DIGITAL  PHOTOGRAPHY  shows  you  how,  when,  and  why  to  use  all  the  features,  controls,  and  funcHons  of  the  G15  to  take  great  photographs  and  movies.  Introductory  chapters  will  help  you  get  comfortable  with  the  basics  of  your  camera  before  you  dive  right  into  exploring  creaHve  ways  to  apply  file  formats,  resoluHon,  and  exposure.  BeauHful,  full-­‐color  images  illustrate  where  the  essenHal  buLons  and  dials  are,  so  you'll  quickly  learn  how  to  use  the  Canon  PowerShot  G15,  and  use  it  like  a  pro!  

Example  3  David  Busch’s  Canon  Powershot  G15  

Incorrect  BISAC  subject  

Page 62: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Publisher  BISAC   Ingram  BISAC  change  

 BUS001000    AccounHng  –  General    

 PHO024000  Photography  –  Techniques  –  Digital  

PHO007000    Photography  –  Techniques  –  Equipment  

 3    Incorrect  BISAC  subject  

Page 63: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

 Jerry  Harris  was  a  self-­‐made  California  millionaire  who,  at  age  forty-­‐four,  had  it  all:  booming  businesses,  yachts,  a  mansion,  a  beauHful  wife,  and  a  voice  to  rival  Elvis.  No  one  who  knew  this  well-­‐liked,  generous  man  could  make  sense  of  his  sudden  disappearance  one  autumn  night.  …  

Example  4  In  the  Name  of  Love  by  Ann  Rule  

Incorrect  BISAC  subject  

Page 64: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Publisher  BISAC    Mass  market  paperback  

Publisher  BISAC  Trade  paperback  

Publisher  BISAC  Audio  

Ingram  BISAC  Change  

TRU002000  True  Crime  –  Murder  –  General    

TRU002000  True  Crime  –  Murder  –  General    

TRU003000  True  Crime  –  Organized  Crime    

TRU002000  True  Crime  –  Murder  –  General    

LIT000000  Literary  CriHcism  –  General    

LIT000000  Literary  CriHcism  –  General    

Example  4  Incorrect  BISAC    (Literary  CriHcism)  

Audio  version  different  

Page 65: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Detailed  travel  map,  scale  1:250,000,  with  an  inset  of  central  Mbabane,  a  distance  chart  and  text  informaHon  for  visitors.  

Example  5  InternaLonal  Travel  Maps  Swaziland  Adult  with  juvenile  BISAC  subject  

Page 66: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Publisher  BISAC     Ingram  BISAC  Change  

JUV000000    Juvenile  ficHon  –  General  

TRV002000    Travel  –  Africa  –  General  

TRV027000    Travel  –Maps  &  Road  Atlases    

Example  5  Adult  with  juvenile  ficHon  BISAC  subject  

Page 67: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

IdenHfying  Needed  Changes  

•  Strongly  Hed  to  processes  developed  for  evaluaHon  and  manipulaHon  of  inbound  metadata  

•  RouHnely  administered  audits  of  the  enHre  database  

•  All  the  vendors  maintain  specialists  for  file  review  and  manual  metadata  acHviHes    

Page 68: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Automated  Processes  •  Audits  of  inbound  or  recently  added  metadata  to  

detect  missing  metadata,  formaing  problems,  and  other  errors  

•  Metadata  correcHon,  normalizaHon,  addiHon  of  proprietary  data,  and  data  mapping  

•  Linking  to  name  authority  files  •  Establishing  links  and  checking  for  consistency  

across  Htles,  e.g.  the  same  Htle  in  different  formats,  Htles  belonging  to  the  same  series  

•  AddiHon  of  licensed  metadata,  e.g.  reviews,  tables  of  contents,  etc  

Page 69: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Staff  Processes  •  Book-­‐in-­‐hand  review  of  metadata  (for  the  

bookselling  vendors)  •  Close  review  of  high-­‐demand  and  high-­‐profile  Htles  

•  Manual  changes  and  addiHons  based  on  audit  reports  

•  Changes  and  addiHons  in  response  to  internal  staff  (buyers,  store  personnel,  etc.),  consumer,  and  publisher  reports  

•  CommunicaHon  with  publishers  to  resolve  issues  discovered  through  automated  or  manual  processes  

Page 70: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Where  Changes  Go  

Proprietary  databases  used  for:  1.  To  support  internal  processes  such  as  ordering,  

invoicing,  etc  

2.  To  populate  consumer-­‐facing  websites  3.      To  create  licensed  data  products  and  services  

such  as  Books  in  Print  and  ongoing  data  feeds  to  subscribing  customers    

Page 71: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

Benefits  of  Changing  Metadata  •  Vendor  panelists  invest  significant  financial,  

technical,  and  staff  resources  on  metadata  to:  –  Increase  sales  

–  Improve  search  engine  discoverability  and  customer  experience  

–  Create  efficiencies  in    

•  Internal  processes    •  Supply  chain  communicaHon  

•  TransacHons  

Good  metadata  =    beLer  sales  and  reduced  costs  

Page 72: Who updates publisher metadata and why? Downstream vendors on what happens to metadata in the supply chain. BEA 2013

QuesHons?  

This  presentaHon  will  be  available  from  the  BEA  website  aQer  the  conference.  

Or  contact  Renée  Register  for  a  PDF  of  the  presentaHon.  

[email protected]