Closed kstapelfeldt closed 2 years ago
After running tests Date Range Widget (in Advanced Search) some of below ETDF date values:
The Solr processor which are included in Control Access Term module can recognize the above EDTF format (even with uncertainty ones with '%' and '~') and the Advanced Search can produce the search result regards to the Range Year.
==> We can keep using our current approach in the metadata.
Small Note: Date Range format is not enabled by default in Form Display in the module, a small adjustment need to be done in the Widget Configuration (more documentation at https://islandora.github.io/documentation/user-documentation/metadata)
Thanks Kyle! I'm going to move this to complete now.
The Solr search date-range filter currently gets a unique start and end date that is a lossy version of the RAD text date provided in the GMP. [For example: Winter, 1996 is RAD and we provide 12/21/1996]
ETDF provides us with the ability to encode other features of the date as machine readable, including uncertainty (ca.1986 becomes 1986~) and extended support for ranges as a single field. So, for example, instead of saying "Start date: 12/21/1996 and End date: 12/21/2001" it does something like "1996-12-21/2001-12-21."
We're changing our metadata. Should we keep our current approach of providing a separate lossy date in the metadata for machine purposes, or can we use ETDF's uncertainty and range support in our metadata and expect the Solr date range filter to work.
https://www.loc.gov/standards/datetime/ https://digital2.library.unt.edu/edtf/ Full ETDF Specification https://utoronto.sharepoint.com/:b:/s/utsc-library/EQpLvOHfFwhKnJ6kf3Y6MBMBqU9Y2Re1g6Sy5wgkTwmZjQ?e=Bxz7Ec)