Whilst working through bug 11175 I was reminded of our inconsistent use of useControlNumber and it's lack of accounting for 003 fields.
With the introduction of the ability to search using 003 as part of the query for analytics, we should account for this in the cataloguing workflow. We should check for the presence of 'MarcOrgCode' being defined (at library or system level) and if it is being used we should copy the value of the 003 of the parent record into the constructed 773.
This makes sense, but I think we need a depends on for the bug adding the 003 index?
Created attachment 124426 [details] [review] Bug 21469: Add 003 into 773$w when required This patch looks at the MarcOrgCode preference and if present it will prepend the host 003 data in brackets to the 773$w link field in the child record.
Created attachment 124427 [details] [review] Bug 21469: Add 003 into 773$w when required This patch looks at the MarcOrgCode preference and if present it will prepend the host 003 data in brackets to the 773$w link field in the child record.
I'd love your help with writing a test plan for this Katrin.. I think it should work as expected, but I'm not even actually sure if we need to bind it on the presence of MARCOrgCodes being defined.. we might actually be OK just always prepending 003 if/when it's present in the host record.