TABLE OF CONTENTS INTRODUCTION 2 STANDARDS GUIDE 2 NAMING CONVENTIONS 2 DIESEL AND MOTOR CAR ROSTERS 2 MS EXCEL USERS 2 CONVENTIONS 3 CATEGORIES 3 CAT CODE (CATEGORY) ñ Field #1 3 TYPE (of Category) ñ Field #5 3 SUB-TYPE (within the TYPE) ñ Field #6 3 RAILROAD REFERENCE ñ Field #7 4 NUMBER IDENTIFIER ñ Field #8 4 NUMBER QUALIFIER ñ Field #9a 4 NAME IDENTIFIER ñ Field #9b 4 PUBLICATION REFERENCES 4 PUBLICATION REFERENCE CODE ñ Field #2 4 IMAGE REFERENCE ñ Field #3 5 PAGE (REFERENCE) No. ñ Field #4a 5 IMAGE-ID SUFFIX and PAGE REF. No. QUALIFIER ñ Field #4b 5 DATE FIELDS 5 YEAR ñ Field #11 6 DATE QUALIFIER ñ Field #12 6 LOCATION FIELDS 6 LOCATION QUALIFIER ñ Field #13 6 LOCATION ñ Field #14 6 STATE LOCATION ñ Field #15 6 COMMENT FIELDS 6 INDEXERíS ANNOTATION - Field #16 6 REMARKS ñ Field #17 7 OPTIONAL FIELDS 7 PAINT SCHEME CODE ñ Field #18 7 CONSIST NOTES ñ Field #19 7 SUBMISSION OF WORK 7 GROUND RULES 7 INTRODUCTION This document is designed to provide the reader/indexer with a general overview of the various data fields used in indexing Atchison, Topeka & Santa Fe Railway (ATSF) related images (incl. photographs, drawings, maps and other graphic elements) as published in popular railroading books, magazines and other publications. The primary purpose of the Index is to assist readers and modelers locate from popular publications, images of specific ATSF Railway related subjects up until 31-Dec-1995. Each photograph is examined for all its primary and secondary points of interest (notably with the modeling fraternity in mind), and each feature is listed separately within its category. STANDARDS GUIDE There are other documents which approach this topic from various angles. For example, there is a separate Standards Guide for Indexing ATSF Images (Stds Guide) which discusses in greater detail the technical aspects such field definitions and typical entries. The Stds Guide comes in two formats: INDXSTDS.DOC (MS Word6/95 format) and INDXSTDS.TXT (Text only with line breaks) NAMING CONVENTIONS To assist the indexer identify each subject with a degree of confidence, there is the ATSF Standard Naming Convention (Std Names)listing. This document defines how subjects are to be entered in a consistent manner so that a spade is always called a spade. This file comes in three formats: ATSFNAME.DOC (MS Word6/95 format) and ATSFNAME.TXT (Text only with line breaks) DIESEL AND MOTOR CAR ROSTERS To help indexers identify the various model diesels and motor cars (ìdoodlebugsî) there is a MS Excel 6/95 spreadsheet that contains data on each locomotive. Users of this document should recognise that this data is not meant to be definitive or 100% accurate. Far more knowledgable experts than this writer concede that it is incredibly difficult to get a handle on the Santa Feís locomotive renumbering process. As this was never our objective, it should nonetheless be adequate in identifying a locomotive by its loco number (or class) given the approximate date is known and supplying the preferred model description. Within this file is a page listing the diesels and motor cars from their acquisition date until 1965. There are also separate rosters for 1973, 1985 and 1995 as well as a list of F3/F7 units leased to Amtrak between 1971- 1973. ATSFDSL.XLS (MS Excel6/95 format) and DSL_1965.TXT (Text only with delimited tabs) DSL_1973.TXT (Text only with delimited tabs) DSL_1985.TXT (Text only with delimited tabs) DSL_1995.TXT (Text only with delimited tabs) DSLAMTRK.TXT (Text only with delimited tabs) MS EXCEL USERS Furthermore, for those users of MS Excel, there is a spreadsheet template file (ATSFINDX.XLT) which can be used to compile your index. However, all output regardless of the software used, must be saved as a tab delimited text file for eventual submission (refer to SUBMISSION OF WORK on page 7). Included in the Excel template is a separate page (worksheet) called a Cheat-Sheet that contains a comprehensive sampling of all the fields complete with detailed notes within them. CONVENTIONS The Stds Guide, Std Names and Diesel & Motor Car Roster documents specifies the only preferred terminology to used by all indexers. Any field that is left blank is always taken to mean that either there are no details for that field or if there is, it is unknown or uncertain. Indexers never attempt to second guess such details. However, they may insert a personal comment in the Indexers Annotation field (#15). The maxim - IF IN DOUBT, LEAVE IT OUT ñ applies in every instance. CATEGORIES The subjects of interest are broken down into the following categories: ? Steam Locomotives ? Diesel Locomotives ? Motor Cars (eg. Doodlebugs and self-propelled units) ? Freight rolling stock ? Passenger rolling stock ? Non-revenue rolling stock ? Trackside structures ? Miscellaneous items of interest CAT CODE (CATEGORY) ñ Field #1 The CAT CODE field allows the indexer to identify each record by its subject category. Even though each publication is initially indexed in a separate data file, it is eventually split up into various category files and integrated into its respective Master Category Database file. These records are defined by their CAT CODE (refer to page 2 of the Stds Guide). If an indexer wishes to define their own category abbreviations during the compilation process, these interim category codes must be amended to conform with the standard CAT CODEs upon completion and submission to the Indexing Group. TYPE (of Category) ñ Field #5 The TYPE field within each category, is designed to distinguish the many disparate types that make up a category. However, the logic used to define one category TYPE is not meant to logically flow across all other categories. For example, in the Freight (and Non-Revenue) car category, there are flat cars, box cars, tank cars, etc. each being a different TYPE. However, within the Passenger car category, the TYPE is defined as wooden (WDN), heavyweight (HWT), lightweight (LWT) or bi-level (BIL) depicting the technological era in which the subject was constructed rather than any coincidental mode of construction. In the case of steam locomotives, the Whyte System's wheel arrangement defines its TYPE, whereas the builderís model defines the diesel and motor car TYPEs. Included in the Diesel & Motor Car Rosters are the preferred models names together with its locomotive number and class from their construction until 1995. The TYPE of trackside structure is defined by its functional role (eg. depot, signal, bridge, etc.) as shown in the Std Names. The Miscellaneous category has many TYPEs all dependent upon the subject. A list of a few sample TYPEs within each of the CATEGORIES is shown in the Stds Guide. SUB-TYPE (within the TYPE) ñ Field #6 This field is meant to breakdown the TYPE in various sub-types. In the case of the Freight (incl. non-revenue) category, a box carsí SUB-TYPE field is its classification number (eg. Bx-2). However, in the case of passenger cars, the SUB-TYPE could have Baggage, Sleeper or Observation car. In the case of steam, diesel and motor car locomotives, the SUB-TYPE is its manufacturer or builder abbreviation, a list of which is in the Std Names. Miscellaneous category/type records would show an appropriate TYPE breakdown. As stated in the TYPE topic, the Std Names defines the preferred Full Descriptive Names for Trackside Structures for both TYPE and SUB-TYPE values. Where the TYPE description is followed by a comma then the subsequent SUB-TYPE description must be used. For example, if the TYPE is Signal, then the SUB-TYPE could be Cantilever Semaphore or Bridge Searchlight or something else. However, a TYPE does not always have to have a SUB-TYPE if it is inappropriate (eg. Ashpit). Should the indexer be confronted with an anomoly not defined in the Std Names, then the decision to complete the SUB-TYPE field can either be referred to the Group or left to their discretion with an appropriate Indexers Annotation entry. RAILROAD REFERENCE ñ Field #7 All Santa Fe subjects must have ATSF in this field. Predecessor railroads (as being portrayed) should be entered. A tentative listing of railroads and their abbreviations are included in the Std Names. The Index is focussed exclusively on all related subjects pertaining to the ATSF Railway and its affilated RR companies. All other railroads, including the BNSF are not to be included (although individuals can include them in their own separate file/s). NUMBER IDENTIFIER ñ Field #8 Numeric (1-20 chars) This field is the subject's unique numeric identifier if applicable. Some early steam locomotives had both a number and a name assigned to it. In such cases the number will appear in the Number field and the name in the Number Qualifier field. In the case of the Structures category and some Miscellaneous category/types this field may not be applicable. NUMBER QUALIFIER ñ Field #9a Adjacent to the NUMBER field, is its NUMBER QUALIFIER field. This optional field allows the indexer to enter any suffix data without interfering with the sort criteria of the numeric NUMBER field. For example, diesel loco number 304 would be sorted differently if the NUMBER field contained text data such as a LABC suffix. Using the NUMBER QUALIFIER field to store the suffix eliminates this problem. NAME IDENTIFIER ñ Field #9b Sometimes a name was allocated along with or instead of a number (eg. Cimmaron Valley or John R. Hayden) and it should be entered in the Name Qualifier field. The use of quotation marks is not normally required, unless it was an unofficial nickname (eg. ìMadame Queenî). PUBLICATION REFERENCES Each publication being indexed is allocated a Publication Reference code as shown in the Stds Guide. If a book is not shown in the listing, then the reader should note that the listing is only a starting point. The Indexing Group allocates all new Publication Reference Codes as required. If none is listed, the indexer should request one and in the interim define their own code. PUBLICATION REFERENCE CODE ñ Field #2 A comprehensive list of ATSF biased publications is included in the Stds Guide. Normally an indexer will create a separate file for each new publication being indexed. If the volume of subjects is minimal in a publication, he may choose to include several similar publications into one file. Each book is assigned a PUBLICATION REFERENCE CODE and it is entered into Field #2 for every entry compiled from that publication. If indexers choose to invent their own shortened codes, then this is allowed, provided that it is changed to the preferred code upon completion and before submission to the Indexing Group. IMAGE REFERENCE ñ Field #3 This defines the type of graphic element. The list of predefined IMAGE REFERENCE codes is listed in the Stds Guide. However, the majority of images will be monochrome or black and white photographs and these have a reference code of BWP. PAGE (REFERENCE) No. ñ Field #4a This is strictly a numeric page number on which the image is to be found. Please note, that in referencing calendars or postcards, the page number is irrelevant and should be left blank. IMAGE-ID SUFFIX and PAGE REF. No. QUALIFIER ñ Field #4b In order to distinguish multiple images on a page, each image is given a unique alphabetic suffix (regardless of whether the subject is an ATSF subject or not). Where an image spreads across more than one page, the first page number containing some or all of the image is used. The purpose of this suffix is not so much as to identify photographs on a page, but to uniquely identify the image across multiple databases. The allocation of suffixes always begins with ëaí (even if there is only one image on the page) and follows a rasterised pattern. This means that the indexer starts from the top left corner of a page and scans across the top towards the right. Then going down to the next row of images, starts from the left hand side and repeats this process until the last image nearest the bottom right hand corner is reached. Optional Page Reference No. Qualifier This field also supports an additional qualifying role where the related Page Reference No. is a non-numeric value. The following examples includes a typical Page No. and Image-ID suffix followed by the hyphenated Page Ref. No. Qualifier: * Cover, dustjacket, endpapers (including front and rear for each) 0a-cover; 0a-cover-f; 0a-cover-r 0a-dustjacket; 0a-dustjacket-f; 0a-dustjacket-r 0a-endpaper; 0a-endpaper-f; 0a-endpaper-r NB: examples not showing ñf or ñr implies identical images. * Roman numerals (with ëzeroí page numbers) 0a-iii; 0b-v; 0a-ix * Plates inserted as un-numbered pages between two consecutive pages 24a-1; 24a-2; 24b-2; 24a-10 * Frontispiece page (eg. an un-numbered title page) 2a-Frontispiece (ie. uses an implicit page number) 0a-Frontispiece (ie. no implicit page number to use) * Liftout pages/sheets (eg. maps, timetables, plans, etc.) 0a-Liftout-1 * Foldout pages 3a-Foldout-1 (ie. uses an implicit page number) 0a-Foldout-1 (ie. no implicit page number to use) DATE FIELDS There are two date fields. The first is the YEAR date field and the other is a DATE QUALIFIER field. YEAR ñ Field #11 This four digit numeric field is for the YEAR date (ie. 1955). If the year is unknown, but is within a known decade (eg. the 1950ís), then the YEAR date is shown as 195x (x = the unknown year). If a YEAR date is unknown, then it should be always left blank as indexers must not guess dates. DATE QUALIFIER ñ Field #12 This role of this field is not unlike the Number Qualifier field (#9), in that it supports a variety of possible suffixes to the Year date. For example, ? Where there is a span of more than one year, the earliest year is shown in the YEAR date field (eg. 1955) and the last year is entered into the Date Qualifier field (eg. -1956). ? Where the YEAR date is not definite, but is within a year either way, then the word Circa can be entered after the YEAR date. ? A full list of legal date qualifiers is also listed in the Stds Guide and the Excel spreadsheet template. LOCATION FIELDS The location details are broken into the following three fields: LOCATION QUALIFIER ñ Field #13 This is a freeform text for such terms as ënearí, ëWest ofí, ëon turntableí. It may also be the precise place where the photograph was taken, and could include a milepost (MP54), ëat depotí, ëfreight yardí, ëround houseí, ëat river crossingí, ëon bridgeí, etc. LOCATION ñ Field #14 This is a freeform text field depicting the general area in which the photograph was taken. If known the location, albeit a station name and/or region. The region could be a valley or a pass or an area within a Division (eg.Mojave Desert). It could also, be a station name (eg. ëVictorvilleí or ëSummit, Cajon Passí). STATE LOCATION ñ Field #15 This field is the two letter state abbreviation code (eg. CA, AZ, CO, etc.) where the photograph was taken. Where the subject is crossing the state border (eg. on a bridge crossing a river) enter the subject twice but with the respective state code shown in each instance. COMMENT FIELDS There two types of comment fields within the Index database: INDEXERíS ANNOTATION - Field #16 This is a 255 character TEMPORARY freeform text field for the indexerís personal use. Itís not unlike a figurative yellow Post-It sticker on which he can write himself a reminder in respect of some specific detail in a record. It could contain a request for assistance in resolving some indeterminate detail. This allows him to move on and return to the query at a later date. If the problem remains, then the proofreader or his assistant will scan for all such notes and attempt to resolve them. It is not to be used for storing additional information relative to the subject being indexed as the Remarks field has been defined for that role. It will be eventually discarded once it has served its purpose and the field possibly recycled at a later date. REMARKS ñ Field #17 This is a 255 character freeform text field. Unlike the preceding field, this field is used to store any interesting information relative to the subject being indexed. Some indexers may enter a notation about the train itself, or something special about the occasion. Others may choose to note the details of a predecessor railroad. In a nutshell it is designed to allow the indexer to store data not appropriate in any of the other fields. OPTIONAL FIELDS Because of the complexity of this task, it was felt that it should be approached in two or more phases. The first phase would attempt to address all the first 16 fields. Then as part of a second phase, additional information could be appended to the initial database. However, as a concession to those indexers who feel that color schemes and train consist notes are equally important and should be included in the first phase, these OPTIONAL fields have been defined for those who wish to complete them. PAINT SCHEME CODE ñ Field #18 This field has been defined to store a 4 letter color code for diesel and motor car paint schemes. A tentative color code for buildings is also included in the Stds Guide. CONSIST NOTES ñ Field #19 This is a 1-255 character text field, where the preferred consist/train codes as shown in the Stds Guide may be entered. Essentially it is designed to show the makeup or consist of a train. SUBMISSION OF WORK Normally, every publication being indexed has its own file (filename = a suitable 3-8 char.title abbrev.). When your contribution has been completed, it must be saved as a simple text file with tab delimiters. For your first submission, please contact the ATSF Image Indexing Group giving them all your details and the title of the publication indexed. You will be advised of a forwarding address to send your work to so that it may be proofread and checked for accuracy. Once this has been completed the submitted work will be forwarded to the Index Database Administrator for assimilation into its respective Master Category files. GROUND RULES The ATSF Image Indexing Group is group of private individuals who have undertaken a voluntary and a non-commercial venture in supporting the Santa Fe enthusiast. Nonetheless, readers and indexers who access its files implicitly acknowledge the following disclaimers: * Contributors should note that all work submitted to the ATSF Image Indexing Group (hereafter referred to simply as the Group) is viewed as a completely unsolicited voluntary undertaking and no payment is to be expected, claimed or will be forthcoming. * All submitted work becomes the exclusive property of the Group, although individuals are free to use their own private copy of their submitted work as they see fit. * The Group does not accept any responsibility for errors or misleading information supplied by any contributor or individual members of the Group. * The Group whilst striving to ensure that all its files are not infected by damaging software programs such as computer viruses, will not be held responsible for any damage done to any computer system accessing its files. * The Group offers free access to its files, to any private individual on the sole basis that is for their exclusive personal use. It is not intended for commercial use or exploitation by any individual, group or enterprise. * The submission for changes to the format, design or any other aspect of the overall database model may be made to the Group for its consideration. If the Group by a majority vote turns down the recommendation, then only one appeal for reconsideration may subsequently be lodged with the Group, providing that the line of argumentation or reasoning is, * Not simply a rehash of its original content, but a genuine re-examination of merits not previously clearly presented, or * Not a claim that the recommendation was rejected due to some perceived discriminatory action by the Group. The outcome of any appeal is final, non-negotiable and no subsequent discussion of the matter will be entertained by the Group. John Parker 26-Jan-2000 Previous version: 6-Jun-1999 Page 2 of 8 AT&SF Railway Image Index Issue date: 26-Jan-2000 README.DOC