Summary: | Koha to MARC mapping 264$a, $b, and, $c | ||
---|---|---|---|
Product: | Koha | Reporter: | Héctor Eduardo Castro Avalos <hector.hecaxmmx> |
Component: | System Administration | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | new feature | ||
Priority: | P5 - low | CC: | gmcharlt, m.de.rooy, marjorie.barry-vila, mtj |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10306 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13723 |
||
Change sponsored?: | --- | Patch complexity: | Medium patch |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Héctor Eduardo Castro Avalos
2014-08-13 17:40:30 UTC
Hmm, I think this bug is applicable for 'master' Koha too, not just 3.16.x I will update bug... I think this is kind of a duplicate to bug 10306 - which I found after my comment on the other bug. I am not sure new fields are the best solution here. It means that you will have to change lots of places in Koha - because the same information is stored in 2 different places - we already have this problem with copyrightdate and publicationyear, where one is used for MARC21 and the other in UNIMARC. Why not store it in the same place and allow multiple mappings with kind of a sequence? If 264 is not there, try 260. This would make things much easier, also for reporting. Hm, there is also the other way around - if we make Koha-to-MARC-Mappings 1:n, we also need to change the procedures that are used for creating a record from a non-marc format, for example in acquisitions. |