Dear Cory and Michael, dear all,
thank you very much for your comments.
In the Archives Portal Europe we are thinking about not using/having
the @level attribute anymore in our profile, as the conversion from
original EAD files (any profile, various uses of the values with
different meanings) into the apeEAD profile (selection of values)
turns out quite time-consuming and this is a risk for the data
integration into our portal.
So we struggle with the "lack both a vocabulary for and agreement
about the application of terms for @level" as Michael described.
At the moment we are not using the @level attribute for any search
function or any display function in the Archives Portal Europe.
Accordingly a change in apeEAD regarding getting rid of the @level
attribute could be a solution. Another solution we are thinking about
is keeping the @level attributes as they are and maybe use them later
on for refinements. This would at least keep the information in our
systems and allow us to "make something" of it whenever we would need
That as short explanation why I search for the use cases which could
make it worth to keep the time-consuming conversion and accordingly
the @level attributes.
----- Nachricht von foxmjc <[log in to unmask]> ---------
Datum: Thu, 9 Oct 2014 19:46:20 -0500
Von: foxmjc <[log in to unmask]>
Antwort an: Encoded Archival Description List <[log in to unmask]>
Betreff: Re: Use of @LEVEL
An: [log in to unmask]
> The level attribute can also be used to drive the output from XSLT
> stylesheets as when one wants a different display for a c02
> depending on whether the component described is a subcollection,
> series, or subseries, as evidenced by the value of @level.
> There are rudimentary examples of this in the EAD Cookbook
> On the other hand, slavish application of the level attribute
> becomes less useful at more granular levels of description. Is
> that c05 a sub-sub-subseries or is it a sub-sub-sub-sub-subfile?
> Where are the attribute police when we need them?
> My observation is that we lack both a vocabulary for and agreement
> about the application of terms for @level at the more detailed
> levels of description. And even if we had, I've never seen a
> practical example of the utility of their application.
> Michael Fox
> Sent via the Samsung Galaxy S™III, an AT&T 4G LTE smartphone
> <div>-------- Original message --------</div><div>From: Susanne
> Waidmann <[log in to unmask]> </div><div>Date:10/09/2014
> 2:40 PM (GMT-06:00) </div><div>To: [log in to unmask]
> </div><div>Subject: Use of @LEVEL </div><div>
> </div>Dear all,
> EAD offers several values within the @LEVEL attribute in the <c>
> elements (class, series, subseries, file, item etc).
> Do you know any search engine, portal or websites that uses these
> attributes / values for interesting or relevant search or display
> For any input I would be thankful.
> Best regards
> Susanne Waidmann
> Referentin im Referat StA 1
> Stiftung Archiv der Parteien und Massenorganisationen der DDR im Bundesarchiv
> Finckensteinallee 63
> 12205 Berlin
> Telefon: +49 (0) 3018 7770 - 740
> Telefax: +49 (0) 3018 7770 - 111
----- Ende der Nachricht von foxmjc <[log in to unmask]> -----
Referentin im Referat StA 1
Stiftung Archiv der Parteien und Massenorganisationen der DDR im Bundesarchiv
Telefon: +49 (0) 3018 7770 - 740
Telefax: +49 (0) 3018 7770 - 111