Multiple 006/007 fields for MARC Editor

[Simon Mai]

MARC Fields 006, 007 are repeatable according to the current MARC standards (http://www.loc.gov/marc/bibliographic/bd007.html).
Evergreen 2.3.x will only allow the entry of one 006 and one 007 field per bibliographic record. Some bibliographic items may require multiple 006 or 007 fields-for example, Blu-ray/DVD bundles and multi-item type kits (book, cassette, CD-ROM, etc.).

With the current MARC editor of Evergreen, "Add/Replace 006/007" will add a 006/007 field if there is none. Replace, of course, completely overwrites the 006/007 field in the record. Since subfields are not marked in the 006/007 fields, a blank field cannot be added and filled in because the subfield delimiter (double dagger) is hard-coded to the field. Staff is not able to add a second 006/007 field to the record.

Ideally, the functionality needed is the ability to add multiple 006/007s, edit any of the 006/007s, and delete any of them. This functionality should be equivalent to the current functionality in the other date fields--right-clicking with drop down options.

So I did updated the MARC editor to change "Add/Replace 006/007" into ""Add 006/007" and support staff to add multiple 006/007 fields. To delete any these fields, just right click and select "Remove Row" as the way we've used to remove any data fields.

I'm working with Evergreen ver. 2.3.x.

PS: I updated this bug to keep the "Add/Replace 008" like the current option, since this 008 field is NOT repeatable as Galen suggested.

[Galen Charlton (gmc)]

The patch is too broad, as the 008 field is NOT repeatable: http://www.loc.gov/marc/bibliographic/bd008.html.

[Simon Mai (simonmai)]

@Galen: Oh, ok, let me double check. If the 008 fields is NOT repeatable, so I think I will keep an "Add/Replace 008" option as the current menu.
Thanks for quick suggestion. ^^

[Simon Mai (simonmai)]

The new updated branch:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/simonmai/multiple_006_007_fields_marc_editor
Thanks,
Simon.

[Mike Rylander (mrylander)]

Simon,

What is the purpose of using CreateMARCTextbox for the tag and indicator fields? (Note: indicators don't exist for control fields in MARC -- the createLabel calls are really just visual placeholders.) It seems like the changes to the menu labels and the conditional added to createControlField() should be enough to accomplish your goal, no?

[Simon Mai (simonmai)]

Hi Mike,
I used CreateMARCTextbox for the tag field for this reason: Be able to remove the row (006/007 fields)
    To delete a row, we need to be able to click (select the tag field of that row), right click, and press Remove Row in drop-down menu as the way we're using to remove any data fields. If I still use createLabel for this tag, do I have any other ways to remove this row?

About indicator fields, you're right. I should keep the createLabel for them, since those indicators don't exist for control fields.
I will change the code a little bit. Thanks for your suggestion.

[Simon Mai (simonmai)]

I updated the code at:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/simonmai/multiple_006_007_fields_marc_editor
Thanks for testing,
Simon.

[Christine Morgan (cmorgan-z)]

Tested in Master in two different sandboxes. The patch did not work as described. I could not add an additional 007 or 006 and the existing field was blanked. I was not able to edit the 008 field either. I also did not have the new field drop down functionality that came in with 2.6, so perhaps this patch needs to be rewritten to incorporate that.

[Mike Rylander (mrylander)]

Thanks for testing, Christine. Removing pullrequest and marking incomplete for now.

[Jane Sandberg (sandbergja)]

A note that it's possible to add as many 006s and 007s as you want in the Web client in Evergreen 3.1.

[Andrea Neiman (aneiman)]

Marking won't fix on the basis of Jane's comment #12