tutorials:musicmaster:nexus-api-setup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tutorials:musicmaster:nexus-api-setup [2017/08/31 15:17] – [mAirList Setup] tw | tutorials:musicmaster:nexus-api-setup [2019/07/09 16:18] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 77: | Line 77: | ||
* Ramps can either be stored (and retrieved) in "full seconds" | * Ramps can either be stored (and retrieved) in "full seconds" | ||
* Color key is used by the [[tutorials: | * Color key is used by the [[tutorials: | ||
+ | |||
+ | On the //Attribute Field Mapping// tab, you can link additional attribute fields in mAirList to fields in MusicMaster: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Just type a mAirList attribute name in the left-hand column, and select the corresponding MusicMaster field in the right-hand column. **Use the cursor-down key to add more rows.** | ||
+ | |||
+ | ===== MusicMaster Enterprise ===== | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | The Nexus functions mAirList will handle Enterprise databases in the following way: | ||
+ | |||
+ | * All library **write** operations will be performed on the parent database. | ||
+ | * Library **read** operations during [[tutorials: | ||
+ | * All schedule **read** operations and their corresponding library lookups will be performed on the child database. | ||
+ | |||
+ | One important thing to understand is that the MusicMaster field IDs can (and often will) be different between the parent and the child databases. So you must actually configure the field mapping twice in mAirList: once for the parent database, and once for the child database. | ||
+ | |||
+ | To set up a Nexus connection to an Enterprise database, switch to the // | ||
+ | |||
+ | For non-Enterprise databases, it is important to leave the // |
tutorials/musicmaster/nexus-api-setup.1504192629.txt.gz · Last modified: 2019/07/09 16:19 (external edit)