Fix for problems indexing date_range in non-compliant EAD files - #68
Open
rshiggin wants to merge 2 commits into
Open
Fix for problems indexing date_range in non-compliant EAD files#68rshiggin wants to merge 2 commits into
rshiggin wants to merge 2 commits into
Conversation
rshiggin
marked this pull request as ready for review
August 13, 2026 17:02
Member
Author
|
CI failures are
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Top chunk in each changed file is for EAD files that conform to spec (e.g.,
bhlXML includes@normalwithdate_range). Bottom chunk parses XML that is out of spec. For the most part, these are tweaked queries ported fromproduction. Tested in dev withbhl,clements, andscrc.