search

lcnetdev / bibframe2marc

XSLT application to generate MARCXML from BIBFRAME RDF/XML
Creative Commons Zero v1.0 Universal
15 stars 5 forks source link

former frequencies placed in 310 instead of 321 fields #24

Open jodiw01 opened 2 months ago

jodiw01 commented 2 months ago

Former frequencies should be placed in the MARC 321 field, but bibframe2marc is placing them in the 310 field.

Examples: 001 11138862 https://id.loc.gov/resources/instances/11138862.html

Output has: 310 \$aweekly$0http://id.loc.gov/vocabulary/frequencies/wkl 310 \$airregular$0http://id.loc.gov/vocabulary/frequencies/irr 310 \$aWeekly (except one week in Jan., Feb., Apr., June, July, Sept., and Dec.)$b<June 11, 2018-> 310 \$aWeekly (except one issue in Jan. and one issue in Aug.)$bSept. 1929- 310 \$aWeekly (except for one issue in Jan., Feb., Mar., July and Aug.)$b<Dec. 2009-> 310 \$aWeekly (except one week in Mar., June, Aug., and Dec.)$b<July 14, 2014->

Should have: 310 \$aweekly$0http://id.loc.gov/vocabulary/frequencies/wkl 310 \$airregular$0http://id.loc.gov/vocabulary/frequencies/irr 310 \$aWeekly (except one week in Jan., Feb., Apr., June, July, Sept., and Dec.)$b<June 11, 2018-> 321 \$aWeekly (except one issue in Jan. and one issue in Aug.)$bSept. 1929- 321 \$aWeekly (except for one issue in Jan., Feb., Mar., July and Aug.)$b<Dec. 2009-> 321 \$aWeekly (except one week in Mar., June, Aug., and Dec.)$b<July 14, 2014->

BF data for this title includes appropriate bf:status coding to differentiate between current and former frequencies