[Koha-bugs] [Bug 6590] Removing hyphens from isbn and issn when cataloging a biblio

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6590

Frédéric Demians <frederic at tamil.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fridolyn.somers at gmail.com

--- Comment #5 from Frédéric Demians <frederic at tamil.fr> 2011-07-16 08:45:02 UTC ---
> If UNIMARC handle multiple isbns, its no just a problem to loop over
> them, and remove hyphens in every one. And, the original isbn is kept
> in isbn field in biblioitems table.

But (1) when a library will export its catalog in ISO2709, ISBN fields
will come from biblioitems.marcxml not biblioitems.isbn and (2)
biblioitems.isbn size is only 30 characters which could be too short
with multiple ISBNs.

> When a search is performed, only during search specifically by isbn or
> issn, hyphens are removed from query, but not during other search like
> kw, au ...

Ok, so it's not that bad but it would be great if a anywhere search
would work also with ISBN.

> I'm agree with the modification in koha. Add another index type to
> handle this.  I saw somebody did it a few days ago, here:

> http://lists.indexdata.dk/pipermail/zebralist/2010-May/002423.html , it maybe
> work, its only a decision about handle it.

We can ask to Frydolin. I've added him to this thread.

> We need this change, by one way or another, because most of the people
> search an isbn without hyphens, and as I saw, most of the Z we used,
> could handle this, searching with or without hyphens.

I agree and I support 100% your work. I really want it into Koha but we
also need to avoid a regression. I know libraries who count on Koha to
catalog normalized UNIMARC biblio records.

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.