Bug 12731 - Mulitiple setspecs that use the same MARC tag only work for the first setspec
Summary: Mulitiple setspecs that use the same MARC tag only work for the first setspec
Status: RESOLVED DUPLICATE of bug 24531
Alias: None
Product: Koha
Classification: Unclassified
Component: Database (show other bugs)
Version: 3.16
Hardware: All All
: P5 - low normal (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-07 14:57 UTC by Steve Sowder
Modified: 2020-03-05 20:38 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Sowder 2014-08-07 14:57:50 UTC
I have discovered that if you have a record that is in multiple OAI Sets
you cannot use the same MARC tag for mapping them.

Thus, if you have two sets with mapping as

590a  is equal to  TOM
590a  is equal to  MARY

And a record with

...
590a  TOM
590a  MARY
...

This record will be in the OAI set "TOM" and it will NOT be in the set
"MARY".

If you switch the order of the 590a so that

...
590a MARY
590a TOM
...

Then the record will be in the OAI set "MARY" but not in "TOM".

Because the "map reader" stops after the first mapping match.

I consider this a bug.
It should read all of the 590a tags and map each one that is a match.

Don't forget that the MARC tag used in OAI mapping must be an indexed tag.

BTW: This is Koha V3.16.02.000
Comment 1 Owen Leonard 2016-06-23 18:04:40 UTC
Is bug still valid in master?
Comment 2 Tomás Cohen Arazi 2020-03-05 20:38:05 UTC

*** This bug has been marked as a duplicate of bug 24531 ***