Bug 34590 - Include syntax option in settings when staging MARC records
Summary: Include syntax option in settings when staging MARC records
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 22.11
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-22 15:32 UTC by Esther Melander
Modified: 2023-09-20 17:26 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Esther Melander 2023-08-22 15:32:03 UTC
Currently the settings for an import profile include record type, character encoding, and format. It would be nice to also include syntax. This is useful for importing foreign language records with unique characters and punctuation. Syntax is currently an option when configuring z39.50 searches. It would be nice to have when Staging MARC records too.
Comment 1 Katrin Fischer 2023-08-23 12:58:44 UTC
Hi Esther, can you give an example of what different syntax settings would look like?
Comment 2 Esther Melander 2023-09-12 19:37:21 UTC
A library gave me this example.

MARC21/USMARC places a personal name in 100$a (100 1 _ $aGonzález, Juan)

UNIMARC places a personal name in 200$a (surname) and 200$b (forename) (200 _ 1 $aGonzález$bJuan)
Comment 3 Katrin Fischer 2023-09-19 21:19:15 UTC
Hi Esther, I think we don't offer this, because you can only import in the format that your Koha installation is set up for. If you have a MARC21 installation, you can only import MARC21, same for UNIMARC. We can't convert.
Comment 4 Katrin Fischer 2023-09-19 21:20:49 UTC
The foreign languages/unique characters etc. should be covered by the encoding setting - it's not related to the MARC format.
Comment 5 Esther Melander 2023-09-20 15:13:16 UTC
Syntax is an option when configuring z39.50 search targets. If this option truly can't be used, then it should be removed in the z39.50 configuration options.

Also, in this case, syntax appears to deal with how data is mapped and not special characters, as described in comment 2.
Comment 6 Katrin Fischer 2023-09-20 17:26:46 UTC
(In reply to Esther Melander from comment #5)
> Syntax is an option when configuring z39.50 search targets. If this option
> truly can't be used, then it should be removed in the z39.50 configuration
> options.

I stumbled on the same thing, but you are correct. In some cases it might work, because the formats are very similar to MARC21, but UNIMARC is too different. You could import it, but it would not make sense at all as all the fields are different.

> Also, in this case, syntax appears to deal with how data is mapped and not
> special characters, as described in comment 2.


Correct, I was referring to your initial description that talked about special chaaracters.