<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is more of an archival description question, but I’m not a member of that listserv, so I figured it would be easier to ping some of you about this for advice since I wager there’s a lot of overlap.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have not-infrequent discussions around here about what “level of description” label to assign to an archival component at a given level, i.e. collection, series, file, item, etc. But because our data is already structured in hierarchical
relationships via EAD/JSON, there’s no real need to “tell the computer” what level this is since these labels aren’t the way computers understand context and hierarchy, the nesting of data is.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Once I realized this, I often made the case that these level-of-description labels are useful for stylesheets, i.e. tell a stylesheet with level=series to make it all caps and bold, level=file should be red, etc. But the ASpace PUI doesn’t/doesn’t
need to style levels in this manner for the hierarchy to be easily understood.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So we’re considering discontinuing use of the “level of description” field in ASpace. But am I missing an important value of this field? Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jordon<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jordon Steele<o:p></o:p></p>
<p class="MsoNormal">Hodson Curator of the University Archives<o:p></o:p></p>
<p class="MsoNormal">Sheridan Libraries<o:p></o:p></p>
<p class="MsoNormal">Johns Hopkins University<o:p></o:p></p>
<p class="MsoNormal">3400 N Charles St<o:p></o:p></p>
<p class="MsoNormal">Baltimore, MD 21218<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:jsteele@jhu.edu"><span style="color:#0563C1">jsteele@jhu.edu</span></a><o:p></o:p></p>
<p class="MsoNormal">410-516-5493<o:p></o:p></p>
<p class="MsoNormal">he/him/his<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>