This is a REQUIRED FIELD at UCSF and TDO. The identification is assigned internally at each organization to maintain consistency within a collection. This field is used internally to identify the document, as well as to keep record, image file, and OCR'd text linked. This number will be unique among each collection, but not necessarily across collections. [Dublin Core Metadata Mapping: Identifier]

STRONGLY RECOMMENDED FIELD. The Bates number on the first page of a document. [Dublin Core Metadata Mapping: Identifier] Example: 2024868371

The last Bates number on the document. If this is blank, the document is assumed to be a single page, unless the PageCount variable is set. [Dublin Core Metadata Mapping: Identifier] Example: 2024868773

(Note: Repeatable Field.) In this field, give Trial Exhibit Number, and any second, third Bates numbers, in this format: FirstBatesNumber/last 4 digits of Bates range. [Dublin Core Metadata Mapping: Identifier]

STRONGLY RECOMMENDED FIELD, naming the tobacco company which originally created the document ("non-industry" is also an option.) [Dublin Core Metadata Mapping: Creator] Example: RJR

(Note: Repeatable Field.) Names the company division which produced the document. See Personal Name Element below for a further explanation of the format of this field. [Dublin Core Metadata Mapping: Creator] Example: Research & Planning, or R&D

REQUIRED FIELD. The format in which UCSF holds the material: print, image file, web-based image file (held at a location other than UCSF, i.e. TDO) [Dublin Core Metadata Mapping: Format]

(Note: Repeatable Field.) The type of document. An authority list is to be provided. [Dublin Core Metadata Mapping: Type]

REQUIRED FIELD. The number of pages in the document. [Dublin Core Metadata Mapping: Identifier] Example: 76

(Note: Repeatable Field.) STRONGLY RECOMMENDED FIELD. This field stores the document image file, or the link to the image file. [Dublin Core Metadata Mapping: Relation]

(Note: Repeatable Field.) If the document has an attachment not included here, please note that here. Cite and link if possible. [Dublin Core Metadata Mapping: Relation]

(Note: Repeatable Field.) If the document contains marginalia, drawings, or if it is a draft, please note that here, even if it is indicated in the title. This is both to clarify dirty OCR'd text and to frame the document as a physical object--legibility, etc. An authority list of characteristics can be developed to aid indexers in consistency. [Dublin Core Metadata Mapping: Description] Example: Contains handwritten notes, probably from HW.

(Note: Memo Field) This field stores the OCR'd text of the image file. Its function is to hold text searched by search engines to find documents rather than for readability. Some systems may choose not to display the OCR at all, although others will use it for KWIC (Key Word In Context) when returning search results. [Dublin Core Mapping: Description]

STRONGLY RECOMMENDED FIELD. The date on the document. Suggested format (numeric field): yyyymmdd, using a question mark after the date if uncertain Zeros can be used when a document is an annual or monthly date. [Dublin Core Metadata Mapping: Date]

(Note: Memo Field) Quoted portion of document. Not used by all groups, but useful to some. Recommendation: identify the page number and the speaker, and note any context necessary to frame the quote. [Dublin Core Metadata Mapping: Description]

(Note: Repeatable Field.) The default is English. [Dublin Core Metadata Mapping: Language] Example: GERMAN

(Note: Repeatable Field.) Listing of the URLS which find this document, i.e. at UCSF, at TDO, at pmdocs.com, etc. [Dublin Core Metadata Mapping: Identifier]

REQUIRED FIELD. The title of the document. If there is no obvious title, the indexer will create one and place it in brackets in the field to indicate that the title is a created one, as in [Re: Project ASSIST]. [Dublin Core Metadata Mapping: Title] Example: Answers to the Most Asked Questions About Cigarettes

(Note: Repeatable Field.) REQUIRED FIELD. Personal names of document authors. Sometimes the Corporate Author field will be the only one which can be filled in. Then, consider that the required field. An authority list is being developed for this. [Dublin Core Metadata Mapping: Creator] See Personal Name Element below for more details about this field.

(Note: Repeatable Field.) The corporation or organization which authored the document. Sometimes this will be the only author of a document. [Dublin Core Metadata Mapping: Creator]

(Note: Repeatable Field.) This field names the person who is the recipient of the document. Recipient company is its own field. Format: lastname, firstname, mi, degree. (title/company: division) Since some documents may have a large number of recipients, a suggested rule of thumb for manual indexing is to name the first ten. [Dublin Core Metadata Mapping: Description] See Personal Name Element below for more details about this field.

(Note: Repeatable Field.) The corporate recipient of a document. [Dublin Core Metadata Mapping: Description] Example: Philip Morris

(Note: Repeatable Field.)Format: lastname, firstname, mi, degree. (title/company: division). This field also includes elements named in "BCC".[Dublin Core Metadata Mapping: Description] See Personal Name Element below for more details about this field.

(Note: Repeatable Field.) Name(s) of individuals referenced in the text of the document. All names are recorded with the last name first followed by first and middle initials when available. Multiple entries are separated by semi-colons. Format: lastname, firstname, mi, degree. (title/company: division); lastname, firstname, mi, degree. (title/company: division) Note: the industry fields "person attended" will map to this field. [Dublin Core Metadata Mapping: Description] See Personal Name Element below for more details about this field.

(Note: Repeatable Field.) This field will ultimately contain industry field "organization attended" information, as well as any organizations named in the document. [Dublin Core Metadata Mapping: Description]

(Note: Repeatable Field.) Project Hippo [Dublin Core Metadata Mapping: Description] Example: Operation Whitecoat

