These recommendations are intended to apply across all institutions, except for cases where a library does not use some of the subject headings types (sm, sc, etc.) but doesn't remove the fields as they catalog. In those cases, LUIS will continue not to display the headings with those indicators.

• For the 1xx: the "Author, etc." is a compromise label agreed upon by the Format Integration Task Force. It has the mnemonic value of beginning with A, like the "A=" for author searches, and it covers all types of authorship with the "etc."
• Include 245 |c and 260 |c in Brief to enhance the odds of having a fairly complete citation display.
• Relabel all 246 as ALTERNATE TITLE(S), and include display constants.
• We relabeled 362 ISSUED as PUBLISHING HISTORY. 780/5 are also relabeled as PUBLISHING HISTORY. As all tags with the same label will display together, these tags will now be neighbors up high in the record.
• Series: We have grouped all the 4xx and 8xx series fields together in the 4xx position on the record. We kept debating whether the 490 with 1st indicator 1 should display in the public view, and we decided to leave them in for now. Please look at the Books Review for further detail and rationale regarding the 490 1.
• We added the |x to several displays, so the ISSN will appear. Is this helpful or annoying?
• For cross-institution consistency, we altered all ADDED SERIES and ADDED BIBLIOGRAPHIC SERIES labels to SERIES.
• Notes: Some specialized note fields have been relabeled with the generic NOTES. This practice frees up labels needed for cross-format use and makes the labels for those tags more consistent across formats. One snag: All tags with the same label must display in the same "chunk". We can reorder tags within the same label (e.g., 508, 536, 535, 518) but we cannot split the label (e.g., NOTES, SUMMARY, NOTES). Will this increased use of NOTES cause less or more confusion for our patrons, because it will separate similar information on records for the sake of consistency across formats? Please look at the Books Review for further detail.
• Language: the 546 field with the label LANGUAGE has been added to all formats.
• The controversial issue of whether plain 500 should be keyword-indexed reared its head again. The Task Force did not see sufficient need to alter the current practice (plain 500 **NOT** keyword-indexed) within the scope of this project. If we wish to keyword-index some (but not all) of the plain 500 fields, the issue should be considered outside of the Format Integration project.
• Subjects: The instruction to "type" has been removed from the subject headings labels, both to shorten the length and because WebLUIS users are clicking rather than typing. We discovered the occasional use of "subjects,general (type sl=)". We recommend changing all of these to the simple (s=).
• We are adding the |v to the public display of the LC subject heading fields, in anticipation of LC implementing use of the |v soon.
• The use of the 653 for uncontrolled vocabularies of any sort was suggested for the Visual Materials format, with the label INDEX TERMS. However, if an tag is indexed in *any* format, it must be indexed in *every* format. A group may wish to investigate, with FCLA, the status of 653s in all formats and all databases before deciding their fate.
• RELATED MATERIALS as a label is intended to cover entries which are connected in a variety of ways to the title in hand. We hoped to be able to distinguish 7xx fields with second indicator 2, Analytical entries, with the label OTHER AUTHORS or TITLES, and use the label RELATED MATERIALS for all other 7xxs. This idea was based upon the assumption that the second indicator 2s represented, as intended, works contained within the item at hand while all other 7xxs represented works in some different relationship to the item. This is probably not practical based upon a quick check of the databases and past inconsistent usage of indicators. This is doubly unfortunate as we'd hoped in some future life to propose converting 740s to 246s based upon indicators but this will probably not be possible.
• We propose relabeling 780 and 785 as PUBLISHING HISTORY, and using display constants as coded. These tags will display immediately after the 3xx tags.
• 856: We are contemplating the use of display constants for first ind 7 and second ind 0, 1, and 2 as recommended by LC. See further description in the Computer Files format recommendation. The Task Force is recommending that all 856 subfields (except |x, nonpublic note) display and be keyword-indexed. Currently, LUIS can be confused by unusual uses of subfields. And LUIS is not converting the dots within URLs to spaces so the elements can be indexed as keywords. (If you now search for "k856=gov" you'll retrieve a record with a URL that contains "/gov/" but not one that contains "www.epa.gov/") We also see many 856 fields containing more text characters than the display length. These display oddities are being reported to FCLA as they are discovered.
• Cosmetic changes across all tags include:
  • We removed |h from all fields except 130, 240, and 245. In all formats, in many fields, the subfield h was at one time intended to carry a media qualifier. This practice has been outdated for some time and the subfield h should be used only in the 245. This would be an opportunity to stop displaying the qualifier in all entries except the 240 and 245. We except the 240 because of the music practice for many years of having the subfield h in the 240 in lieu of the 245.
  • We removed all the blank lines between fields. (Before you argue, look at some WebLUIS displays!)
  • We have made all fields repeatable except 1xx, 240, 243, 245, 250, and 260.

How will records display if they are coded for more than one format?
The tags/labels appropriate for the primary format will display. If a tag is labeled differently among formats (which we've tried to minimalize), the label of the primary format will display. Ideally, if a tag used in a multi-format record is not coded to display in the primary format, LUIS would extract and display the label used by the secondary format. However, this request may not be programmable.