datefixR
Standardize Dates in Different Formats or with Missing Data
Description
There are many different formats dates are commonly represented with: the order of day, month, or year can differ, different separators ("-", "/", or whitespace) can be used, months can be numerical, names, or abbreviations and year given as two digits or four. 'datefixR' takes dates in all these different formats and converts them to R's built-in date class. If 'datefixR' cannot standardize a date, such as because it is too malformed, then the user is told which date cannot be standardized and the corresponding ID for the row. 'datefixR' also allows the imputation of missing days and months with user-controlled behavior.
Downloads
774
Last 30 days
4643rd
2.2K
Last 90 days
7.4K
Last year
Trend: -4.4% (30d vs prior 30d)
CRAN Check Status
Show all 14 flavors
| Flavor | Status |
|---|---|
| r-devel-linux-x86_64-debian-clang | NOTE |
| r-devel-linux-x86_64-debian-gcc | NOTE |
| r-devel-linux-x86_64-fedora-clang | NOTE |
| r-devel-linux-x86_64-fedora-gcc | NOTE |
| r-devel-macos-arm64 | OK |
| r-devel-windows-x86_64 | NOTE |
| r-oldrel-macos-arm64 | NOTE |
| r-oldrel-macos-x86_64 | NOTE |
| r-oldrel-windows-x86_64 | OK |
| r-patched-linux-x86_64 | NOTE |
| r-release-linux-x86_64 | OK |
| r-release-macos-arm64 | OK |
| r-release-macos-x86_64 | OK |
| r-release-windows-x86_64 | OK |
Check details (8 non-OK)
compiled code
File ‘datefixR/libs/datefixR.so’:
Found non-API calls to R: ‘R_NamespaceRegistry’, ‘R_Srcref’,
‘R_UnboundValue’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
compiled code
File ‘datefixR/libs/datefixR.so’: Found non-API calls to R: ‘R_NamespaceRegistry’, ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
compiled code
File ‘datefixR/libs/datefixR.so’: Found non-API calls to R: ‘R_NamespaceRegistry’, ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
compiled code
File ‘datefixR/libs/datefixR.so’:
Found non-API calls to R: ‘R_NamespaceRegistry’, ‘R_Srcref’,
‘R_UnboundValue’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
compiled code
File 'datefixR/libs/x64/datefixR.dll':
Found non-API calls to R: 'R_NamespaceRegistry', 'R_Srcref',
'R_UnboundValue'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.
installed package size
installed size is 6.8Mb
sub-directories of 1Mb or more:
libs 5.8Mb
installed package size
installed size is 6.6Mb
sub-directories of 1Mb or more:
libs 5.6Mb
compiled code
File ‘datefixR/libs/datefixR.so’:
Found non-API calls to R: ‘R_MissingArg’, ‘R_NamespaceRegistry’,
‘R_Srcref’, ‘R_UnboundValue’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Check History
NOTE 12 OK · 2 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Mar 10, 2026
installed package size
installed size is 6.8Mb
sub-directories of 1Mb or more:
libs 5.8Mb
installed package size
installed size is 6.6Mb
sub-directories of 1Mb or more:
libs 5.6Mb