Search

Communicating data issues in MWN

In MWN 1.3, the acknowledgement message FtpAcknowledgementMessage has three elements to communicate technical issues experienced by a recipient of a message: FileStatus (which has an AVS with the values FileOK and UserDefined), ErrorText (for a comment to help the recipient of the acknowledgement message to resolve the issues complained about) and ProposedActionType (which has an AVS with the values Resubmit and UserDefined). These elements are not designed to describe multiple issues at the musical work level. However, data issues relating to individual works can be communicated in the FtpAcknowledgementMessage as follows until a more expressive acknowledgement message is provided in a future version of the MWN standard.

Communicating CWR error codes

The CWR specification, e.g. CWR08-2493, describes error messages that CWR users can send to communicate data errors. Each of them is described by a Message Type, a Message Level and a Message Sequence. For instance, a society-assigned agreement number that did not match the identifier for an original agreement is encoded as “PWR F 004”.

In MWN, the string composed of these three values can be communicated in the ErrorText element, with a colon used as a separator:

<ErrorText>PWR:F:004</ErrorText>

Communicating CWR error codes at a specific level

To communicate to which entity such a CWR error code applies, a reference identifier defined in the message, such as the MusicalWorkReference of the musical work or the PartyReference of the party, has to be included as a fourth element, i.e. in the following form:

<ErrorText>PWR:F:004:W12345</ErrorText>

Communicating multiple CWR error codes

The element ErrorText is not repeatable, which restricts how multiple issues can be described. Multiple CWR error codes, including reference identifiers such as MusicalWorkReferences, can be concatenated in the ErrorText:

<ErrorText>PWR:F:004:W12345,NWR:F:004:W11111</ErrorText>

Variations of the CWR error codes by customised error message texts cannot be communicated this way. Also, the syntax proposed here for communicating CWR error codes is not validated by the XSD for the standard, so a message sender can only rely on a recipient processing the data as intended if the messaging parties have agreed to adhere to the proposed format.