These changes represent minor typos/glitches that I've found in the XML files while testing the ingest system and generally reviewing the data.
I don't think any of these represent any larger issues, simply edge cases that have cropped up.
The one issue I am unclear on what happened with is the 1936 value which has inserted a row of hashes, rendering the file and that entry as invalid XML. It does not appear to have any correspondence to the page in the original volume, so I am not sure how that happened.
These changes represent minor typos/glitches that I've found in the XML files while testing the ingest system and generally reviewing the data.
I don't think any of these represent any larger issues, simply edge cases that have cropped up.
The one issue I am unclear on what happened with is the
1936value which has inserted a row of hashes, rendering the file and that entry as invalid XML. It does not appear to have any correspondence to the page in the original volume, so I am not sure how that happened.