[506] in ad-lib
Forwarded message: [m.ridgeway%34@gem.geac.com:MIT # 00078, 00103 TRUNCATED VOLUME INFO]
daemon@ATHENA.MIT.EDU (Grant Young )
Tue May 2 15:31:04 1995
To: ad-cat@MIT.EDU
Date: Tue, 2 May 95 15:29:42
From: gyoung@MIT.EDU (Grant Young )
Michel has confirmed that my earlier message about multi-volumes was
correct and that the spec we have is adequate. As you can see below, Dave
Alexander will fix the problem we had in the first GMA.
-- Grant
------- Forwarded Message
To: gyoung@MIT.EDU
Subject: MIT # 00078, 00103 TRUNCATED VOLUME INFO
Date: Tue, 2 May 95 13:46 EDT
From: m.ridgeway%34@gem.geac.com
The semi-colon is ADVANCE's convention in managing this in general.
If you create an 852 tag {to convert to PIECE and it has multi-volume
enumeration on several levels the data can go in like
852$v vol 1 ; pt 2 ; bd 1
and it will parse out properly. Dave is just using the standard ADVANCE
piece management here. This will probably come up some other time with
another interface altogether so just store this convention somewhere in
your brain to be pulled out and amaze.
--
Michel Ridgeway, Project Manager, Libraries m.ridgeway@geac.com
923 West King Road, Malvern, PA 19355
voice (610) 644-4071 fax (610) 644-0907
837 DAVID.ALEXANDER 55 02MAY95 11:01 19
Subject: MIT # 00078, 00103 TRUNCATED VOLUME INFO
To: M.RIDGEWAY:34
Cc: DAVID.ALEXANDER:55
Michel,
The back-transfer was transferring the Volume info as it existed in Circ
into the 966 $d.
The problem was that it was all one string as you suspected.
i.e. Ser.2 Suppl. Bd.1
I have modified the back-transfer to insert the separator ";" for each
blank so the ADVANCE loader can parse them out properly.
This would end up as:
Ser. 2
Suppl.
Bd. 1
Dave
------- End of Forwarded Message
