Bug 11472

Summary: MARC21 008 plugin should consult leader to set default type of material
Product: Koha Reporter: Galen Charlton <gmcharlt>
Component: CatalogingAssignee: Galen Charlton <gmcharlt>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: bgkriegel, dcook, m.de.rooy
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Galen Charlton 2014-01-02 19:02:50 UTC
Currently, when you use the MARC21 008 plugin to edit field positions, the type of material is always set to BKS, regardless of the actual material type of the record.  This means that you always have to change the material type in the fixed field editor to the appropriate value.

It would be nice if the type of material were determined by the current leader value.

The "material type" in this context is determined by the Leader/06 and Leader/07.  The "input conventions" heading near the bottom of http://www.loc.gov/marc/bibliographic/bdleader.html contains a "dependencies" section that designates the appropriate material type for the 008 based on the Leader/06-07.
Comment 1 David Cook 2014-06-05 07:02:42 UTC
This is something that I've been thinking about lately as well. I think the following would be very possible.

Dependencies

Field 008/18-34 Configuration
If Leader/06 = a and Leader/07 = a, c, d, or m: Books
If Leader/06 = a and Leader/07 = b, i, or s: Continuing Resources
If Leader/06 = t: Books
If Leader/06 = c, d, i, or j: Music
If Leader/06 = e, or f: Maps
If Leader/06 = g, k, o, or r: Visual Materials
If Leader/06 = m: Computer Files
If Leader/06 = p: Mixed Materials

Capitalization - Alphabetic codes are input as lowercase letters.

I might actually look at this myself tomorrow or next week...
Comment 2 Bernardo Gonzalez Kriegel 2014-06-05 19:44:50 UTC
Mmm, duplicate of Bug 9093?
Comment 3 David Cook 2014-06-05 23:48:12 UTC
Yep, definitely a duplicate.

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