Hi, On Wed, Oct 30, 2013 at 7:21 PM, Elaine Bradtke <eb@efdss.org> wrote:
Still, there's an underlying quirk - if Koha sees a character it doesn't like in the 008 editing window, it skips over it and collapses the rest of the data. While the non # characters were originally in the correct place - once we touch that field in the editing window they are moved to a different position, and either ignored because they're not valid or dumped in the wrong place where they are valid, but incorrect.
Of course if it didn't do this, we probably would have never noticed the # issue.
Indeed, this is worth writing up as a bug report; I've certainly run into MARC records in the past that used # where blanks were meant. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org