plk

The `*date` fields don't exist outside of the data files as they are parsed into their components (e.g `year` and `sortyear`). We have thought about sorting by month/day after year...

Put the template below in your preamble and set the package sort option: `sorting=ntymd` ``` \DeclareSortingTemplate{ntymd}{ \sort{ \field{presort} } \sort[final]{ \field{sortkey} } \sort{ \field{sortname} \field{author} \field{editor} \field{translator} \field{sorttitle} \field{title} }...

@moewew - What's your view on this? It would be possible to add add month/day to all default sorting templates with little impact but it could change the sort order...

I think there is a case to be made here that granular date sorting should be the default as it is what people expect when they have month/day in there...

Well, the general principle is that we don't want to change existing documents to the extent that we can do that. Adding month/day would change the sort order of some...

I would want to make the sorting determinable from the visible information in the sorting templates, not invisible in an option that `biber` used in the background as that just...

I was thinking of an "all or nothing" option - it's either just year, or it's everything. I can't see any real use-case for anything in between.

I think it's fine to add a driver source map for this.

The problem with inheriting `option` and `annotations` with xdata is that you can have cascading and multiple inheritance - should such fields be merged, overwritten etc. when they conflict? This...

Annotations should now be inherited via XDATA in `biber` 2.20 DEV version. It also takes care of remapping xdata granular indices across entries. You can test with `biber` 2.20 DEV...