In field 240 (Uniform Title) the $n (Number of part/section of a work) is repeatable, for example
240 10 |a Quatuors en fugues, |n op. 1. |n No 2
It is converted as:
bf:partNumber "No 2",
"op. 1." ;
The problem is that the two part numbers are related and appear in a specific order: op. 1. No 2. In a triple store, there is no order, so the statement "No 2 op. 1." is equally "true" but incorrect.
This is an example of the larger problem of needing to order data elements. Unfortunately, combining both $n subfields together does not work in all cases.
In field 240 (Uniform Title) the $n (Number of part/section of a work) is repeatable, for example
240 10 |a Quatuors en fugues, |n op. 1. |n No 2
It is converted as:
The problem is that the two part numbers are related and appear in a specific order: op. 1. No 2. In a triple store, there is no order, so the statement "No 2 op. 1." is equally "true" but incorrect.
This is an example of the larger problem of needing to order data elements. Unfortunately, combining both $n subfields together does not work in all cases.
(OCLC # 4157133)