Consider productCatalog element for media

[cjcodeproj]

Right now media devices are only cataloged by numbers tied to the physical product.

   <productId>
    <barcode type='upc'>883929301331</barcode>
   </productId>

or

   <productId>
    <barcode type='upc'>926663164794</barcode>
    <sku retailer='bby'>4771602</sku>
    <other>
     <name>Shout Select Spine Number</name>
     <value>3</value>
    </other>
   </productId>

It may make more sense to extend the structure to be more flexible, and to group similar data together.

 <productCatalog>
   <salesId>
     <barcode type='upc'>883929301331</barcode>
   </salesId>
   <shelving>
     <variantTitle sortable='true'>Three Days Of The Condor</sortTitle>
   </shelving>
 </productCatalog>

Are there other metrics that can be recorded in this data structure? When music comes around, what other values make sense?

This would also benefit ticket #43

Note: This would be a pretty extensive change if it is determined to be suitable.

[cjcodeproj]

Follow-Up

The element will need a structure that allows for each integration with third party or non-standard identifiers.

Consider this:

<other>
 <name>Criterion Spine Number</name>
 <value>1027</value>
</other>

One goal should be avoiding an endless string of name/value pairs, especially when the data is consistent.

Consider these values:

• Music album catalog number
• Vinyl record matrix number
• Collection number tied to a vendor (Criterion, Shout Factpry, Arrow, etc)
• Proof of purchase

Each of these values are potentially unique keys. The element structure should allow for external elements with their own namespaces.

Rough example:

<other xmlns:shout='http://shoutfactory/'>
 <shout:spineNumber>3</shout:spineNumber>
</other>