- Article Type: General
- Product: Aleph
- Product Version: 18.01
I would like p_file_96 to add appropriate values for Z30-MATERIAL and Z68-MATERIAL-TYPE based on a value in the bib. It would be especially helpful if we could set this based on values in the 049, but even if this could be done based on FMT that would be at least something. Right now, we assign everything the BOOK value, but our libraries want to use this to load other materials as well.
Both of the fields you mention are controlled by the default values table (e.g. tab_yankee_def). This table is capable of handling different values from the 049. The problem is that the 049s may not perfectly correspond to material type (or not really at all). However, since fix routines are applied before the defaults value file during the p-file-96 load, you could create special codes in the 049 field which you could then use to map different values for sublibrary / Collection / Z30-MATERIAL / Z68-MATERIAL-TYPE. The special codes would be added to the defaults value file but not to your list of actual 049 codes (e.g. tab_mapping). This would allow a single file sent from the vendor to be used without needing to separate records for different materials into different files.
For example, in the current default values file you could have:
Z30-MATERIAL AAAA BOOK
Z30-MATERIAL BBBB ISSUE
Z30-MATERIAL CCCC VIDEO
Z30-MATERIAL ########## BOOK
Z68-MATERIAL-TYPE AAAA M1
Z68-MATERIAL-TYPE BBBB M2
Z68-MATERIAL-TYPE CCCC M3
Z68-MATERIAL-TYPE ########## M1
The codes such as AAAA and BBBB should match whatever you put in the 049 fields of the records.
Thanks to Daniel Cromwell of FCLA for posting this information on the ALEPH-NA list.
- Article last edited: 10/8/2013