From: Anne Mitchell and Helena Zinkham, LC Prints and Photographs
A few more observations and questions that have come up as we've
been tagging finding aid for NAACP collection of photographs.
1. Using Author/Editor, scrolling through text was a very slow
process on the computer we are using (a 486), hence, tagging
was slow. Did anyone else find this a problem?
2. In reference to tags: We agree with Janice Ruth's comments
that DTD forces separation of elements in <admininfo>. In the
print version of our finding aid <acqinfo> and <custodhist>
are part of the same paragraph, but in <admininfo> one is
forced to separate these elements because it is impossible to
"wrap" both into one paragraph.
Also, in the <admininfo> part of our finding aid, we have text
pointing users to parts of the same collection found in other
custodial divisions at the library. We thought of this
information as belonging in <relatedmaterial>, however
<relatedmaterial> only allowed in <add>. We ended up tagging
this as <procinfo> because of this limitation.
3. We ran into a problem tagging the abbreviated name of our
division (P&P) in our finding aid (&P recognized as a
tag/command in SGML). Thanks to Martha Anderson in National
Digital Library we have a solution to this problem. P&P
becomes P&P for the purpose of coding. We were wondering
whether there is a stock list of characters that need this
4. We had a problem with <arrangement> and <organization> not
being allowed within each other. The print version of this
finding aid has information presented as:
"Organized into 4 subject categories: Identified
individuals (arranged alphabetically by surname); Unidentified
individuals; Children; Groups."
We settled for coding the entire statement as <organization>
5. One final question, why does SGML force use of <p> to surround
text within some elements (e.g., <note>, <scopecontent>, ...
when tag library states that the element may contain "0 or
more elements found at the paragraph level ..."