The only subelement we use regularly is <extent>, which we use at both the collection level and the c0# level. We haven't found it particularly useful to date.
We have occasionally used <dimension> at the c0# level, particularly in our cartoon collections which contain a lot of original artwork. Again, we haven't found a use for it yet, but since it was easy to do and we could envision potential uses for it we decided to go ahead.
I'd be curious to see a summary of your pros and cons that come out of your own discussion.
Michele
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Mike Doylen
Sent: Tuesday, November 15, 2011 5:30 PM
To: [log in to unmask]
Subject: subelements in <physdesc>
At my repository, we are discussing the pros and cons of marking up elements of <physdesc> at a more granular level than we've done in the past.
Previously we've entered information as plain text. We're exploring the possibility of encoding <dimension>, <extent>, <genreform>, and <physfacet> subelements.
What advantages have people found to encoding these subelements separately?
Thank you for your input.
|