Bug 14815 - Different leader values per framework code
Summary: Different leader values per framework code
Status: ASSIGNED
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Marcel de Rooy
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-14 11:48 UTC by Marcel de Rooy
Modified: 2017-09-05 14:41 UTC (History)
4 users (show)

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


Attachments
Bug 14815: Different leader values per framework code (5.12 KB, patch)
2015-09-29 11:04 UTC, Marcel de Rooy
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel de Rooy 2015-09-14 11:48:57 UTC
This is a follow up of report 14201 removing some dead code for leader plugins.
Based on the framework code, we could define some different leader values in a preference (or so) and enhance the leader plugin.
Comment 1 Marcel de Rooy 2015-09-14 11:56:03 UTC
document.forms['f'].Frameworks.value
<select name="frameworkcode" id="Frameworks" onchange="Changefwk(this);">
Comment 2 Marcel de Rooy 2015-09-29 11:04:15 UTC
Created attachment 42947 [details] [review]
Bug 14815: Different leader values per framework code

NOTE: This is not yet ready for signoff, but just a concept.

Use the defaultvalue in the framework to fill the leader.
Add different defaults in the simple_bib_frameworks.
TODO: Copy those changes to the various install languages.
Remove the default from the plugin code.
Add a db rev to insert the default into existing frameworks.
TODO: Make sure that you run this only for MARC21 databases.

Use existing functionality to change the default for your frameworks.
Comment 3 Marcel de Rooy 2015-09-29 11:05:58 UTC
Hector: What do you think of the direction made by this conceptual patch?
Instead of just saying "Add a default to your framework", we could improve Koha by adding some more specific leader values in simple_bib_frameworks etc.
Comment 4 Héctor Eduardo Castro Avalos 2015-09-29 17:17:38 UTC
God job, Marcel.
You go in right way.

I just add here the different leaders to take in consideration
Maps = Framework not in Koha
00000nem a2200000 i 4500
     nem a22     7i 4500

Score = Framework not in Koha. By the way this two frameworks should exist in koha.
00000ncm a2200000 i 4500
     ncm a22     7i 4500

Sound recording = SR
00000njm a2200000 i 4500
     njm a22     7i 4500

Binder or equal to Loose-leaf services is a kind of integrating resource = IR
00000nai a2200000 i 4500
     nai a22     7i 4500

Models is a three-dimensional artifact or naturally occurring object = AR
00000nrm a2200000 i 4500
     nrm a22     7i 4500

Kits = KT
00000nom a2200000 i 4500
     nom a22     7i 4500

DVD, VHS = VR
00000ngm a2200000 i 4500
     ngm a22     7i 4500

NOTE:
1) Look that you're coding in AACR2 (pos 18=a) and in minimal level (pos 17=7), the leader above provide RDA and full level, the example below with minimal level. I think IMHO nobody is cataloging at minimal level.
2) Pos 7 can take a lot of codes by the default code in 'm' see <http://www.oclc.org/bibformats/en/fixedfield/type.html> section 'Combinations of Type and BLvl codes'

Regards
Comment 5 Héctor Eduardo Castro Avalos 2015-09-29 18:09:41 UTC
This is excellent, Marcel, Koha change 008 depending with the data coded in Leader, i.e., if leader has '     nas a22     7i 4500' field 008 change in type of meterial to CR - Continuing Resources. But figure out that by default the 008 is filled with '150929b        xxu||||| |||| 00| 0 eng d' and this not fit with the record created, the default value most be like this:
'150929c    9999xxu r         0    0eng d'