> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Riley, Jenn
> Subject: Triggering horizontal lines in finding aid display
> For some of our more complex finding aids we're discovering that vertical space and indenting
> some of the description isn't enough to make it obvious where the descripton of one component
> ends and the next begins. One option we're considering for improving this is rendering an <hr>
> (or something similar) between <c0x> at the same level. But *only* in certain cases!
Hi Jenn --
It sounds like the ruling has nothing to do with the content of your finding aid but is a display issue, right? If so, rather than using a hard-coded attribute in your EAD, why not decide under what conditions you want it, then test for it in the style sheet and output if it meets the conditions? For example, say you want an hr only if there are more than 3 c02s; put that test in your style sheet. Or if you want it only if there are more than 3 c02s AND they each have more than 3 c03's. Or only if there are more than 75 c0#s in total. Etc etc etc -- you can make up whatever test you want.
This gives you several benefits: you don't have to remember to encode it in the EAD; you keep the content and the display decisions separate; it will always be done consistently; and if you want to change the conditions, you can do it in the style sheet rather than having to re-code your EAD.
Another option besides an hr would be a spacer row in the table and give it a specific background color (black, dark gray, etc). Again, that could (and I would argue should) be done in the style sheet.
(be green - don't print this email!)
Special Collections Research Center
Syracuse University Libraries
222 Waverly Ave.
Syracuse, NY 13244
[log in to unmask]