(Note: Repeatable Field.) This field identifies any places explicitly emphasized in a document, and might be a country, state, or city. [Dublin Core Metadata Mapping: Coverage] Authority List: ISO3166 (Country) Example: GERMANY

(Note: Repeatable Field.) Cigarette, Cigar, and Smokeless Tobacco brands are named here. [Dublin Core Metadata Mapping: Description] An authority list is to be provided.

(Note: Repeatable Field.) When the document discusses marketing, methods should be listed here. An authority list is to be provided. [Dublin Core Metadata Mapping: Description] Example: Print Ad

(Note: Repeatable Field.) When a target market is named, identify it here. An authority list is to be provided. [Dublin Core Metadata Mapping: Description] Example: Hispanic

(Note: Memo Field) REQUIRED FIELD at UCSF. STRONGLY RECOMMENDED FIELD. The indexer's description of the document's content. Further style guidelines and other instructions will be provided to indexers. [Dublin Core Metadata Mapping: Description]

(Note: Repeatable Field.) REQUIRED FIELD. Terms from the ANR thesaurus. [Dublin Core Metadata Mapping: Subject] Example: Secondhand Smoke

(Note: Repeatable Field.) A field for non-standard subject terms, used to express concepts that are not available in the standard vocabulary (thesaurus). This field can also function as a "holding pattern" for terms which are being proposed for inclusion in the Thesaurus. They should be mentioned in the abstract as well, as space allows. [Dublin Core Metadata Mapping: Subject]

(Note: Repeatable Field.) Presently, this field holds Roswell Park Cancer Institute Subject Heading list Major terms. [Dublin Core Metadata Mapping: Subject] Example: Tobacco Industry

(Note: Repeatable Field.) Presently, this field holds Roswell Park Cancer Institute Subject Heading list minor terms. [Dublin Core Metadata Mapping: Subject] Example: Tobacco Industry--health claims

(Note: Repeatable Field.) This field derives from PM citations on www.pmdocs.com, and describes the physical location in which the document was found. Indexers will not enter information into this field, as it can only be provided by (and may only be relevant to) the tobacco company. [Dublin Core Metadata Mapping: Identifier] Example: STINN,WALTER/INBIFO OFFICE

(Note: Repeatable Field.) This field derives from PM citations on www.pmdocs.com. Indexers will not enter information into this field, as it can only be provided by (and may only be relevant to) the tobacco company. [Dublin Core Metadata Mapping: Description] Example: STMN/R2-038

(Note: Repeatable Field.) Privilege codes are used by the Bliley set, as well as some others. [Dublin Core Metadata Mapping: Description]

(Note: Repeatable Field.) From the PM (and other) collections. Indexers will not need to enter information. [Dublin Core Metadata Mapping: Source] Example: I35

REQUIRED FIELD for internal indexing use. Identifies the tobacco control group or individual researcher or industry website which provides the document. i.e., ANR, RPCI, Mass, Philip Morris. Note: there can be more than one source. i.e., PM, JAMA. [Dublin Core Metadata Mapping: Source]

(Note: Repeatable Field.) Other physical or cyber locations of the document. [Dublin Core Metadata Mapping: Identifier] Example: Roswell Park Marketing to Youth print collection

(Note: Memo Field) Indexer's notes on context of document, other information. Notes on physical aspects of the document (condition, marginalia, etc.) should be entered in Characteristics field. [Dublin Core Metadata Mapping: Description] Example: This memo appears to be a response to Doc 7668708.

(Note: Repeatable Field.) This refers to the box number of the physical document, located at one of the depositories or institutions. See File Number. [Dublin Core Metadata Mapping: Identifier] Example: Guildford Depository 11223444

(Note: Repeatable Field.) This refers to the physical location of the document in the Guilford or Minnesota Depositories, or at Roswell, ANR, UCSF, etc. [Dublin Core Metadata Mapping: Identifier] Example: MN Depository 12222344

(Note: Repeatable Field.) This field will be utilized to identify the litigation stamped on the document, although the same document may also have been presented in other cases. Indexers may attempt to identify a complete history if they wish. This field is currently used at Philip Morris. [Dublin Core Metadata Mapping: Relation] Example: STMN/PRODUCED

(Note: Repeatable Field.) The date on which the document was introduced in court. This need only be included if it were obvious on the document, or easily obtained. [Dublin Core Metadata Mapping: Date] Example: 19970315

(Note: Repeatable Field.) The witness with whom this document was used in litigation. Uses Name Format, see description below. [Dublin Core Metadata Mapping: Description] See Personal Name Element below for more details about this field.

(Note: Repeatable Field.) REQUIRED FIELD at UCSF. The initials of the person who has indexed the document, or checked the document to confirm that it conforms to UCSF's required standards. This field will not be public. [Dublin Core Metadata Mapping: Contributor] Example: CMW

Most fields are made up of a string of characters. Names are not -- they are made up a other fields, which are made up of strings of characters. Example:

Henry
Wakeham

This field exists as a backup for systems that lack the ability to properly parse out the fields within a name (e.g. the tobacco industry indices). Properly formatted, this should be lastname, firstname including suffix such as Jr., mi, degree. (title/company: division.) This field will be linked to a name authority list. When entering information, be as complete as it is possible to be, but do not guess. If only initials are given, enter these: lastname initial, firstinitial middleinitial. Example: Cullman, Joseph F. (President/Philip Morris)

The surname of the person. Example: Cullman

Everything which is not part of the surname that is part of the name, including "Jr.", "III", etc., and degree. Example: Joseph F. III

The title of the person (the term Position has been assigned to avoid confusion with the title of the document). [Dublin Core Metadata Mapping: Description] Example: President