Specifications

Configuring iNEWS Servers
51
MOS item is inserted into the story, the time associated with that item may
be inserted too—either appearing in the MOS-DURATION field for an
item dragged to the Story Form panel, or as a Runs time shown in a
machine control event in the Instruction panel. Whether a MOS item’s
time is inserted is determined by settings defined in the SYSTEM.MOS-
MAP story. See “Edit the SYSTEM.MOS-MAP Story” on page 51 for more
information.
If both MOS-DURATION and RUNS-TIME fields are used in the Story
Form panel, then the RUNS-TIME field will display the calculated sum of
time appearing in the MOS-DURATION field and all Runs times from the
Instruction panel. The TOTAL-TIME field will show the calculated sum of
values from the RUNS-TIME, AUDIO-TIME, and TAPE-TIME fields.
n
Users may manually enter times in the TAPE-TIME field. The time
appearing in the AUDIO-TIME field is the estimated read time of the text
in the Story Text panel, as calculated by the iNEWS system, according to
reading speeds defined by the system administrator.
Step 4: Edit the SYSTEM.MOS-MAP Story
The SYSTEM.MOS-MAP story contains a section of information, known
as the DeviceTable, which consists of two columns:
• The first column has the MOS device’s mosID—reported by the
vendor's ActiveX control. It must match the <mos> value in the
mosconfig.xml file, which is installed on the MOS Gateway
Server.
• The second column has an iNEWS device name associated with the
mosID to display in machine control events in the story body. It must
match the <amcp> value in the mosconfig.xml file.
The following is an example of a SYSTEM.MOS-MAP story with a single
device listed in the DeviceTable:
TABLE-START DeviceTable
Mos.omnibus.co.uk OmniMOS
TABLE-END
n
If the SYSTEM.MOS-MAP story does not exist, it must be created in
iNEWS as the first story in the MOS-Map queue in the System directory.