address encoding updates from Feb 2016 "editor mask" meetings

[paregorios]

There are a number of encoding changes envisioned as a result of discussions, which have been being discussed in email. This "epic" ticket will bind together the various subordinate issues (surfacing them from the email thread), some of which will no doubt drive XSLT and other changes, not just XML re-encoding or expansion.

Next steps:

• Create a separate issue for each "NEW" section in 59749_Example of new changes.xml
  • name for display: example ➡️ use "title" element as name for display #206
  • ancient archives/libraries in <collection>: example ➡️ this was resolved, after some changes in direction, with support Place Stored (ancient) in metadata transform #21. Issue change order in which the key components of the metadata section are presented #25 had an effect on order of display in HTML.
  • <material> in <supportDesc><support>: example ➡️ use "material" tag in <supportDesc><support> #207
  • <dimensions> in <supportDesc><support>: example ➡️ Issue: Implement support for structured dimensions in metadata editor #192
  • Information about writing style (<handDesc>): example ➡️ issue Information about writing style (handDesc) #208
  • multiple parts of papyrus in <msParts> in header: example ➡️ issue encode information about multiple parts of a papyrus in msParts #322
  • <biblScope> for a sequence of page ranges: example ➡️ issue encode multiple ranges of pages on biblScope #323
  • Alternative Authors, Quoted Authors: example
  • <bibl type="illustration">: example
• Append discussion of provenance and the ancient archive from related email thread to the corresponding ticket
• Tie together and normalize other tickets dealing with provenance, e.g., handle multiple provenances of different types (elegantly) #6

[paregorios]

The open tasks above are for me to run down. I suspect they are all dealt with now in other tickets.