ParagraphStyle Domain: Match Examples from GeMS Document?

[dmirandaUSGS]

I saw in the latest release that Create Database now includes a ParagraphStyle domain for the DMU. This sounds like it could be quite helpful for standardizing to some extent, how this field is populated. Tracey Felger and I had two thoughts about the implementation:

Have codes/descriptions reflect the GeMS Document

For the domain codes and descriptions that are similar to the examples found in the GeMS Document, would be possible to have them match? For example::

• DMUUnit1, DMUUnit2 instead of DMU Unit 1, DMU Unit 2.
• DMUHeading1, DMUHeading2 instead of DMU-Heading1, DMU-Heading2

Provide definitions in the Glossary for ParagraphStyle domain codes/values

Much in the way that certain and questionable are defined in the Glossary if standard confidence are included, would it be possible to include definitions in the Glossary for the ParagraphStyle values?

[ethoms-usgs]

Ok, so the codes in the new domain match the style names that are found in \Resources\DMU_Template.docx which is based off MapManuscript_v3-1_06-22.dotx, the Word template that Taryn Lindquist told me is the authoritative template for USGS editors as of now. And even the older template that Ralph based his first tool on, and which was the basis for the ParagraphStyles that made it into the GeMS document as examples, uses, more or less, the same style names. That is, I don't know why the examples that are in the GeMS document are what they are. It may be because the names of the styles as they are saved in the xml-version of the document have no spaces, but the best practice with the python module (docx) that the tool uses to build the Word doc is to use the name as it appears in the Styles section in Word.

Also, the new DMU to DOCX tool can accept styles like 'DMU Unit 1' or 'DMUUnit1' because of a dictionary that tries to match what's found in the table with what is needed for the Word doc. I can add other variations as needed.

Of course, I thought about adding Glossary definitions for the styles, but I didn't have text descriptions of them yet and I figured I would kick the can until I get back to working on metadata. But I just figured out how to print style properties from a document, so I will add that to the queue.

[dmirandaUSGS]

Ok, we are convinced that the domain values make sense since they are directly from MapManuscript_v3-1_06-22.

And, thanks for putting the Glossary entries in the queue! Ultimately, this will make things easier for us and others in the long run, so we appreciate the upgrades.