Final details were small but took a long time to figure out. Among them were issues of subelements. For instance, there's a need to include the names of editors and encoders in the data, but the only tag available for this is DC.contributor, which is vague. This can be qualified, like this: DC.contributor.editor. However, there's no official set of terms for this. There was a proposal to add "editor" but it was voted down a few years ago. Therefore I've had to use my own unofficial extensions, and I'm simply basing these on the value of the <resp> element in the relevant <respStmt> tags.

Beyond that, everything is fairly straightforward, although the implementation took a little while. My plan now is to base the Web view of the metadata on the Dublin Core <meta> tags that are already in the header, parsed through JavaScript, so that (for instance) the JS code would iterate through each <meta> tag, and if its name begins with "DC.", take the string after the last dot (e.g. "editor"), upper-case the first letter ("Editor") and then show the value in the content attribute. That would make a neat little JS class that could be used for any page with DC metadata in it.