Review and revise export of MARCXML for resources

Description

Revised mapping document is attached. Two items in red may require further review, but are included as the current thinking on this.

Subtasks:

Static changes to Leader
Fix Duplicate "040" tags
Agent links should get their own 700 tags
245 tag changes: Set ind1 correctly based on creator
245 tag: handle dates correctly
300 tag changes: Extents: 300 tag for each extent, handle extent #'s and translations
Note changes: 351, 524, 544, 561 tags
Agent-Family: Use value of qualifier in $c if agent_type: agent_family
Output Marc fields in numerical order (ANW-383)
Support excluding unpublished output (ANW-376)
Creator tags (100 for first, 700); Punctuation rules (ANW-174)
Repeated fields should not be concatenated (ANW-655)

Git Branches:

-> master
-----> ANW-639 (Parent MARCXML JT)
======== leader fix
----------> ANW-144 (duplicate 040 tag fix)
----------> ANW-146 (creators going into a single 700 fix)
=========== agent-family has qualifier in $c fix
--------------> ANW-174 (trailing punctuation in 700 tags)
======== set ind1 on 245 tag based on presence of creator
======== set bulk and inclusive dates correctly in 245 tag
======== handle extents: number in $a, translation in $f
======== note tag changes for 351, 524, 544, 561
--------------> ANW-383 (write out MARCXML with tags in numerical order)
--------------> ANW-376 (option to include/exclude unpublished notes and agents in MARCXML) (merged )

Activity

Show:
Christine Di Bella
March 9, 2018, 6:46 PM

Main issue is to implement the new mapping - most of the linked issues reflect things that need to be done to improve or resolve bugs in exporting MARCXML overall.

Manny Rodriguez
March 14, 2018, 9:22 PM

Punctuation rules from spreadsheet:

The first creator listed becomes the 100 field. All others are treated as 700 (see below). Punctuation rules explained below reflect what is wanted for

"Punctuation rules:

If subfield $c is present, the value of the preceding subfield must end in a comma.
If subfield $d is present, the value of the preceding subfield must end in a comma.
If subfield $e is present, the value of the preceding subfield must end in a comma.
The value of subfield q must be enclosed in parentheses.
The value of the final subfield must end in a period.

Order rules: For family names (applies to 100, 600, 700), output in this order: $a family name : $d dates : $c qualifier, $e relator term. [Better to manually insert parentheses, after mapping]

"Punctuation rules:

If subfield $d is present, the value of the preceding subfield must end in a colon.
If subfield $c is present, the value of the preceding subfield must end in a colon.
If subfield $e is present, the value of the preceding subfield must end in a comma.

The value of the final subfield must end in a period."

Done

Assignee

Manny Rodriguez

Reporter

Christine Di Bella

Priority

Major