Differences

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

--- tutorials:musicmaster:nexus-api-setup [2017/08/31 15:06] – [Prerequisites] tw
+++ tutorials:musicmaster:nexus-api-setup [2019/07/09 16:18] (current) – external edit 127.0.0.1
@@ Line 48: / Line 48: @@
 First, type the name of the MusicMaster databases, as defined in the Nexus server configuration, or click the dropdown arrow to select it from the list. The latter will also serve as a connection test, as it will query a list of available databases directly from the Nexus server.
+On the //System Field Mapping// tab, we link some MusicMaster fields to mAirList's internal metadata fields:
+  * Artist
+  * Title
+  * Duration
+  * Filename
+  * XML Metadata
+  * ID
+  * Category
+  * NonMusic
+  * Ramp 1 (seconds)
+  * Ramp 2 (seconds)
+  * Ramp 3 (seconds)
+  * Ramp 1 (mm:ss)
+  * Ramp 2 (mm:ss)
+  * Ramp 3 (mm:ss)
+  * Color Key
+When you enter the dialog for the first time, only numeric IDs will be displayed. As soon as you use the dropdown for any field, mAirList will fetch the field names from the Nexus server:
+ {{ :tutorials:musicmaster:pasted:20170831-171112.png?400 }}
+Notes:
+  * XML Metadata is the Memo field that you created in order to save non-standard metadata fields as XML (see //Prerequisites// section above).
+  * The ID field is where mAirList will save its Internal Database ID values during [[tutorials:musicmaster:mairlistdb-sync-nexus|mAirListDB library synchronization]]. It is also used by the direct [[tutorials:musicmaster:nexus-database-connection|Nexus database connection]] to reference items in an external database.
+  * Ramps can either be stored (and retrieved) in "full seconds" or "mm:ss" format. Just fill out the field mapping for the format that you wish to use, and leave the other one empty.
+  * Color key is used by the [[tutorials:musicmaster:nexus-database-connection|Nexus database connection]] to color items based on a particular field, e.g. the Category field.
+On the //Attribute Field Mapping// tab, you can link additional attribute fields in mAirList to fields in MusicMaster:
+{{ :tutorials:musicmaster:pasted:20170831-172523.png?400 }}
+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://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 parent 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 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 //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!