Skip to content

Onyx

What we are calling the "Onyx" data is the data that is stored in MongoDB Atlas which supports the Onyx applications.

The entire MongoDB footprint is about 17 databases and roughly 492 collections.

The Onyx data can be found in the UTA database, which as of this writing consists of about 85 collections. We could be wrong but only nine appear to be relevant for a authoritative data load into the target model:

Relevant Collections

CollectionDoc count
artists_utour3718
companies47344
locations_utour20366
people137676
people_utour38726
prod_companies16723
prod_people117078
prod_relationships23506
relationships8385

People and Companies

For people types, we see:

TypeCount
(blank)4
Ad Hoc1
Client14500
Employee1588
Industry Contact116713
Outlook5
Shared Contact15
null4835

For company types, we see only:

TypeCount
null1
Branding/Product Placement, Publicity, Entertainment Marketing1
Client53
Industry Contact47269
Shared Contact4

Relationships

There is at least one relationships table which is used to join people to people and people to companies. This may be created by the Mongoose ODM used at UTa: Mongoose layers on top of the MongodB driver and can add a veneer of "simulated relational database" to help the application developer.

At first glance the internal team (agent, "responsible agent") seems to be more maintained.

Unique relationship types in relationships collection:

RelationshipCount
(blank)3
Agency65
Agent4570
Attorney247
BusinessAffairs1
BusinessPartner1
CoverageAgent9
Manager7
Negotiator2
Network2
PersonalManager447
Producer1
Publicist2
ResponsibleAgent2976
Studio1
UnknownRole51

In the prod_relationships collection:

RelationshipCount
(blank)5
Agency76
Agent16517
Attorney283
BusinessAffairs1
BusinessPartner1
Manager1
Network2
PersonalManager527
Publicist1
ResponsibleAgent6033
UnknownRole59

Initial Gap Analysis

  1. No data on relationship start and end date could be found anywhere in the MongoDB collections. There were some create/modify dates.

  2. Roles or relationships we need but cannot discern in the Onyx data include Buyer, Client Company, Client Group, and possibly Venue although we have not reviewed the Locations collection yet.

  3. It is unclear if we have a good enough list of Participant roles (attorney, manager, etc).

  4. There is a considerable mismatch in the counts for similar data in Netsuite. For example, on client, Onyx reports 14,553 while Netsuite reports 16,347. We need to understand more detail about this.

Confidential. For internal use only.