Bug 5190

Summary: MARC and UNIMARC bibliographic fields documentation accesible when cataloging
Product: Koha Reporter: Tomás Cohen Arazi <tomascohen>
Component: CatalogingAssignee: Galen Charlton <gmcharlt>
Status: CLOSED FIXED QA Contact: Bugs List <koha-bugs>
Severity: enhancement    
Priority: PATCH-Sent (DO NOT USE) CC: chris, cnighswonger, jos.kohado, koha.sekjal
Version: 3.4   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Attachments: Enable MARC documentation
follow-up patch with improvements

Description Tomás Cohen Arazi 2010-08-31 20:39:23 UTC
This was discussed on the koha-devel list, and I finally sent some patches for this. I just open the bug so we can track the status of it.
Comment 1 Tomás Cohen Arazi 2010-10-21 12:52:48 UTC
Created attachment 2697 [details] [review]
Enable MARC documentation
Comment 2 Galen Charlton 2010-10-27 13:48:59 UTC
Started work testing and improving the patch.  Current issues:

* links to MARC21 fields <= 099 broken
* patch breaks field cloning
Comment 3 Galen Charlton 2010-10-30 02:39:01 UTC
Created attachment 2713 [details] [review]
follow-up patch with improvements
Comment 4 Chris Cormack 2010-11-04 07:54:39 UTC
Patches pushed, please test and close
Comment 5 MJ Ray (software.coop) 2010-11-10 08:49:09 UTC
This bug is mentioned in:
bug 5190: link to	MARC21/UNIMARC online doc in the bib editor http://lists.koha-community.org/pipermail/koha-patches/2010-October/012766.html
bug 5190: improve linking to MARC field	documentation http://lists.koha-community.org/pipermail/koha-patches/2010-October/012767.html
Comment 6 Chris Nighswonger 2010-11-18 03:15:36 UTC
This bug has a patch presently committed to HEAD and 3.2.x.

Please take the appropriate action to update the status of this bug.

Remember, bugs which have been resolved should be tested and marked closed, preferably by the original reporter.
Comment 7 Chris Nighswonger 2010-11-30 15:54:51 UTC
A fix for this bug has been committed to the current development HEAD as well as released in 3.2.1.