-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
msDesc
/additional
should always display last
#205
Comments
I've made a change so that:
I've re-indexed Medieval QA to provide some examples:
As |
This all looks good for medieval |
Just a thought: Would it be preferable for the "Digital Images" section, i.e. |
I don't think so, but it does raise the question of navigating long and complex entries 9which I don't really have an answer to: I don't really like how the Hebrew catalogue handles this (e.g. https://hebrew.bodleian.ox.ac.uk/catalog/volume_14) but maybe a stripped down version of that with just the part numbers? |
There are always edge cases. Like MS. Lat. misc. a. 3, which has 87 parts. Or MS. Bodl. 572 with parts within parts containing works with sub-works. One thing that could handle any size or complexity of description, without taking up a lot of space and cluttering the layout, would a drop-down, maybe in the top-right corner. It would jump to whatever part (or other major section?) you choose, using JavaScript. Here's a mockup: But I'm not sure how usable or accessible that would be. |
Andrew - would you be able to implement this drop down on QA so we can test it? We've got an increasing number of longer and more complex records, and I think it could be really helpful in those cases. Thanks! |
The
additional
element, as a child ofmsDesc
, contains bibliographical and administrative information relating to the record as a whole, including anymsPart
elements. The default display of this information in document order, before anymsPart
elements, is potentially confusing. Displaying this information at the end of the record will provide an improved user experience and have the incidental benefit of making it easier to usemspart
to describe endleaves.The text was updated successfully, but these errors were encountered: