Summary: | Selecting a framework on import does not modify leader or 008 correctly | ||
---|---|---|---|
Product: | Koha | Reporter: | Kyle M Hall <kyle> |
Component: | Cataloging | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | katrin.fischer, 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
Kyle M Hall
2012-07-26 12:07:09 UTC
Hi Kyle, I am not sure this should work this way? I theory it doesn't matter how you name your frameworks. They don't even have to be by media types, or a library could have multiple frameworks for different kinds for serials. And if you configure default values in the frameworks, I still don't think that they should overwrite incoming data where that field exists. So I think this change needs at least checkbox or something to be done during import. But perhaps it would be better to have a general tool for changing bibliographic records in bulk, then putting too much different functonality into import scripts. I was thinking that serials are a special case such that we could have a 'continuing resource' checkbox to tell Koha that a given framework is a serials framework. Then, Koha would know if a given framework was a serials framework and modify the leader. The 008 field sounds more complicated, as that would require translation, perhaps a system preference containing the new value would be in order? I think the problem could occur with other data too, like electronic ressources, analytics and so on. So perhaps we really need a more general tool? (In reply to comment #2) > I was thinking that serials are a special case such that we could have a > 'continuing resource' checkbox to tell Koha that a given framework is a > serials framework. Then, Koha would know if a given framework was a serials > framework and modify the leader. The 008 field sounds more complicated, as > that would require translation, perhaps a system preference containing the > new value would be in order? I don't think this is a good solution. If you are importing 300 serial records, they should already have leader and 008 fields. If they do not, then there is a problem with your records, and special-casing their treatment doesn't make sense because this isn't a solution, it's just a workaround that will come back and bite you later (had some legitimate book records in with those serials? Sorry, the leader and 008 have been clobbered by Koha). In addition, if we're going to handle serials like this (LDR/07=s), we also need to handle analytics (LDR/07=a or =b), collections (LDR/07=c), and the various formats that require wholly different 008 fields. |