* using log directory 'd:/RCompile/CRANincoming/R-devel/tatooheene.Rcheck'
* using R Under development (unstable) (2024-12-15 r87442 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 13.3.0
    GNU Fortran (GCC) 13.3.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* checking for file 'tatooheene/DESCRIPTION' ... OK
* this is package 'tatooheene' version '0.10.0'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Stijn Peeters <s.b.peeters@eshpm.eur.nl>'

New submission

Authors@R field should be a call to person(), or combine such calls.

The Description field should not start with the package name,
  'This package' or similar.

Found the following \keyword or \concept entries
which likely give several index terms:
  File 'depreciation_interest.Rd':
    \keyword{Generic,}
  File 'discount_value.Rd':
    \keyword{Costs,}
    \keyword{Discounting,}
  File 'discount_vector.Rd':
    \keyword{Costs,}
    \keyword{Discounting,}
  File 'friction_period.Rd':
    \keyword{Generic,}
  File 'nl_med_prices.Rd':
    \keyword{Generic,}
    \keyword{Manual,}
    \keyword{Prices,}
  File 'nl_pat_fam_prices.Rd':
    \keyword{Generic,}
    \keyword{Manual,}
    \keyword{Prices,}
  File 'nl_ppp.Rd':
    \keyword{Generic,}
    \keyword{Manual,}
  File 'nl_price_index.Rd':
    \keyword{CBS,}
    \keyword{CPI,}
    \keyword{Index,}
  File 'nl_prod_oth_prices.Rd':
    \keyword{Generic,}
    \keyword{Manual,}
    \keyword{Prices,}
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking whether package 'tatooheene' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking contents of 'data' directory ... OK
* checking data for non-ASCII characters ... OK
* checking LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking examples ... OK
* checking PDF version of manual ... [20s] OK
* checking HTML version of manual ... OK
* DONE
Status: 1 NOTE