https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24807
--- Comment #31 from Julian Maurice <[email protected]> --- (In reply to Nick Clemens from comment #30) > From what little I understand there, UNIMARC uses '#' as the unkown > character? or '#' translates to blank? I think that '#' translates to blank. UNIMARC cataloguing plugin for 100$a in Koha uses spaces. > leading blanks should be preserved as 0? I think so. > and trailing ranged as you say below? I don't know... > > > - Replacing the uncertain character by 0 can be problematic. 197u is not > > 1970. Ideally, searching for records published in 1975 should return records > > where publication date is "197u", right ? Elasticsearch has an integer_range > > data type that could be useful in this situation. What do you think ? > > That is interesting, how does the range affect sorting? Might it still be > worthwhile to sort unknown/ranged dates either at start or end, so file the > sort value as either 1970 or 1979? I have not tested integer_range yet. Rethinking about this, maybe replacing "uncertain" by 0 is good enough for now. Support for uncertain dates as ranges can be added later. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
