# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | transaction number(+) | 0;1 | NUMERIC | B | This is the internal entry number for each record. | |
1 | transaction type | 0;2 | FREE TEXT | C | This the specific type of transaction that is being transmitted or received. Some types of transactions can be combined into one mail message. | |
2 | transaction status | 0;3 | SET OF CODES | T:TRANSMITTED W:WAITING FOR TRANSMISSION R:READY FOR PROCESSING P:PROCESSED M:MANUAL PROCESS | AC | This field designates the status of transactions. 'W' for waiting for transmission and 'T' for transmitted are statuses for transactions being sent. 'R' for ready for processing and 'P' for processed are statuses after a transmission has come in. |
3 | send station | 0;4 | FREE TEXT | This is for use on FORUM and is the station number of the library station sending the transaction. | ||
4 | local transaction number | 0;5 | NUMERIC | This is for use on FORUM and is the local internal number of a serial title that is being sent to FORUM. This number will be sent back to the local site for processing the disposition of the transaction. | ||
5 | title | 1;1 | FREE TEXT | AD | This is the full serials title. | |
6 | taf da# | 1;2 | NUMERIC | This field automatically provides the FORUM Title Authority File internal number associated with a particular serials title. | ||
7 | local da# | 1;3 | NUMERIC | This field is the local station level internal number. | ||
8 | portion | 1;4 | SET OF CODES | N:NATIONAL L:LOCAL | This field is a set of codes to indicate whether the serials title was created at the national (FORUM) level or at the local level. | |
9 | synonym | 2;1 | FREE TEXT | This field is for the input of a synonym, alternative name, or acronym commonly used for this serials title. for instance, the New England Journal of Medicine is often called: NEJM. This field is not the same as the NLM TITLE ABBREVIATION. If an acronym is the official title of the serial, then the spelled-out version of the title would be entered in this field. | ||
10 | issn/isbn | 2;2 | FREE TEXT | This field is for the International Standard Serials Number of the International Standard Book Number for the specific serials title. | ||
11 | formerly | 2;3 | FREE TEXT | This field is for the complete serials title which was the immediate predecessor to this specific serials title. | ||
12 | nlm abbreviation | 3;1 | FREE TEXT | This field is for a title abbreviation either assigned by the National Library of Medicine or created following their abbreviation format. | ||
13 | continued by | 3;2 | FREE TEXT | This field is for the complete serials title which is the immediate successor to this specific serials title. | ||
14 | serline | 3;3 | FREE TEXT | This field allows for the input of the 9 character SERLINE number which is assigned to each title in the National Library of Medicine SERHOLD database. Not every serials title in the Serials Module will have a SERLINE number, particularly non-medical titles. | ||
15 | publisher | 4;1 | FREE TEXT | This field allows for the input of the name of a publisher for a serials title. | ||
16 | first issue | 4;2 | FREE TEXT | This field is for the input of the first volume and issue number and issue date, historically, used when this specific serials title was first published under this name. These volume and issue numbers and issue dates are not necessarily the same as holdings statements. | ||
17 | last issue | 4;3 | FREE TEXT | This field is for the input of the last volume and issue number and issue date, historically, used when this specific serials title was last published under this name. These volume and issue numbers and issue dates are not necessarily the same as holdings statements. | ||
18 | frequency | 4;4 | FREE TEXT | This field provides for the frequency of issue which has been assigned in the National Library Files Maintenance option on FORUM. No local input in the local Serials Module is allowed for this field. Every serials title may have a frequency assigned; however, not every serials title may have a prediction pattern. If no prediction pattern can be assigned, the frequency field may have the following type of value: QUARTERLY, NO PREDICT. PATTERN. Old serials which are not longer published may not have a frequency entered. | ||
19 | prediction pattern | 4;5 | FREE TEXT | This field provides for the prediction pattern which has been assigned in the National Library Files Maintenance option on FORUM for a serials title which is still being published. No local input in the local Serials Module is allowed for this field. If there is no value in this field, there is no prediction pattern for this title, and thus there will be no automatic prediction of the next expected issue in the CHE option on the local module. Certain issuing patterns by publishers do not lend themselves to the establishment of a prediction pattern, most notably those quarterly publications which are labeled with seasonal designations such as spring, winter, etc. In order for a prediction pattern to be created, the serials title must be dated in a MM/YY or MM/DD/YY format. | ||
20 | predict pat seq | 4;6 | FREE TEXT | This field allows for the input of the alpha-numeric code which identifies the prediction pattern and puts it into a sequence with all other patterns. This field requires the entry of one alpha character and 4 numbers, in the form of A1111, to identify and place the prediction pattern in a coherent scheme of patterns. The alpha characters identify the underlying frequency, such as A- monthly, K- 8 times per year, etc. The numbers place the prediction pattern in the proper sequence within its frequency type according to months, days, number of volumes, etc., according to a predetermined format for the PREDICTION PATTERN NAME. | ||
21 | month | 5;1 | FREE TEXT | This field allows the input of the month or months involved in the construction of the specific prediction pattern. | ||
22 | wom/dow | 5;2 | FREE TEXT | This field is to create a pattern for those serials titles which are issued on a certain day of the week for a certain week of the month, for example, Friday of the third week. This field can handle more than one week; for example, you could have a title issued the first and third Fridays; the notation would be 1/5, 3/5. Days of the week are indicated by 0=Sunday through 6=Saturday. | ||
23 | days added | 5;3 | FREE TEXT | This field is used when a serials title is used every so many days, for instance, every 21 days. In such a case, the value of 21 would be placed in this field. | ||
24 | change month | 5;4 | FREE TEXT | This field is for the input of the months at which the volume numbers increase, the values input from 1 to 12. For instance, if a monthly serials title has two volumes per year, changing in January and July, the CHANGE MONTH value should be: 1,7. | ||
25 | volume increment | 5;5 | FREE TEXT | This field allows the volume field to be incremented at the month designated by the CHANGE MONTH field. If the volume number increases by 1 at each CHANGE MONTH, the value in this field should be +1. | ||
26 | issue change | 5;6 | FREE TEXT | This field will be used on all computed JOURNAL DATES other than the first JOURNAL DATE during the CHANGE MONTH. The issue should be incremented by the amount stated in this field if the entry has a '+' as the first character. | ||
27 | issue increment | 5;7 | FREE TEXT | This field will be used on the first computed JOURNAL DATE during the CHANGE MONTH. The ISSUE will be set to the number in this field if the number does not start with a '+"; otherwise add the number to the last ISSUE. | ||
28 | day of month | 5;8 | FREE TEXT | If a serials title is always dated with a specific day of the month, that day would be entered here. More than one day can be entered. A serials title which is always issued and dated on the third and fifteenth would have the value of: 3,15. | ||
29 | index | 6;0 | MULTIPLE | 682.129 | This field allows the input of the names of indexing and abstracting tools in which various articles from various serials titles are found. | |
30 | general notes | 7;0 | WORD-PROCESSING | This is a word-processing field in which the bibliographic history of a serials title should be described along with alternative titles, synonyms, changes in publishers, etc. | ||
31 | predict pat desc. | 8;0 | WORD-PROCESSING | This is a word-processing field in which the parameters of the prediction pattern should be described in plain English. | ||
32 | multiple titles | 9;0 | MULTIPLE | 682.132 | This field is for those transactions that may have more than one title to be sent in the mail message. For example, if a prediction pattern is changed, then all titles with that particular prediction pattern will appear on the mail message. | |
33 | date/time created | 0;6 | DATE-TIME | This field stores the date the transaction was created or received, then transmitted or processed. | ||
34 | to station | 0;7 | POINTER | 4.2 | This field is the domain that the transaction is being sent to. | |
35 | explanation | 10;0 | WORD-PROCESSING | Give an explanation about why a local serial title transaction was rejected by the National Librarians. | ||
36 | message | 0;8 | FREE TEXT | This field is used for certain transactions types; whether a frequency was added, changed or deleted for a serials title or a prediction pattern. | ||
37 | user | 1;5 | POINTER | 200 | This is the user that created this transaction. | |
38 | data edited | 11;0 | WORD-PROCESSING | This is the data that was edited for a 'UTL' transaction. This will be used for the 'Any TAF Changes' report. | ||
39 | orignal transaction # | 0;9 | POINTER | 682.1 | This field refers back to the originally received transaction. It is used for reporting purposes. |