plk
plk
2.20 is now released
2.20 is now released
The problem is that this results in incoherent sorted lists in general as the criteria isn't visible to the user and it's not obvious what it is. You can have...
So, you mean you want to use `eventdate` instead of `date` only for some types? Couldn't you just always do that or are there cases where some types would have...
You can already do that with the "sourcemapping" feature - replace/substitute fields during .bib parsing on a per-type basis. You could, for example, just copy `eventdate` into another field like...
If you can put a MWE here which demonstrated what you would like to do, I can suggest a solution with the current functionality.
You can just copy `eventdate` to `date` as that will sort first and is of the same type. It's not recommended to use the legacy `year` field whenever possible. You...
Add this to the preamble: ``` \DeclareSourcemap{ \maps[datatype=bibtex]{ \map{ \pertype{customa} \step[fieldsource=eventdate, match=\regexp{\A(\d+)}] \step[fieldset=sortyear, fieldvalue={$1}] } } } ``` This will copy the year from the eventdate into the `sortyear` field...
Actually, `year` and `sortyear` are not legacy fields in sorting templates, they are deprecated only in the actual `.bib` data files. `biber` splits up ISO8601 date fields into the date...
Yes, sorting at more granularity than year needs a custom sorting template but doesn't need to be per-type in this case - just add month and day below year and...