collecting_society

• HFA Song Code
  • Harry Fox Song Code https://secure.harryfox.com/songfile/faq.jsp#faq30
  • creation
• IPI
  • Interested Parties Information https://en.wikipedia.org/wiki/Interested_Parties_Information
  • party
• ISNI
  • International Standard Name Identifier http://www.isni.org/
  • party
• ISRC
  
  • International Standard Recording Code https://en.wikipedia.org/wiki/International_Standard_Recording_Code
  • creation (gerade in release)
• ISWC
  • International Standard Musical Work Code https://en.wikipedia.org/wiki/International_Standard_Musical_Work_Code
  • creation
• IPN
  • International Performer Number https://www.ppluk.com/membership/more-information/ipn/
  • artist (solo)
• GRid
  • Global Release Identifier https://en.wikipedia.org/wiki/Global_Release_Identifier
  • release
• DPID
  • DDEX Party Identifier https://kb.ddex.net/display/HBK/DDEX+Party+Identifier+Standard
  • party
• EAN/UPC
  • Universal Product Code https://en.wikipedia.org/wiki/Universal_Product_Code
  • release (schon da)
• CWR
  • Common Work Registration https://de.wikipedia.org/wiki/Common_Work_Registration
  • creation

Maybe a standard table for all IDs or for each object?
- name
- version
- code

If one table for all objects: a reference would be needed, the performance disadvantage is unclear (probably one stringsearch more than a integer id, as the string of the object is saved, e.g. 'web_user/1')