[DCRM-L] [rules] Fwd: [MARC] MAC papers and agenda for ALA 2020 Midwinter Conference available online

Tue Jan 7 08:51:38 MST 2020

Hi, Ted,

MARC 21 bibliographic records include Work, Expression, and Manifestation elements in order to achieve a multilevel (WEM) description of a specific manifestation (provider neutral records are an exception to this in that they represent multiple manifestations on the same record). Separate descriptions for works, expressions, manifestations, and items are possible in a linked data environment (among other encoding implementations), but cannot be meaningfully accommodated in the current MARC 21 bibliographic, holdings, and authority environment. So while it is true that a bib record represents a manifestation, it contains Work and Expression elements. From a WEMI modeling perspective, MARC records are and have always been a complicated mess, and this is one of the reasons why BIBFRAME to MARC conversion is so challenging. The addition of a field for manifestation statement will not affect this one way or the other.

Discussion Paper No. 2020-DP06: Defining a New Field for Manifestation Statements<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fwww.loc.gov-252Fmarc-252Fmac-252F2020-252F2020-2Ddp06.html-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C1-257C637138727956466830-26sdata-3Dvly5x0SNQQxY3dYzejLP9-252FK93GybaoItsEdqA8xFFkI-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=SstAcgIYbYxQuRFwoVNc7uKGkgUjheRTFouVDYMofKE&e=> was brought by the MARC/RDA Working Group<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.loc.gov-252Fmarc-252Fmac-252FMARC-2DRDA-5FWorking-5FGroup.html-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C1-257C637138727956476822-26sdata-3DNFIsDad2d3SyA5lHhl2YdWViIkr7yLQeS9mE2-252FdFG6Y-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=b_0hXJJa0_u0KNZaTj8YatdOrD98mGY10SuPGVUE3DU&e=> in order to accommodate the new beta RDA Toolkit element, Manifestation: manifestation statement and its sub types in MARC 21. It has no direct* connection with the 386 field, which was implemented in order to accommodate certain types of subject data about a work that are not appropriate for inclusion in LCGFT (cf. MARC proposal No. 2013-06<https://www.loc.gov/marc/marbi/2013/2013-06.html>).

Manifestation statements are defined by the LRM<https://www.ifla.org/files/assets/cataloguing/frbr-lrm/ifla-lrm-august-2017_rev201712.pdf> as “A statement appearing in exemplars of the manifestation and deemed to be significant for users to understand how the resource represents itself,” consistent with the IFLA Statement of Cataloguing Principles (ICP) 2.3<https://www.ifla.org/files/assets/cataloguing/icp/icp_2016-en.pdf>, “A description should represent a resource as it appears.” While an ms may contain information that pertains to work and expression descriptions, as a straight transcription it can only be a Manifestation element.

In addition to the early printed resource use case I mentioned in my first email, other use cases for the addition of a field for ms include the use of scanned data for libraries lacking staff resources for even basic description or language expertise. Another use case sometimes cited are national libraries inundated by vast quantities of electronic legal deposits.

Since the LRM consolidates and supersedes FRBR, FRAD, and FRSAD, it may be helpful to think about an LRM framework, rather than a FRBR framework.

Best,
Honor

*The current discussion paper is related to the 386 implementation in that both are part of the larger project to adapt traditional bibliographic description and bibliographic exchange formats for current technologies, including the semantic web, but that is true for the vast majority of recent MARC 21 development.

From: DCRM-L <dcrm-l-bounces at lib.byu.edu> On Behalf Of Gemberling, Ted P
Sent: Monday, January 6, 2020 7:29 PM
To: DCRM Users' Group <dcrm-l at lib.byu.edu>
Subject: Re: [DCRM-L] [rules] Fwd: [MARC] MAC papers and agenda for ALA 2020 Midwinter Conference available online

I remember when I encountered this idea several years ago while reading about LRM it seemed kind of bizarre. I don’t mean to put down efforts you put into developing the concept, but it seemed counterintuitive in a FRBR framework. Didn’t we agree that what we normally call bib records represent Manifestations? I thought we were going to create Expression and Work records for Expressions and Works.

It seems this whole concept of Manifestation Statement suggests that bib records are being turned into Work and Expression records. If so, it will be very difficult for catalogers, maybe especially beginning catalogers, to understand bibliographic records. When you are looking at a record, what part is “manifestation” and what part is “work” or “expression”?

Could this have some connection to the recent move to add things like 386 (Creator/contributor characteristics) to bib records? This is importing elements of authority records into bib records. Bib records may be becoming a complicated mess.

Just my two cents. I’ve been out of touch with cataloging theory somewhat for a couple of years, so I could be off base.

Ted Gemberling
UAB Libraries

From: DCRM-L <dcrm-l-bounces at lib.byu.edu<mailto:dcrm-l-bounces at lib.byu.edu>> On Behalf Of Moody, Honor M.
Sent: Monday, January 6, 2020 2:32 PM
To: DCRM Users' Group <dcrm-l at lib.byu.edu<mailto:dcrm-l at lib.byu.edu>>
Subject: Re: [DCRM-L] [rules] Fwd: [MARC] MAC papers and agenda for ALA 2020 Midwinter Conference available online

Inline comments in blue. I’m abbreviating manifestation statement as ms, because my life is too short to keep typing it out (sorry, not sorry to all of you who automatically expand it to manuscript in your heads).

From: DCRM-L <dcrm-l-bounces at lib.byu.edu<mailto:dcrm-l-bounces at lib.byu.edu>> On Behalf Of Lapka, Francis
Sent: Monday, January 6, 2020 1:10 PM
To: DCRM Users' Group <dcrm-l at lib.byu.edu<mailto:dcrm-l at lib.byu.edu>>
Subject: Re: [DCRM-L] [rules] Fwd: [MARC] MAC papers and agenda for ALA 2020 Midwinter Conference available online

Thanks for bringing this to our attention Honor.

While I understand your skepticism about meaningful implementation of such a field, we might as well make the new field as well-designed as possible. Responding to your points:

  1.  As this is a transcription field, I think it would be much more useful (to catalogers) to place it in the vicinity of other transcriptions. Why couldn’t we use 280 or 281 (the “etc.” in “Edition, Imprint, Etc.”)?
As I understand it, the rationale is that only the 3xx, 5xx, and 841-88x blocks were considered, as the other blocks are defined for specific descriptive areas, and an ms can have data corresponding to multiple areas. No additional rationale is given for the choice of 841-88x over the other two blocks.

  1.  I agree that the order of subfields should not be prescribed. The examples (2 and 3) show the subfields in alphabetical order, but does the proposal say that they have to be recorded that way? I didn’t see such a prescription, though I skimmed it quickly.
Apparently you weren’t the only one skimming (or at least not reading as closely as one should). The options for subfield order have to do with what order the ms sub-types go in (i.e., should $j be ms manufacture statement or ms copyright statement), and don’t seem to be related to a prescribed order or recordings (despite the examples usage). I apologize for any confusion. I’m not sure that I care one way or another about these subfield orders, as long as I can use them in the order appropriate for ms being transcribed.

  1.  + a bunch to your request for subfield 2, for recording transcription scheme.

It might be nice to offer alternative examples for a complex manifestation statement, following DCRM(B) transcription guidelines, and using a $2dcrmb alongside an example providing a more formal descriptive bibliography transcription that included marks for line breaks, etc. I think we could suggest a subfield 2 definition that allowed for description convention or transcription scheme to be used

I started to play around with this, and while I might enjoy spending the whole day playing with the transcription of mss for early printed resources (interesting thought exercise, more complicated than it might seem at first), I have deadlines and other tasks that need to get done.

If any of you were interested in giving it a whirl, please let me know or just post examples (particularly fun times could be had doing state variation, and while I can’t think of any good examples off the top of my head, I suspect that more than one person on this list could).

Francis

Francis Lapka
Senior Catalogue Librarian
Department of Rare Books and Manuscripts
Yale Center for British Art
203-432-9672  ·  francis.lapka at yale.edu<mailto:francis.lapka at yale.edu>

From: DCRM-L <dcrm-l-bounces at lib.byu.edu<mailto:dcrm-l-bounces at lib.byu.edu>> On Behalf Of Moody, Honor M.
Sent: Sunday, January 5, 2020 9:00 PM
To: DCRM Users' Group <dcrm-l at lib.byu.edu<mailto:dcrm-l at lib.byu.edu>>
Subject: [DCRM-L] FW: [rules] Fwd: [MARC] MAC papers and agenda for ALA 2020 Midwinter Conference available online

Dear DCRM colleagues,

CC:DA has been asked to comment on the discussion papers and proposals that will be discussed by the MARC Advisory Committee (MAC) at ALA Midwinter. All are now linked from the agenda<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fwww.loc.gov-252Fmarc-252Fmac-252Fmw2020-5Fage.html-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C1-257C637138727956456829-26sdata-3D2hykRXchsdmCcXxHWngtsGGA8Qf7UwTt3CDy4DSLRsM-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=MuZ94KDZwAzdiXUV_OlpEBW5hASCyETFKvFNJYy7zQ4&e=>.

Several were developed by NDMSO, primarily to facilitate data conversion between MARC and BIBFRAME.

Discussion Paper No. 2020-DP06: Defining a New Field for Manifestation Statements<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fwww.loc.gov-252Fmarc-252Fmac-252F2020-252F2020-2Ddp06.html-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C1-257C637138727956466830-26sdata-3Dvly5x0SNQQxY3dYzejLP9-252FK93GybaoItsEdqA8xFFkI-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=SstAcgIYbYxQuRFwoVNc7uKGkgUjheRTFouVDYMofKE&e=> from the MARC/RDA Working Group<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.loc.gov-252Fmarc-252Fmac-252FMARC-2DRDA-5FWorking-5FGroup.html-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C1-257C637138727956476822-26sdata-3DNFIsDad2d3SyA5lHhl2YdWViIkr7yLQeS9mE2-252FdFG6Y-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=b_0hXJJa0_u0KNZaTj8YatdOrD98mGY10SuPGVUE3DU&e=> will be of particular interest, as “the exact transcription of statements for early printed resources” is identified as a use case for the new field. The manifestation statement concept was introduced as a Manifestation attribute in the LRM<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.ifla.org-252Ffiles-252Fassets-252Fcataloguing-252Ffrbr-2Dlrm-252Fifla-2Dlrm-2Daugust-2D2017-5Frev201712.pdf-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C1-257C637138727956476822-26sdata-3Dc6tC9C2U4kcV9FD6MeRfi4xSKo5jPZCDHL1qBV5f2mA-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=553cKxy6YB6eB3Px4K1QlkfHCqLunWeaHct2McQnhwE&e=>, and is implemented in the beta RDA Toolkit along with 13 narrower elements<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fbeta.rdatoolkit.org-252Fen-2DUS-5Fala-2D6f241594-2D3b46-2D3eb3-2Da053-2D1ecec038fa34-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C1-257C637138727956486822-26sdata-3DrDGzygqLyp7KDyBbyvIVXmehtFfk3fpvVE9cNyrp-252Bc4-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=HArC8CyZHOxHEYQT7GfKCPB5ZyScpOJIg7VA1-eUzEs&e=>. The discussion paper explores the possibility of a new MARC field 881, defining $a for manifestation statement, and $b-h, $j-o for the 13 narrower elements.

I offer the following initial responses to spark discussion, to be wrapped up by January 13th.

  1.  It is not clear to me that a MARC field is needed or desirable for recording a manifestation statement. I am not persuaded that any new fields would be meaningfully implemented in either front or back end library systems, so a 500 note might be a more realistic approach.
  2.  Any prescribed subfield order will render the subfield breakout less useful for chunking out a continuous manifestation statement (the whole point is basically that resources don’t have a uniform layout and don’t play well with ISBD order for descriptive elements).
  3.  If implemented, please define a subfield 2 for this field. Given that beta RDA Toolkit allows for the use of any transcription guidelines or scheme, the use case of “exact transcription of statements for early printed resources,” especially the identification of different states distinguished by capitalization or placement of text, cannot be achieved without some way to record the transcription guidelines/scheme.

Barring any discussion from the list, I do not plan to respond to the other discussion papers/proposals.

Best,
Honor

Honor Moody
Metadata Creation Manager
Harvard Library Information and Technical Services
honor_moody at harvard.edu<mailto:honor_moody at harvard.edu>

From: rules-request at lists.ala.org<mailto:rules-request at lists.ala.org> <rules-request at lists.ala.org<mailto:rules-request at lists.ala.org>> On Behalf Of Myers, John
Sent: Thursday, January 2, 2020 10:45 AM
To: rules at lists.ala.org<mailto:rules at lists.ala.org>
Subject: [rules] Fwd: [MARC] MAC papers and agenda for ALA 2020 Midwinter Conference available online

Dear colleagues on CC:DA, attached is the notice for the MARC papers for Midwinter, at present. As the original message from LC mentions, there are another two papers forthcoming.

Please review and provide feedback to me by January 15.

You are free to comment on any paper. Some papers of particular interest to CC:DA --

2020-DP01 discusses a major overhaul of field 856 -- I am very interested in a broad set of perspectives on the proposed options
2020-DP03 discusses places to distinctly record RDA elements for illustrative and sound content (new subfields in field 340)
2020-DP04 discusses places to distinctly record RDA elements for aspect ratio and motion technique (new subfields in field 345)
2020-DP05 discusses reinstatement of field 241 to record transliterated title

John Myers, Catalog & Metadata Librarian
Schaffer Library, Union College
Schenectady NY 12308

518-388-6623
myersj at union.edu<mailto:myersj at union.edu>
pronouns: he/him/his

---------- Forwarded message ---------
From: NDMSO <ndmso at loc.gov<mailto:ndmso at loc.gov>>
Date: Fri, Dec 20, 2019 at 4:36 PM
Subject: [MARC] MAC papers and agenda for ALA 2020 Midwinter Conference available online
To: <MARC at listserv.loc.gov<mailto:MARC at listserv.loc.gov>>

The MAC ALA 2020 Midwinter Conference agenda is available at:
http://www.loc.gov/marc/mac/mw2020_age.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5Fmw2020-2D5Fage.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DRk87RwQD3o3SUf6QJL59T8IwCzhZAcpS0iJaEYfvrWg-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956496813-26sdata-3D5H60c7htgBbtXrcvsfCT4nuyhO7sjAA5bKQMeBZIVQM-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=ia3Hz3nUjQOtk1l5LcpLUTKO1HN7Qbv1ry9kVS0dfik&e=>

Please note that 2 discussion papers are pending finalization,
with an expected publication date of January 3.

PROPOSALS

Proposal No. 2020-01: Defining a New Indicator Value for
Human-generated Content in Field 883 of the MARC 21 formats
(http://www.loc.gov/marc/mac/2020/2020-01.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5F2020-5F2020-2D2D01.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DTzNZ0plfPTd8MnHKLyRaOUVAU-2D6OL1ehRKiaCQjWXNE-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956496813-26sdata-3DY-252FVN2nuzT2gpKRzN-252BCanbL-252F9f94hAqb3-252BCFXD7a4mmQ-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=4QACowwkG4MvVqx6Rg8Qkl8i3f_sFuwTceZ01ZTnrhk&e=>)

Proposal No. 2020-02: Adding Subfield $0 to Fields 310 and 321
in the MARC 21 Bibliographic Format
(http://www.loc.gov/marc/mac/2020/2020-02.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5F2020-5F2020-2D2D02.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DV-5FYdixfOsyxNIMWuijv-2DxO1DgvhEHHbRuFpl77Wwibw-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956506808-26sdata-3D69EYO2nYO2jiICNLxzgYlnLqdV6lr7uKljja4A9VSSA-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=ahn30A2pF00XuGnFGmfmnwmPANCTwOZiQ0tDlvISYR0&e=>)

DISCUSSION PAPERS

Discussion Paper No. 2020-DP01: Modernization or Replacement
of Field 856 in the MARC 21 Formats
(http://www.loc.gov/marc/mac/2020/2020-dp01.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5F2020-5F2020-2D2Ddp01.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DrvesG5HaJYvh5-5FE5H6RKhSPWjCoaYgiYHJfGc2LJNgs-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956516799-26sdata-3DgQBQ8te-252FrlHL31yG2jm93Xc-252FnNkrfF6W-252BG9lkORIMZc-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=E3imWgyD3uUi2eywL5xuJGAvHDHgqGuttI5_0zvmns0&e=>)

Discussion Paper No. 2020-DP02: Adding Subfield $0 to Fields 504
and 525 of the MARC 21 Bibliographic Format
(http://www.loc.gov/marc/mac/2020/2020-dp02.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5F2020-5F2020-2D2Ddp02.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DvIcDt1VERsHBh-5FYdP61E9n7ubn0GE0BDkfFoP7WwBjg-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956526792-26sdata-3DeQXuAaXmH6muT-252BAEtNNirEm0Ki6XoTlrIEHFBmhgEDU-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=pxPaeb1OR2fj-kzAPOOZHq4SduG1QMY7Q-7wGnKbnWI&e=>)

Discussion Paper No. 2020-DP03: Defining New Subfields in Field
340 to Record Illustrative Content and Sound Content in the
MARC 21 Bibliographic Format
(http://www.loc.gov/marc/mac/2020/2020-dp03.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5F2020-5F2020-2D2Ddp03.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DO2n-2D0c6vJ-2DTjcs9JYuYZIOX-5FzO0ocrhREL14gWNZTbs-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956526792-26sdata-3DEpv2dlThmgLcacUWk5SsVEV-252FxcgZOWrYWjAmcU0NQ-252F4-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=Jaijqqe8lN7v057BgHYPykRcBhjgZPXrgThdKQ-cs-k&e=>)

Discussion Paper No. 2020-DP04: Renaming Field 345 and Defining
New Subfields for Aspect Ratio and Motion Technique in the
MARC 21 Bibliographic Format
(http://www.loc.gov/marc/mac/2020/2020-dp04.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5F2020-5F2020-2D2Ddp04.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DpwS8-2DuTUGoXWPpf-5FGEpB-5FoeTxADC42c2YXqeI-5Fnjdyg-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956536805-26sdata-3DUlpJHIHyVQDounxkX6EgNaAhEqTWJoCAaf8AqIXnqis-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=VVPcAhfR_SXI7ULSlBzfA7Vb6LEC8jv7Tj2X0IRsp6M&e=>)

Discussion Paper No. 2020-DP05: Reinstatement of Field 241
in the MARC 21 Bibliographic Format
(http://www.loc.gov/marc/mac/2020/2020-dp05.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam05.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttp-2D3A-5F-5Fwww.loc.gov-5Fmarc-5Fmac-5F2020-5F2020-2D2Ddp05.html-2526d-253DDwMFaQ-2526c-253DWO-2DRGvefibhHBZq3fL85hQ-2526r-253DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk-2526m-253D9N3Ht-2DAF336Uglv1-2DYAq51rRoFYC5STTBj0JWpYqgv4-2526s-253DA4DGFtuINUNJHjrTMrRyaUxKTuu7CPSlmfVEutk5GAE-2526e-253D-26data-3D02-257C01-257Cfrancis.lapka-2540yale.edu-257C3994218519e34915651008d7924c1e1c-257Cdd8cbebb21394df8b4114e3e87abeb5c-257C0-257C0-257C637138727956546789-26sdata-3DCH-252F8543Zu1XgX6CSgIo8bXnOlw2zW4G5c6Mh-252FzFARzs-253D-26reserved-3D0&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=gfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk&m=9LRjGhgYexpVTlBLuw1DxqQZsJU2HJ8yf9qeWzY7gPY&s=q_cO86Nw8Z_H0m1bxdSqvzYq64DOGHAfjjtE1s9yg1M&e=>)

-----------------------------------------------
Network Development and MARC Standards Office
101 Independence Ave., S.E.
Washington, DC 20540-4402 U.S.A.
TEL: +1-202-707-6237
FAX: +1-202-707-0115
NET: [log in to unmask]
-----------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20200107/f0e01182/attachment-0001.html>