Bug 4814 - Item Type (MARC952 $c) not self-populating from imported OCLC bib
Summary: Item Type (MARC952 $c) not self-populating from imported OCLC bib
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 3.4
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Galen Charlton
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-25 18:40 UTC by Kurt
Modified: 2017-06-14 22:10 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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt 2010-05-25 18:40:36 UTC
After importing a bib record from OCLC, the item record Item Type in MARC 952 $c does not automatically populate itself with the value in the bib record's 942 $c unless I first open the bib record and save it.  

There is often no other reason to open the bib record in the edit screen at that point, so it would save 2 mouse clicks plus the wait time while the bib saves itself, in addition to having to select an Item Type while adding the Item Record, if that subfield self-populated as it does whenever the bib record has been opened and saved.  (Note that no actual editing of the bib record need happen; all that has to happen is that it be opened in the edit screen and then saved, it that happens then the 952 $c fills itself with whatever is in the bib record's 942 $c.)


Koha 3.01.00.061 on a hosted Linux bluehillils 2.6.18-6-686 #1 SMP Fri Dec 12 16:48:28 UTC 2008 i686 GNU/Linux with Perl version 5.008008.
Comment 1 Galen Charlton 2010-05-25 20:21:22 UTC
Are you editing the 942$c in OCLC before importing the bib?
Comment 2 Kurt 2010-05-26 14:06:24 UTC
(In reply to comment #1)
> Are you editing the 942$c in OCLC before importing the bib?

No.  Normally, I don't think we would do anything in OCLC with the 9XX fields.  Certainly haven't manually edited the 942$c in OCLC.

Kurt
Comment 3 Katrin Fischer 2015-01-06 17:22:53 UTC
I think we need more information on this and maybe an example record.

What Koha does is that it suggests the itemtype from 942$c in the bib record as the item type for the item (952$y).

The 942$c will only be populated on import, if it is in the imported record and contains a valid itemtype code that exists in Koha.
Comment 4 Katrin Fischer 2016-08-14 15:11:39 UTC
We don't have enough information to reproduce this:

- How was the record imported? Staged tools, Z39.50, SRU, bulkmarcimport, connexion client functionality?
- Does the problem appear in current versions of Koha?
- How does a sample record look like?

I think this is more likely to be an issue outside of Koha - maybe capitalization of the itemtype code or similar. I am setting resolved INVALID for now - please reopen if you have more information and still see this problem happening.