Header for the whole thing:

--double the width of the top green bar, and place the shelfmark on it, in the same size and weight font as the city+institution+library information above it -- OK

--put the link to "View All Images for this Manuscript" on that same second green bar. -- OK

Manuscript level:

--Nickname: I forgot this field. It's not used very often, e.g. in Columbia's 1444 records it only occurs once, and even then it's quite short. I think that it could go on the same second green line that would thereby look like this:

BP.096 [ 6-8 blank spaces?] Phoenix Hours [more blank spaces] "View all Images of this Manuscript." -- PREFER AS PART OF DESC.

--Physical Issues: I forgot this field. It doesn't need a label; it can go inside the present paragraph, directly after the Folios and before the Binding, using the same dash as divider. -- OK

Part level:

--top line that now has as label "Place / Date"; change this to "Place and Date" (it's not an either/or or even an and/or situation) -- OK

--top line: put a comma, not a semicolon between the data for Country and for Date -- OK

--Watermark: I forgot this field. When present, it would occur after Support, i.e. in the present configuration (the sample using X242.1.S) it would occur after "Paper" (with a comma connecting the Support and the Watermark), and it would occur before "ff. 1-213" and occupy about ½ a line; it would not need a label. -- OK

--Artist: I forgot this field. When present, it will be a pretty short field (but I don't know what could go on the same line with it), and it should precede Figurative Decoration (see next comment) --OK

--label that now says "Representational Decoration": change it to Figurative Decoration -- OK

Text level:

--the only required field is Range Of Folios (or Folios in the old ds-access), so there's not much to go on --OK

--the author/title information clusters in what may be two main groups which only occasionally overlap (in Columbia's data they overlap 39 times out of 2006 texts; for NYPL there are 14 overlaps in 341 records):

1. Author, Associated Name, Title

2. Generic Title

I could make a point of eliminating this sort of overlap for the databases that I can get access to, if that's helpful. It may be a moot point, since apparently it's possible to arrange for non-display of fields with no content. -- OK AS IS

--at any rate: make the labels read: Author; Associated Name (in the db as Other Associated Name); Title AND Title again for what in the db is Generic Title (but we're making that distinction pretty well invisible to the user). Thus:

Author: Livy

Title: Decades

or: Author: Ovid

Associated Name: Octavien de St. Gelais, translator

Title: Heroides

or: Title: Breviary ---

or: Title: Rent receipt

or: Title: Zerstreuung einer gemeiner Handschrift. OK TO HANDLE AS IN SCHEMATIC??

Title: Calligraphy e.g., Title: [Calligraphy] Zerstreuung einer gemeiner Handschrift.

I don't think that any of these four fields is very long, so it might be possible to use them in tabular format:

Author:	Associate Name:
Title:	Title:

--Docket (with that label), when present is quite long, in the form of a full sentence, and it may need to wrap to the next line. -- OK

--the next cluster are the quotes of salient texts from the manuscript, each needing a label and a full line; of the three, the middle one (Incipit) is the most likely to have content:

1. Rubric

2. Incipit

3. Explicit

Is it possible to put an ellipsis on the end of Incipit, and one at the beginning of Explicit? -- OK

--Languages may be a fairly short line; could it go on the same line as Status of Text (see next comment)?

--Status of Text isn't a great label; its content is material of this sort:

Alphabetical subject index and text itself beginning defectively. -- NOTES ON CONDITION

ff. 33-36v added in a contemporary hand. -- NOTES ON THE COPY

Fragment; worn along central fold; recto entirely erased.

The 8th quire, ff. 57-64, misbound.

Any better ideas of what to call it? One could leave the label off (since readers hardly need to be taught to consider it as a searchable field), but since all the other fields of the Text level will have labels, it's hard to not put any here.

--Notes needs its label and a full line, as on other levels. -- OK

--Acknowledgments needs its label and a full line, as on other levels. -- OK

--Link is a field for someone to insert a link to something else on the web that pertains to the text in question; it's a new field, so far no one has used it. -- OMIT FOR NOW

Images:

--it's good the way you've done it, putting the caption on the same line as the folio number; could we add some space between the two, though? -- OK esp. when the "folio number" is something like "Binding" and then that has a caption, it looks somewhat awkward.