Open ebeshero opened 6 years ago
@lmwilson To read the Mitford ODD documentation and look up our project elements, you can point a web browser here for the Project ODD: https://digitalmitford.github.io/DM_documentation/MitfordODD/mitfordODD.html
We can think of that link (https://digitalmitford.github.io/DM_documentation/MitfordODD/mitfordODD.html ) as our Digital Mitford project gateway to the TEI. You can find your way to the TEI Guidelines and chapters from within our ODD and see how we're customizing the elements and attributes for the project on the same page--it's basically our customized TEI look-up on the web.
@ebeshero @lmwilson I'm going to post a Word file of occupations in Box, in the SI folder.
@lmwilson Here's a recap to help us both take stock of where we are! While I was visiting you, I was working on two schema files for our project which we're now testing:
1) The new schema for the si and si_Add files to codify the new occupation element and its
@type
and@subtype
and the revised@sortKey
(That's in the DM_SiteIndex repo and you and I are currently testing that schema on the si_Add files and a locally copy of the full SI. The schema is a local association--just sitting in your local GitHub directory. If I push changes to that schema, you'll get them when you do agit pull
).@sortKey
and simplify ourlistBibl
lists according to what we worked out on the full SI, and I need to find a new way for us to code the Mitford editing team lists so we're not using the<occupation>
element to list where we work.si_Add
files and making sure the schema the new SI schema is working the way we expect it to when we're preparingsi_Add
files for addition to the new SI.2) The other ODD schema I'm developing is for the full project team working on edition files. This is the Digital Mitford Project ODD and it's posted now on this
DM_documentation
repo (where I'm posting this ticket). We're still testing this schema, too--it's not quite ready for release on all the project files. Here are some instructions on how to access and test this schema for now (and we'll turn this into formal documentation after a little more testing):?xml
line at the very top alone--don't delete it. Just comment out all the other schema lines, including the ones associated with the TEI-All, so we can put them back if we want to and compare the old schema checking to the new one.)Schema lines:
Things to work on might include proofing/correcting/refining the validation messages, in addition to making sure stuff works as we expect! Once we're pretty confident things are working, we'll associate these schemas on all our files and get the full team working with them.