Closed MomoMoses closed 3 years ago
UC calls this section "DESCRIPTIVE SUMMARY". It is available in the sidebar, and the sub-element "Abstract" is given a nav link. (I'm not sure that's essential -- the abstract link--as long as the top section is linked.
This is your call, so please let me know if you'd like to implement this. In the regularization step of our EAD-to-HTML transformation, I add "implied" head tags to certain sections. For example, if an abstract element is present without a head element, I give it a header with the text "Abstract".
The initial chunk of information is the did element at the top of the archdesc. It's allowed to have a head element, so if you'd like I could add one where they're missing in the regularization step.
Please let me know if I should go ahead and add that. If you'd prefer to tag this "design" or "research" just let me know.
In fact UChicago sets it up like this: <archdesc level="collection">
<did>
<head>
Descriptive Summary</head>
I suppose we could leave it as is for repositories that do use the heading, so as to respect their choices, and add our own choice for the "implied" heading. (I like that approach, btw.)
The ACLU guide does have a label for the abstract element.
I think we could implement and just see if anyone notices or talks about it in later user research. That is, if we end up liking the results.
This is now fixed in https://github.com/johnjung/bmrcportal/commit/9f734f3a0c6da1330a409c6b4af030145c95935a. Please confirm that it looks good and I'll close this issue out.
I'm going to close this issue out. Please re-open if necessary.
This looks good - maybe tag it with "research" so that we check it with users.
Aaron H. Payne papers (UIC) is the example. ISSUE: Should this initial chunk of info have a section heading, i.e. "OVERVIEW" so that it looks and behaves like the other sections? It would then have a nav link in the LH sidebar -- this could actually be useful as a sort of "back to the top" link if one was lost in the weeds of a long inventory. :)