This has been the normal behaviour since the summer of 2010 when it
was initially implemented. As the content of the $0 subfield is not
expected to be read by any humans other than to cataloguers, we didn't
think this presented a problem.
Tools that display the contents of a 650, for example, should strip
the $0 subfield out no matter where it appears in the field, right?
This has been the normal behaviour since the summer of 2010 when it
was initially implemented. As the content of the $0 subfield is not
expected to be read by any humans other than to cataloguers, we didn't
think this presented a problem.
Tools that display the contents of a 650, for example, should strip
the $0 subfield out no matter where it appears in the field, right?