Differences

This shows you the differences between two versions of the page.

--- tutorials:musicmaster:nexus-api-setup [2017/08/31 15:45] – [MusicMaster Enterprise] tw
+++ tutorials:musicmaster:nexus-api-setup [2019/07/09 16:18] (current) – external edit 127.0.0.1
@@ Line 86: / Line 86: @@
 ===== MusicMaster Enterprise =====
-[[https://www.musicmaster.com/?p=2175|MusicMaster Enterprise]] is a feature of MusicMaster where you have one "master" (or "parent") database that holds the metadata for all songs, which is then replicated to one or more "slave" databases, where the actual scheduling takes places.
+[[https://www.musicmaster.com/?p=2175|MusicMaster Enterprise]] is a feature of MusicMaster where you have one "parent" database that holds the metadata for all songs, which is then replicated to one or more "child" databases, where the actual scheduling takes places.
 The Nexus functions mAirList will handle Enterprise databases in the following way:
-  * All library **write** operations will be performed on the master database.
+  * All library **write** operations will be performed on the parent database.
-  * Library **read** operations during [[tutorials:musicmaster:mairlistdb-sync-nexus|mAirListDB library synchronization]] will also be performed on the master database.
+  * Library **read** operations during [[tutorials:musicmaster:mairlistdb-sync-nexus|mAirListDB library synchronization]] will also be performed on the parent database.
-  * All schedule **read** operations and their corresponding library lookups will be performed on the slave database.
+  * 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 master and the slave database. So you must actually configure the field mapping twice in mAirList: once for the master database, and once for the slave 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 //Master/Parent// tab, select the Database and set up the field mapping.
+To set up a Nexus connection to an Enterprise database, switch to the //Master/Parent// tab, select the Database that is the "master" database in the Enterprise setup, and set up the field mapping.
 For non-Enterprise databases, it is important to leave the //Database/Station ID// field empty for the //Master/Parent// database!