Cara - In response to your comments about the inability to get
your columns to line up in Panorama, I can report that the two expert
Panorama users at Yale (I and a colleague) have never been able to
make the program parse columns as intended by Panorama. Over the past year
or so, we
have tried many different approaches with the style sheet and the
COLSPEC/SPANSPEC tags, but to no avail. Our opinion was that
the discrepancy between the EAD.DTD and Panorama was to account for it.
That is - Panorama builds tables based on CALS protocol - but the EAD
provides for table markup using a protocol that is not strictly CALS compliant.
(That's what we were told last year.)
So, we shrugged our shoulders and went with what Panorama gave us.
For the Beinecke Library finding aids, the layout and spacing of tables
and columns looked close enough to our current online displays that
we were content, so we decided to not even include COLSPECS and
SPANSPECs. The Divinity Library and the Manuscripts and Archives
Department kept those tags in their instances, anticipating the daywhen they
I write this assuming that you have been able to make make columns and
cells appear within Panorama using the style sheet. If you are still having
doing that, please write me and I may be able to give you some basic
Beinecke Rare Book and Manuscript Library
[log in to unmask]
At 11:44 AM 4/18/97 EST, you wrote:
>We are currently marking-up our finding aids with the Author Editor
>Program. We create the style sheets and navigators in Panorama Pro.
>We have run into some difficulty editing the style sheet to format the
>container listings. We are unable to align the box, folder, and
>contents even though we followed the table model offered by RLG Fast
>track. Does anyone have any helpful suggestions they could pass
>Also, in accordance with RLG's table model, we insert 20 colspec tags
>followed by 4 spanspec tags. When viewed in A/E the start and end
>tags for each tag appear together. When we export in SGML and import
>it into Panorama Pro, the 20 colspec tags are broken up, with the
>first 10 start tags listed followed by the 4 span spec tags and then
>the 10 end tags for colspecs. We believe this may be the reason for
>our container listing problems. However, we have not yet figured out
>a way to remedy this. Nor, I should add, has SoftQuad. Any
>information will be much appreciated.
>New York University Archives
>[log in to unmask]