Home > Bibliographic Services Division > Information for Licensees > CatfilePlus and Serfile in XML |
XML Elements descriptions for elements defined in NLMCatalogRecord.dtd (drawing on NLMSharedcatcit.dtd and NLMCommon.dtd) and used in CatfilePlus (in XML) and Serfile (in XML)
THE ELEMENTS defined in or referenced by the NLMCatalogRecord DTD:
The elements are presented in this document in the order in which they appear in the XML versions of CatfilePlus and Serfile. The elements are defined in the NLMCatalogRecord.DTD, which in turn references elements in NLMSharedcatcit.dtd and NLMCommon.dtd.
Together, these three interconnected DTDs produce a file of records which NLMCatalogRecord.DTD identifies as "NLMCatalogRecordSet"
Any NLMCatalogRecordSet may contain zero, one or many individual bibliographic records, with each record encapsulated in an occurrence of <NLMCatalogRecord> AND/OR one (and only one) occurrence of an "umbrella" record, DeleteCatalogRecord, which lists one or more deleted records, by record identifier only.
The contents of NLMCatalogRecordSet:
Notification of the delete of (a) previously issued record(s) requires a single occurrence of the top-level XML element, <DeleteCatalogRecord>, which will contain occurrence(s) of the <NLMUniqueID> element of record(s) being deleted and no other sub-elements.
An alphabetical list of all element names is at http://www.nlm.nih.gov/bsd/licensee/catrecordxml_elementlist_alphabetical
Within each of the 47 numbered sections, the following information is listed, if appropriate:
About Attributes:
While a brief description of the attributes for each element is given with the element, additional information about the attributes will be found in the separate document on attributes, where the values are also listed.
"CompleteYN" attribute:
The attribute "CompleteYN" is used only once in NLMCatalogRecord, in <AuthorList>. However, in every case (including <AuthorList>) where a list element is defined to group multiple occurrences of like elements, the list is considered to be complete.
About the Examples(s):
In most cases, multiple examples are given within the Example(s) section. If multiple occurrences of the same element occur together, without intervening blank lines, the intent is to show a situation which is possible with repeating occurrences on one record. Where there are blank lines between occurrences of the same element, the examples are drawn from multiple records. That does not necessarily preclude these values from occurring on the same record under other circumstances. If an element is not repeatable, this is explicitly stated.
About Elements:
An alphabetical list of all element names is at http://www.nlm.nih.gov/bsd/licensee/catrecordxml_elementlist_alphabetical.html
About the Character Set:
Information about the character set used in NLMCatalogRecordSet is at http://www.nlm.nih.gov/bsd/licensee/catrecordxml_characterset.html
TOP ELEMENT for new or updated Catalog Records: <NLMCatalogRecord>
Additional ("child") elements: See 1-47, below.
Attributes:
with <NLMCatalogRecord>: Owner, Status
<NLMCatalogRecord> is the top-level element which encloses each record.
One <NLMCatalogRecord> is derived from one new or updated LocatorPlus record.
This element itself contains no data but has two attributes, Owner and Status.
The Owner attribute at this top-level element indicates the organization that is responsible for the creation and maintenance of the bibliographic record in LocatorPlus. If responsibility is shared between NLM and any other organization(s), Owner will be set to NLM and the other organizations will be identified in <CollaborativePartnerDate>.
The Status attribute indicates the current processing or cataloging status of the resource reflected by this record.
Example(s): See sample set, or Examples of specific elements below.
MARC 21 source: Each XML record corresponds to one MARC 21 record in LocatorPlus.
The <NLMUniqueID> is the 7-9 digit alpha-numeric identifier used to uniquely identify every record in LocatorPlus and, as a consequence, also in NLMCatalogRecordSet.
This element is required and not repeatable within a single catalog record. However, as an XML element, it may be repeated within <DeleteCatalogRecord> when a list of deleted records is being supplied.
Example(s):
<NlmUniqueID>2436043R</NlmUniqueID>
<NlmUniqueID>18120320R</NlmUniqueID>
<NlmUniqueID>9600954</NlmUniqueID>
<NlmUniqueID>7900631A</NlmUniqueID>
<NlmUniqueID>100931012</NlmUniqueID>
MARC 21 source: Field 035 subfield $9 (local field in LocatorPlus). When LocatorPlus records are distributed in MARC 21 format, the data in <NLMUniqueID> appears in the 001 field.
Additional information/background:
For catalog records initiated in NLM's cataloging, acquisitions or serial record systems prior to Fall 1998, the <NLMUniqueID> may be 7 to 9 digits in length; the terminal digit may be numeric or the alphabetic characters "A" or "R".
Beginning with NLM's implementation of the LocatorPlus integrated library system in Fall 1998, each record initiated in or loaded from NLM or collaborative partner databases has an <NLMUniqueID> consisting of 9 numerics.
<NLMUniqueID> may be used to locate the bibliographic record in LocatorPlus at http://locatorplus.gov/ where the user can have access to NLM holdings and item information.
The <DateCreated> is the date the record was first entered into an NLM or collaborative partner database.
MARC 21 source: Field 008 bytes 00/05 (year has been expanded to 4 digits)
The <DateRevised> is a system-supplied date which identifies the most recent time a change was made to the record. There is no indication of what the change was or how significant. Only the latest revision date is given.
MARC 21 source: Field 005 bytes 00/07
The <DateAuthorized> is the date when NLM authorized the cataloging of this record.
MARC 21 source: Field 995 subfield $b (LocatorPlus local field)
Additional information/background:
<DateAuthorized> exists only for records which have been cataloged by NLM.
<DateCompleted> is the earliest of either:
1) the date when the record has been authorized by NLM, or
2) the date when it has been completed by a collaborative partner.
MARC 21 source: The earliest of Field 995 subfield $b or Field 995 subfield $d or Field 998 $b where $a contains "REL". (Fields 995 and 998 are LocatorPlus local fields).
Additional information/background:
<DateCompleted> exists only on records which have reached "completion" according to the standards (which vary) of at least one participating organization. Records with the <LocatorCitation> Status attribute value set to "In-Process records" or "Not-Our-Cataloging" are examples of records that do not have a <DateCompleted>.
<DateRevisedMajor> is an operator- or programmer-assigned date which identifies the most recent time a completed NLM cataloged record underwent revision other than global maintainance by the system. <DateRevisedMajor> is assigned for local tracking purposes. There is no indication of what the change was or how significant. Only the latest major revision date is given.
MARC 21 source: Field 995 subfield $d (LocatorPlus local field)
Additional information/background:
<DateRevisedMajor> is optional and cannot exist unless <DateAuthorized> also exists. When it exists, <DateRevisedMajor> must be equal to or later than <DateAuthorized>.
<CollaborativePartnerDate> indicates the date a collaborative partner last modified the record and changed its CollaborativeStatus. It exists on records which contain data contributed by one or more NLM collaborative partners.
The Owner attribute indicates which collaborative partner is associated with this <CollaborativePartnerDate>.
The CollaborativeStatus attribute indicates the most recent stage the record has reached in the partner's processing.workflow. The value "Other" is the default used when the CollaborativeStatus cannot be explicitly set to one of the other values.
Example(s):
<CollaborativePartnerDate Owner="HSR" CollaborativeStatus="In-House-Review">20030312</CollaborativePartnerDate>
<CollaborativePartnerDate Owner="KIE" CollaborativeStatus="Released">20010409</CollaborativePartnerDate>
<CollaborativePartnerDate Owner="NASA" CollaborativeStatus="Create">20030330</CollaborativePartnerDate>
MARC 21 source: Field 998 (LocatorPlus local field) subfields $a and $b.
Additional information/background:
Multiple collaborative partners may be associated with a single record, regardless of whether the record is owned by and/or cataloged by NLM. <CollaborativePartnerDate> is repeated for each collaborative partner associated with a record.
<TitleMain> contains the title and statement of responsibility information, as they appear on the material. If the title proper is in a non-English language, the <TitleMain> will contain the title in that language; if the language is non-roman (such as Chinese or Japanese), it will appear in a romanized form of that language. In most cases, punctuation is retained from the LocatorPlus record.
The <Title> element contains the title including name and/or numbering of parts; <OtherInformation> contains the statement of responsibility (authorship information).
MARC 21 source: Field 245
<MedlineTA> contains the NLM standard abbreviation for the title of a journal cited in NLM's online services. Each journal title indexed by NLM is assigned a unique title abbreviation.
See the NLM Fact Sheet "Construction of National Library of Medicine Title Abbreviations" at http://www.nlm.nih.gov/pubs/factsheets/constructitle.html for more information on the rules currently used by the National Library of Medicine (NLM) to construct title abbreviations for journals indexed by NLM.
Example(s):
<MedlineTA>20 Century Br Hist</MedlineTA>
<MedlineTA>Allg Wien Med Ztg</MedlineTA>
<MedlineTA>ASA Audio Rev Anesthesiol</MedlineTA>
<MedlineTA>JAMA</MedlineTA>
<MedlineTA>Tuberculosis (Paris)</MedlineTA>
<MedlineTA>VA Annu Rep Act Veterans Adm Med Sch Assist Health Manpower Train Act 1972</MedlineTA>
MARC 21 source: Field 210 (when Indicator 2=0 and $2=DNLM)
<TitleOther> contains series information and titles other than the <TitleMain> and for indexed journals, the <MedlineTA>.
MARC 21 source: Fields 130, various 2XX, 4XX, 7XX and 8XX title and series fields, EXCEPT Field 245 and those occurrences of Field 210 which are <MedlineTA>.
Personal and collective (corporate) author names published with the article are found in <AuthorList>.
Every <AuthorList> for NLMCatalogRecord is considered to be complete (CompleteYN="Y" in all cases), regardless of the number of <Author> elements present.
MARC 21 source: Fields 1XX and 7XX (various)
Additional information/background:
The contents of the <Initials> element is constructed from the data going to the <Forename> element. An individual initial is found at the beginning of the <Forename> string or following a break. A break is a space or hyphen. Only capital letters in <Forename> are candidates for initials except for the letter following a hyphen. The letter following a hyphen is a candidate for an initial unless the string following the hyphen is 'ichi'. If <Forename> is only initials, there will be spaces between initials. Initial includes the following particles: de, do, da, du, del, dos, el-, le and el. All except 'el-' are followed by a space and are preceded by a space or are at the beginning of the name string. If found, all particles will be converted to lower case in <Initials>. If language is Bulgarian, Russian, Serbo-Croatian (Roman), or Ukrainian, then <Initial> may be a 2-4 character transliterated mixed-case initial.
<InvestigatorList> exists on NLMCatalogRecord citations created or maintained by one of NLM's collaborative partners, the National Aeronautics and Space Administration (NASA). It identifies the NASA-funded principal investigator(s) who conducted the research discussed in the work cited. An <Investigator> may or may not also be an <Author>.
Data appears in a format similar to that used for author names in <AuthorList>, including <LastName>, <ForeName>, <Suffix>, and <Initials>. The <Investigator> element also contains <Affiliation>, the organization that the researcher was affiliated with at the time the work was written. Unlike <Affiliation> associated with <Abstract>, this affiliation does not include detailed address information.
Like <AuthorList>, <InvestigatorList> is always complete. Unlike <AuthorList>, however, it has no attribute to indicate completeness.
MARC 21 source: Field 700 when subfield $e contains "Investigator". NASA use only.
<ResourceInfo> contains data related to the format of the material reflected in this <NLMCatalogRecord>. <ResourceInfo> and the first two elements within it, <TypeOfResource> and <Issuance>, must occur one and only once. <ResourceUnit> is required and repeatable; if multiple formats are described in one <NLMCatalogRecord>, <ResourceUnit> will be repeated to include all the appropriate formats.
<TypeOfResource> contains one of the following values: Book, Book Chapter, Collection (manuscript), Collection (print), Electronic Resource, Electronic Serial, Kit, Manuscript, Map, Mixed Material, Nonmusical Recording, Serial, Still Image, Three Dimensional Object, Undetermined, Visual Material
<Issuance> contains one of the following values: monographic, continuing
<ResourceUnit> contains one or more of the following values: aperture card, art original, art reproduction, comic strip, diorama, diskette, electronic resource (undifferentiated), filmstrip, flashcard, globe, graphic, kit, map, microfiche, microfilm, microform (undifferentiated), microopaque, microscope slide, model, motion picture, music, nonprojected graphic (undifferentiated), optical disc, picture, projected graphic (undifferentiated), realia, remote electronic resource, remote-sensing image, slide, sound recording, tactile material, technical drawing, text, toy, transparency, videorecording.
MARC 21 source: Leader bytes 06-07, various bytes of fixed fields 007 and 008
<PublicationTypeList> contains the list of <PublicationType>s associated with this record. Each <NLMCatalogRecord> citation may have no, one or multiple occurrences of <PublicationType>. <PublicationTypeList> is always complete; there is no attribute to indicate completeness.
The <PublicationType> values with their descriptions may be downloaded from http://www.nlm.nih.gov/mesh. The publication headings contain the value D in the Record Type (RY) field and the value 3 in the DescriptorName Form (DF) field.
For additional information on the use of MeSH Publication Types in NLM cataloged records, refer to http://www.nlm.nih.gov/tsd/cataloging/catmesh.html#PT%20FORM%20DIV.
MARC 21 source: Field 655, Field 659 (LocatorPlus local field), various bytes of fixed fields 007, 008
<GenreList> contains the list of <Genre>s associated with this record. Each <NLMCatalogRecord> citation may have no, one or multiple occurrences of <Genre>. <GenreList> is always complete; there is no attribute to indicate completeness.
The values in <Genre> are similar to <PublicationType> but are not Publication Types (PTs) in the MeSH vocabulary. Each occurrence of <Genre> contains one of the following values: autobiography, discography, drama, filmography, folktale, font, game, history, language instruction, law report or digest, legal article, loose-leaf, memoir, monographic series, newspaper, novel, numeric data, poetry, rehearsal, remote sensing image, reporting, short story, sound, speech, theses, treaty, web site.
MARC 21 source: Fixed fields 007 and 008 (various bytes) which do not correspond to values in <PublicationTypeList>
<ProjectedPublicationDate> gives the anticipated 2-digit year and 2-digit month of publication, as announced by the publisher. It exists only on records created at NLM at the pre-publication stage and is removed if/when NLM subsequently acquires and catalogs the material.
<Edition> contains information relating to the edition of the work.
<DatesOfSerialPublication> contains beginning and/or ending numeric, alphabetic and/or chronological designations of a serial.
<Frequency> contains information about the frequency of publication of a serial. While only one current frequency is allow, the element is repeated once for each former frequency.
MARC 21 source: Field 044 subfield $9 (LocatorPlus local subfield), various fixed field 008 bytes, Fields 250, 260, 263, 269 (LocatorPlus local field), 310, 321, 362
<Language> contains the three-letter MARC 21 code for the language associated with the text or sound tract. If the work is in multiple languages, this element is repeated for each language. If the language is unknown, <Language> may be coded "und", meaning "Undetermined".
The values in <Language> are found in the MARC Language Code list, Part II: Code Sequence at http://www.loc.gov/marc/languages/lang_pt2.html
Example(s):
<Language>dut</Language>
<Language>eng</Language>
<Language>fre</Language>
<Language>ger</Language>
MARC 21 source: Field 04l subfield $a
<LanguageAlternate> contains the three-letter MARC 21 code for the language associated with specific aspects of the work: an abstract, a table of contents, and/or the original language of a work in translation. The aspect is indicated by the LangType attribute. <LanguageAlternate> is repeated for multiple aspects and/or if any one of these aspects occurs in multiple languages.
The values in <LanguageAlternate> are found in the MARC Language Code list, Part II: Code Sequence at http://www.loc.gov/marc/languages/lang_pt2.html.
Example(s):
<LanguageAlternate LangType="Summary">eng</LanguageAlternate>
<LanguageAlternate LangType="TableOfContents">chi</LanguageAlternate>
<LanguageAlternate LangType="Original">rus</LanguageAlternate>
MARC 21 source: Field 041 subfields $b, $f, $h
MARC 21 source: Fixed Field 008 (various bytes), Fields 256, 300
The <Abstract> element contains abstract material which was written by the author(s) of the bibliographic work. It is optional and repeatable. Compare to <OtherAbstract>, which contains abstracts which were written by other sources or are of uncertain origin. It is possible for a single record to contain both <Abstract> and <OtherAbstract>.
MARC 21 source: Field 520 when Indicator 1=3 or blank and subfield $9 contains "AUTHOR"
Additional information/background:
Due to historic data entry policies or limitations in source or NLM legacy systems, abstracts may be truncated. An indication of truncation is a phrase at the end of the abstract, enclosed in parentheses, which begins with the words ABSTRACT TRUNCATED.
When located at this position in the order of the XML, one level below the <NLMRecordCitation> envelope element, <Affiliation> exists only on records contributed to LocatorPlus by NASA. This occurrence of <Affiliation> gives the institutional affiliation of the first personal author listed on this record at the time the work was written and published.
Example(s):
<Affiliation>Lockheed Engineering and Sciences Company, USA.</Affiliation>
<Affiliation>Department of Infectious Diseases, St. Jude Children's Research Hospital, Memphis, Tennessee, USA.</Affiliation>
<Affiliation>Institute of Biophysics, Academia Sinica, Beijing, People's Republic of China.</Affiliation>
MARC 21 source: Field 700 subfield $u of first Author (not "Investigator"). NASA use only.
The <OtherAbstract> element contains abstract material which was not written by the author(s) of the bibliographic work. It is optional and repeatable. Compare to <Abstract>, above.
The Type attribute indicates the type of (non-author) abstract in the <OtherAbstract> element, i.e., the organization which provided the <OtherAbstract>.
MARC 21 source: Field 520 EXCEPT when that data qualifies as an <Abstract>.
The <ContentsNote> element contains information about the contents of the work, such as chapters drawn from the table of contents, or the titles of separate parts/volumes contained within the larger bibliographic work. It may include a statement of responsibility for the separate parts.
Example(s):
<ContentsNote>The Anatomy of the inguinal region -- Clinical aspects.</ContentsNote>
<ContentsNote>pt. 1. The differential diagnosis of acute renal failure.--pt. 2. The management of acute renal failure.</ContentsNote>
<ContentsNote>Contents : v. 1. Complete dentures.--v. 2. Fixed partial dentures.--v. 3. Removable partial dentures.</ContentsNote>
<ContentsNote>Contents (partial): "De' rimedii naturali d'Ischia": p. 7-274; "Tavoladelle infermitá": 38 unnumbered pages; "Aenariarum balnea ex Ioanne Elysio ... cum scholiis Io. Francisci Lombardi": p. 1-12. The "Aenariarum" has separate unnumbered half title page.</ContentsNote>
MARC 21 source: Field 505
<IndexingSourceList> is always complete; there is no attribute to indicate completeness.
For non-serial material held by NLM's History of Medicine Division (HMD), the <IndexingSourceList> contains a reference to a published description of that item in a standard source. All data is concatenated in <IndexingSourceName>; <Coverage> is not used for HMD materials.
MARC 21 source: Field 510
<NLMIndexNote> contains historical information regarding a serial title's indexing by NLM for MEDLINE and/or Index Medicus. This data was retained from legacy NLM systems but is not currently entered or maintained in LocatorPlus.
Example(s):
<NLMIndexNote>Indexing Ceased With V6n3,1989.</NLMIndexNote>
<NLMIndexNote>Indexed Selectively Until V62n1,Jan 1988.</NLMIndexNote>
MARC 21 source: Field 596 (LocatorPlus local field)
<GeneralNote> contains supplemental or descriptive information related to the work which is not appropriate for any of the more specific elements.
Example(s):
<GeneralNote Owner="NLM">Includes bibliographical references (p. 434-472) and index.</GeneralNote>
<GeneralNote Owner="NLM">Some issues accompanied by supplements on special topics.</GeneralNote>
<GeneralNote Owner="NLM">Place of publication varies.</GeneralNote>
<GeneralNote Owner="NLM">Includes index.</GeneralNote>
<GeneralNote Owner="NLM">Rev. ed. of: Office techniques for diagnosing skin disease / William H. Eaglstein and David M. Pariser. c1978.</GeneralNote>
<GeneralNote Owner="NLM">"Publication of the Joint Committee on Printing, Congress of the United States."</GeneralNote>
<GeneralNote Owner="NLM">Title from title screen.</GeneralNote>
<GeneralNote Owner="NLM">Related item: United States. Congress. Congressional record (Daily ed.) 0363-7239 (DLC) 80646573 (OCoLC)2437919</GeneralNote>
<GeneralNote Owner="NLM">Not in Thorndike & Kibre: Liber sapientie artis medicine ... Inc.: Quoniam in diebus illis ceperunt demones irritare in filios hominum ... -- [De bono habitu] Inc.: Habitus significat omne permanens et difficile solubile ... -- [De parvae pilae exercitio] Inc.: Quam quidem bonum ad sanitatem ...</GeneralNote>
<GeneralNote Owner="NLM" NoteType="FindingAid">Finding aid available in Library and electronically: folder level control.</GeneralNote>
<GeneralNote Owner="NLM">Dr. Webster was appointed professor of Anatomy at the Geneva Medical College in 1842.</GeneralNote>
<GeneralNote Owner="NLM" NoteType="Restriction">No restrictions on access.</GeneralNote>
<GeneralNote Owner="NLM" NoteType="Usage">Copyright was transferred to the public domain.</GeneralNote>
<GeneralNote Owner="NLM" NoteType="CiteAs">Biblioteca apostolica vaticana, Vat. Lat. 2378.</GeneralNote>
<GeneralNote Owner="NLM">Microfilm. 1 microfilm reel : negative ; 35 mm.</GeneralNote>
<GeneralNote Owner="NLM">Holder of originals: Biblioteca apostolica vaticana; Cortile del Belvedere, 00120; Vatican City; vc</GeneralNote>
<GeneralNote Owner="NASA">NS22716.</GeneralNote>
<GeneralNote Owner="NASA">NAS9-17900.</GeneralNote>
<GeneralNote Owner="NASA">582 ref.</GeneralNote>
<GeneralNote Owner="NASA">Space biology and medicine series edited by A.E. Nicogossian, S.R. Mohler, O.G. Gazenko and A.I. Grigoryev.</GeneralNote>
<GeneralNote Owner="NYA">Includes bibliographical references.</GeneralNote>
<GeneralNote Owner="NYA">Also available via the Internet.</GeneralNote>
<GeneralNote Owner="KIE">Includes bibliographical footnotes.</GeneralNote>
<GeneralNote Owner="KIE">15 fn.</GeneralNote>
<GeneralNote Owner="KIE">KIE BoB Subject Heading: genetic counseling</GeneralNote>
<GeneralNote Owner="KIE">KIE BoB Subject Heading: medical ethics/codes of ethics</GeneralNote>
<GeneralNote Owner="KIE">Dissertation, Ph.D. in History, University of North Carolina, 1995. Order No. 9631980.</GeneralNote>
MARC 21 source: Fields 255, 257, 340, 351, various 5XX and 7XX note fields, Field 960 (LocatorPlus local field, KIE use only)
<LocalNote> contains NLM-specific data about copies or parts of materials held at NLM. The LocalNoteType attribute specifies whether the LocalNote gives information about a dashed-on entry or about preservation action taken by NLM.
Example(s):
<LocalNote LocalNoteType="DashedOn">Part of title on microfilm. Film copy. HMD reel 63-61, no. 1</LocalNote>
<LocalNote LocalNoteType="DashedOn">-- --- Copy 2.</LocalNote>
<LocalNote LocalNoteType="PreservationAction">10 lin. ft.processed and cataloged. Awaiting future deposit of his memoirs. 1991</LocalNote>
<LocalNote LocalNoteType="PreservationAction">19950524 Not printed on acid-free paper</LocalNote>
MARC 21 source: Field 583, Field 590 (LocatorPlus local field)
<PersonalNameSubjectList> contains the names of persons who are subjects of the work reflected in this record. The structure of elements within <PersonalNameSubject> is identical to that used for personal names within <AuthorList>. However, <PersonalNameSubjectList> is always complete; there is no attribute to indicate completeness.
MARC 21 source: Field 600
NLM's controlled topical subject vocabulary, Medical Subject Headings (MeSH®), is used to characterize the subject content of works in LocatorPlus. See http://www.nlm.nih.gov/mesh/meshhome.html for information about MeSH.
<MeshHeadingList> contains the MeSH headings assigned to a particular record. Some records lack MeSH, especially those with a Status of In-Process, Not-Our-Cataloging, or On-Order, but also some older records with a Status of Complete. <MeshHeadingList> is always complete; there is no attribute to indicate completeness.
MARC 21 source: Fields 650 and 651 when Indicator 2=2
<OtherSubjectList> contains subject headings or information which do not qualify for inclusion in the elements <MeshHeadingList>, <PersonalNameSubjectList>, <SpaceFlightMission>, <Keyword> or <ChemicalList>.
On records cataloged by NLM, the large majority of LocatorPlus data contained in <OtherSubjectList> are Corporate or Meeting names and Uniform titles used as subjects. On records owned by or shared with collaborative partners or the NLM Staff Library, the terms in <OtherSubjectList> may also be Library of Congress subject headings (LCSH), geographic terms not included in MeSH, or other special vocabulary not controlled in a way to qualify as a <Keyword>.
<OtherSubjectList> is repeated for each owner. It is always complete; there is no attribute to indicate completeness.
MARC 21 source: Various 6XX fields EXCEPT those in <MeshHeadingList>, <PersonalNameSubjectList>, <SpaceFlightMission>, <Keyword>, or <ChemicalList>.
<SpaceFlightMission> is used exclusively by the NLM collaborative partner NASA. This element contains the space flight mission name and/or number when results of research conducted in space are covered in a publication.
Following the pattern established in the MEDLINE XML records, in cases where there are multiple space flight missions, a specific mission name is not directly linked to the descriptive values manned/unmanned or long/short duration, as they are in LocatorPlus. For records containing more than one Space Flight Mission name, see the Space Flight Mission Summary Table at http://www.nlm.nih.gov/bsd/space_flight.html that provides the manned/unmanned status and duration of each mission.
Example(s):
<SpaceFlightMission>Apollo Project</SpaceFlightMission>
<SpaceFlightMission>Biosatellite Project</SpaceFlightMission>
<SpaceFlightMission>Discoverer Project</SpaceFlightMission>
<SpaceFlightMission>Long duration</SpaceFlightMission>
<SpaceFlightMission>Manned</SpaceFlightMission>
<SpaceFlightMission>Mercury Project</SpaceFlightMission>
<SpaceFlightMission>Project Gemini (U.S.)</SpaceFlightMission>
<SpaceFlightMission>Short duration</SpaceFlightMission>
<SpaceFlightMission>Skylab Project</SpaceFlightMission>
<SpaceFlightMission>Unmanned</SpaceFlightMission>
MARC 21 source: Various 610, 630, 690 (LocatorPlus local field) which correspond to the values listed in the Space Flight Mission Summary Table (http://www.nlm.nih.gov/bsd/space_flight.html). NASA use only.
<KeywordList> contains controlled terms in the <Keyword> element that are assigned by the collaborative partners KIE, NASA, and PIP. The list of controlled terms differs for each partner and is subject to change. When multiple collaborative partners have added keywords to a record, <KeywordList> is repeated for each owner. It is always complete; there is no attribute to indicate completeness.
The default value for the attribute MajorTopicYN is "N". "Y" is only used when the source data in LocatorPlus carries an explicit distinction between primary and secondary importance.
MARC 21 source: Fields 593 and 690 (LocatorPlus local field); Field 700 subfield $e when subfield $e contains "Investigator" (NASA use only)
<BroadJournalHeadingList> contains occurrence(s) of <BroadJournalHeading>, the broad MeSH subject heading(s) used for the Subject Listing in the NLM publication List of Journals Indexed in Index Medicus. All titles indexed in Index Medicus are assigned at least one <BroadSubjectHeading>.
For additional information including the controlled vocabulary, refer to the List of Journals Indexed in Index Medicus at http://www.nlm.nih.gov/tsd/serials/lji.html, or ftp://nlmpubs.nlm.nih.gov/online/journals/ljiweb.pdf.
MARC 21 source: Field 698 (LocatorPlus local field)
<ChemicalList> is used by the NLM collaborative partner NASA to record one or more <Chemical> elements. The element <Chemical> has the subelements <RegistryNumber> and <NameOfSubstance>. <ChemicalList> is always complete; there is no attribute to indicate completeness.
<RegistryNumber> contains the unique five to nine digit number in hyphenated format assigned by the Chemical Abstracts Service to specific chemical substances; for enzymes, the E.C. number derived from Enzyme Nomenclature is placed in this element. A zero (0) is a valid value when an actual number cannot be located or is not yet available.
<NameOfSubstance> is the name of the substance that the registry number or the E.C. number identifies. The MeSH Vocabulary database that contains all <NameOfSubstance> values with their descriptions may be downloaded from http://www.nlm.nih.gov/mesh.
MARC 21 source: Field 691 (LocatorPlus local field). NASA use only.
Note that in order for material to be obtainable from NLM with particular <Classification> information, that occurrence of <Classification> must have "NLMCallNumberYN" value of "Y" and an "Authority" of "NLM".
Example(s):
<Classification NLMCallNumberYN="Y" Authority="NLM" CallNumberType="ShelvingNumber">HF1634</Classification>
<Classification NLMCallNumberYN="Y" Authority="NLM" CallNumberType="NLMClass">WC 140 VC no.19 1947</Classification>
<Classification NLMCallNumberYN="Y" Authority="NLM" CallNumberType="ShelvingNumber">1996 G-412</Classification>
<Classification NLMCallNumberYN="N" Authority="NLM" CallNumberType="NLMClass">WG 210</Classification>
<Classification NLMCallNumberYN="Y" Authority="NLM" CallNumberType="ShelvingNumber">2000 E-962</Classification>
<Classification NLMCallNumberYN="N" Authority="NLM" CallNumberType="NLMClass">W 50 Z999 2000</Classification>
<Classification NLMCallNumberYN="N" Authority="KIE" CallNumberType="Other">R725.5.S84 2000</Classification>
<Classification NLMCallNumberYN="Y" Authority="NLM" CallNumberType="ShelvingNumber">2002 M-860 (p.[5]-10)</Classification>
<Classification NLMCallNumberYN="Y" Authority="NLM" CallNumberType="Other">HQ 18.U5 B498k 1954</Classification>
<Classification NLMCallNumberYN="Y" Authority="NLM" CallNumberType="ShelvingNumber">Film 1021 no.7</Classification>
<Classification NLMCallNumberYN="N" Authority="NLM" CallNumberType="NLMClass">WG</Classification>
<Classification NLMCallNumberYN="N" Authority="Other" CallNumberType="NLMClass">WS 462 2001</Classification>
MARC 21 source: Field 060, Field 090 (LocatorPlus local field)
<GovDocClassNumber> contains a classification number assigned to a government document by a government agency at any level. No distinction is made between numbers assigned according to the US Superintendent of Documents Classification System and any other system, but numbers known to be cancelled or invalid have the attribute "ValidYN" set to "N".
Example(s):
<GovDocClassNumber ValidYN="Y">HEA 445-3 ANABO 99-127</GovDocClassNumber>
<GovDocClassNumber ValidYN="Y">HE 23.1309/2:</GovDocClassNumber>
<GovDocClassNumber ValidYN="Y">X 1.1/A:</GovDocClassNumber>
<GovDocClassNumber ValidYN="N">H 20.3320: AR 7/</GovDocClassNumber>
MARC 21 source: Field 086
<ELocationList> contains information needed to locate and access electronic resources. Each separate occurrence, which is contained in an envelope called <ELocation>, may in turn have two elements. URL (Uniform Resource Locator) information is carried in the <ELocationID> element with the attributes defaulting to EIdType="url" ValidYN = "Y"; any additional data is <DescriptiveInformation>.
<ELocationList> is always complete; there is no attribute to indicate completeness.
MARC 21 source: Field 856
<Host> contains information about the host or "parent" item for the constituent unit described in the record, especially when the record itself describes a book chapter. The amount of detail supplied varies considerably, but at a mimimum contains the title of "parent".
Example(s):
<Host>Harvard Community Health Plan clinical guidelines and algorithms</Host>
<Host>Sulzman FM, Genin AM, eds. Space biology and medicine, vol. 2. Life support and habitability</Host>
<Host>Gaylin, Willard; Macklin, Ruth; Powledge, Tabitha M., eds. Violence and the Politics of Research</Host>
<Host>Organisation for Economic Co-operation and Development [OECD]. Development Centre. Mortality in developing countries. Tome 2. Data bank</Host>
<Host>Los Alamos Life Sciences Symposium (1st : 1973). Mammalian cells, probes and problems : proceedings of the first Los Alamos Life Sciences Symposium held at Los Alamos, New Mexico, October 17-19, 1973 [Oak Ridge, Tenn.] : Technical Information Center, Office of Public Affairs, U. S. Energy Research and Development Administration ; Springfield, Va. : available from the National Technical Information Service, 1975</Host>
MARC 21 source: Field 773
<LCCN> contains a unique alpha-numeric identifier ("Control Number") assigned to the material by the Library of Congress. Valid LCCNs have the attribute "ValidYN" set to "Y", and only one occurrence of <LCCN> with ValidYN="Y" should occur per record. By contrast, LCCNs known to be cancelled or invalid have the attribute "ValidYN" set to "N"; and with this attribute setting, the <LCCN> element is repeatable.
Example(s):
<LCCN ValidYN="Y">40-33754</LCCN>
<LCCN ValidYN="Y">74626513</LCCN>
<LCCN ValidYN="Y">2001023260</LCCN>
<LCCN ValidYN="Y">sn 90003244</LCCN>
<LCCN ValidYN="Y">39001062 //r83</LCCN>
<LCCN ValidYN="N">sn 90-31375</LCCN>
<LCCN ValidYN="N">sn 79004811</LCCN>
MARC 21 source: Field 010
<ISBN> contains an International Standard Book Number (ISBN) and qualifying descriptive information about edition, such as bindings, paper quality, and/or volume numbers of a multi-volume monographic set. <ISBN> is repeated with ValidYN set to "Y" when there are multiple ISSNs that refer to different editions.
Occurrence of <ISBN> containing ISBNs known to be cancelled or invalid have the attribute "ValidYN" set to "N". If the correct ISBN is not known--usually because an ISBN known to be invalid was found to be printed in error on the item-the only an occurrence of <ISBN> on the record will be one with ValidYN="N".
Example(s):
<ISBN ValidYN="Y">0534575730</ISBN>
<ISBN ValidYN="Y">007063369X (alk. paper)</ISBN>
<ISBN ValidYN="Y">354065920X (softcover : alk. paper)</ISBN>
<ISBN ValidYN="Y">0415924499 (v. 1 : alk. paper)</ISBN>
<ISBN ValidYN="Y">0415927374 (v. 2 : alk. paper)</ISBN>
<ISBN ValidYN="Y">0838514944 (domestic : alk. paper)</ISBN>
<ISBN ValidYN="N">0071181853 (international : alk. paper)</ISBN>
<ISBN ValidYN="N">008037044 (pbk. :)</ISBN>
MARC 21 source: Field 020
<ISSN> contains the International Standard Serial Number (ISSN) , a unique 8-character alpha-numeric identifier assigned to a serial by an authoritative ISSN Network center.
Not all serials contain an <ISSN> because ISSNs have not been assigned to all serial titles.
In some cases, there will be more than one valid <ISSN> because the serial is published in both print and electronic forms. When the "ValidYN" attribute is set to "Y", the attribute "IssnType" will be set to either "Print" or "Electronic" to distinguish which ISSN value applies to which form.
Occurrences of <ISSN> which contain ISSNs known to be cancelled or invalid have the "ValidYN" attribute set to "N" and the "IssnType" attribute set to "Undetermined". There may be instances in which the only ISSN is invalid.
Example(s):
<ISSN ValidYN="Y" IssnType="Print">1053-1459</ISSN>
<ISSN ValidYN="Y" IssnType="Print">0272-541X</ISSN>
<ISSN ValidYN="Y" IssnType="Print">0022-538X</ISSN>
<ISSN ValidYN="Y" IssnType="Electronic">1098-5514</ISSN>
<ISSN ValidYN="Y" IssnType="Print">1054-6456</ISSN>
<ISSN ValidYN="N" IssnType="Undetermined">0740-0101</ISSN>
MARC 21 source: Field 022
Occurrences of <ISSNLinking> which contain ISSNs known to be cancelled or invalid have the "ValidYN" attribute set to "N".
The <ISSNLinking> element contains the ISSN designated by the ISSN Network to enable collocation or linking among the different media versions of a continuing resource. The first ISSN assigned to any medium version of a continuing resource shall also be designated to function as the linking ISSN (aka ISSN-L) and shall apply to all other media versions of that resource.
MARC 21 source: Field 022
<NCBIIssnAlias> contains an 8-character International Standard Serials Number (ISSN) used by the National Center for Biotechnology Information (NCBI) at NLM. NCBI ISSN aliases are used in NCBI databases. Since the identifiers in <NCBIIssnAlias> are not deduped against those in <ISSN>, the same values may appear in both places.
Example(s):
<NCBIIssnAlias>0749-8063</NCBIIssnAlias>
<NCBIIssnAlias>1526-3231</NCBIIssnAlias>
MARC 21 source: Field 922 (LocatorPlus local field. NCBI only)
<STRN> contains a Standard Technical Report Number (STRN) formulated according to American National Standards Institute (ANSI) or International Standards Organizations (ISO) standards for numbers assigned to technical reports.
All occurrences of <STRN> are considered to be valid; the "ValidYN" attribute is not used for this element.
Example(s):
<STRN>DOT HS 808 641</STRN>
<STRN>RAND/DRU-1885-AHCPR</STRN>
MARC 21 source: Field 027
<Coden> contains the CODEN designation, a six-character unique identifier for scientific and technical journal titles.
All occurrences of <Coden> are considered to be valid; the "ValidYN" attribute is not used for this element.
Example(s):
<Coden>OFISAD</Coden>
<Coden>JOVIAM</Coden>
<Coden>ARTHE3</Coden>
MARC 21 source: Field 030
<OtherID> contains identifying numbers which link a LocatorPlus record to its precursor record in an NLM legacy system, an NLM collaborative partner's database, or the WorldCat database at OCLC (Online Computer Library Center, Dublin OH).
The attribute Prefix contains the organization code from the MARC field 003 of the incoming MARC source record that was loaded into LocatorPlus. When the record was loaded, this Prefix was moved to the head of the MARC 035 field and is in parentheses. Because of the multitude of possible organization codes, their changing nature and their lack of mnemonic content, no controlled list of values has been established for this attribute.
The attribute Source also identifies the organization which held the source record at the time it was loaded into LocatorPlus, but in a form which is more user-friendly and is controlled by a list of attribute values. If Source="NLM" and the value in <OtherID> ends in (s), this is a SEQ (sequence number) from NLM's legacy Serials Record System. Other values for the Source attribute are collaborative partners and OCLC.
Since some records are created as new records in LocatorPlus or come from sources which are not recorded, <OtherID> may not be present on all records. Conversely, it is possible for a record to have more than one <OtherID>.
Example(s):
<OtherID Prefix="(DNLM)" Source="NLM">SR0003345(s)</OtherID>
<OtherID Prefix="(DNLM)" Source="NLM">J41260000(s)</OtherID>
<OtherID Prefix="(OCoLC)" Source="OCLC">01783311</OtherID>
<OtherID Prefix="(OCoLC)" Source="OCLC">49759873</OtherID>
<OtherID Prefix="(DNLM)" Source="CIT">13461</OtherID>
<OtherID Prefix="(DNLM)" Source="HSR">HSTAR:94904932</OtherID>
<OtherID Prefix="(DNLM)" Source="KIE">KIE:16686</OtherID>
<OtherID Prefix="(DNLM)" Source="NASA">NASA:98617062</OtherID>
<OtherID Prefix="(DNLM)" Source="PIP">PIP:00005171</OtherID>
MARC 21 source: Field 035 when Source is NLM "SEQ" (pre-LocatorPlus NLM identifier), NLM collaborative partner, or OCLC
<AcquisitionSourceList> contains source information about the material described in this record. <AcquisitionInfoList> is always complete; there is no attribute to indicate completeness.
The repeatable element <AcquisitionInfo> in turn contains two elements, <StockNumber> and <AcquistionSource>. <StockNumber> is used for alpha-numeric stock numbers, whereas <AcquisitionSource> contains free-text information, usually a supplier name and address.
NLM collaborative partners use <AcquisitionInfoList> to record National Technical Information Service (NTIS) data for publications the collaborative partners have cataloged in LocatorPlus.
MARC 21 source: Field 037
<ReportNumber> contains a report number that is not a Standard Technical Report Number (STRN). Within LocatorPlus, <ReportNumber> is used to record report numbers and the Secondary Source Identifiers established by the collaborative partners NASA and PIP.
Occurrences of <ReportNumber> known to be cancelled or invalid have the attribute "ValidYN" set to "N".
Example(s):
<ReportNumber ValidYN="Y">EPA 747-R-94-003</ReportNumber>
<ReportNumber ValidYN="Y">68-D2-0139</ReportNumber>
<ReportNumber ValidYN="Y">DOT/FAA/AM-98/25</ReportNumber>
<ReportNumber ValidYN="Y">CPFH 05588cr976</ReportNumber>
<ReportNumber ValidYN="Y">PIP 670301</ReportNumber>
<ReportNumber ValidYN="Y">IND 8025336</ReportNumber>
<ReportNumber ValidYN="Y">NASA 00007057</ReportNumber>
<ReportNumber ValidYN="N">NASA-TN-D-8008</ReportNumber>
MARC 21 source: Field 088
Additional information/background: NASA continues to add these to new records where they function as accession numbers. CPFH, IND and PIP occur on records converted into LocatorPlus from Popline; no new Popline records are being added.
TOP ELEMENT for notification about deleted Catalog Records: <DeleteCatalogRecord>
Within <DeleteCatalogRecord>, <NLMUniqueID> is required and will be repeated for each deleted record.
Last reviewed: 26 December 2007
Last updated: 26 December 2007
First published: 02 August 2004
Metadata| Permanence level: Permanence Not Guaranteed