Skip to content

Optional parsing of unitdate strings #1623

@alexduryee

Description

@alexduryee

Records that don't have a unitdate@normal attribute don't get date_range_isim fields, which causes the records to not appear when using the date search facet. For example, a component with <unittitle>Sample Record</unittitle><unitdate>1990</unitdate> in its EAD XML won't appear when searching for sample record and a date range of 1980-2000.

Support for non-@normal date searching could be added by pulling all four-digit numbers from unitdate, sorting them, and storing the bottom/top values in date_range_isim. This won't capture all non-normalized dates, but would provide year-level specificity for most dates that are only stored as text values.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions