Thank you again!
I have URL encoded the doi according to this guide (https://www-doi-org.ezproxy.csu.edu.au/doi-handbook/HTML/encoding-rules-for-urls.html). I hope it works as it should now.
Thanks, we see:
Found the following (possibly) invalid DOIs: DOI: 10.1002/1097-0258(20001130)19:22<3127::aid-sim784 From: DESCRIPTION Status: 404 Message: Not Found
Unfortunately, the doi comtains a ">" char which is markup for "end of DOI". Therefore, please URLencode() the DOI.
Best, Uwe Ligges
Thank you again!
I have changed the URL to a doi.
Thanks, we see:
The Description field contains
https://onlinelibrary.wiley.com/doi/10.1002/1097-0258(20001130)19:22%3C3127::AID-SIM784%3E3.0.CO;2-M Please use permanent DOI markup for linking to publications as in .
Please fix and resubmit.
Best, Uwe Ligges
Many thanks for your time. The issues with the references should be fixed now.
Thanks, we see:
Found the following (possibly) invalid DOIs: DOI: 10.1002/1097-0258(20001130) From: DESCRIPTION Status: 404 Message: Not Found
You may have to URLencode() the above DOI.
DOI: 10.1136/bmj-2022-073141#'
From: DESCRIPTION
Status: 404
Message: Not Found
Omit the extra "'"
DOI: https://doi.org/10.1002/9780470743386.ch4'
From: DESCRIPTION
Status: 404
Message: Not Found
DOI: https://doi.org/10.1016/C2009-0-03396-0'
From: DESCRIPTION
Status: 404
Message: Not Found
DOI: https://doi.org/10.20982/tqmp.14.4.p242
From: DESCRIPTION
Status: 404
Message: Not Found
DOI: https://doi.org/10.2307/1164588
From: DESCRIPTION
Status: 404
Message: Not Found
The doi start 10...., not https which is a URL rather than a DOI.
The Description field contains Chinn S. (2000) Cochrane Cohen, J. (1977) Ellis, P.D. (2009) Hedges, L. V. (1981) Hedges L. V., Olkin I. (1985) Murad M H, Wang Z, Zhu
Stackoverflow (2018) . Please enclose URLs in angle brackets (<...>). The Description field contains Chinn S. (2000) Hedges, L. V. (1981) Hedges L. V., Olkin I. (1985) Murad M H, Wang Z, Zhu Please write DOIs as .
Please fix and resubmit.
Thank you for reviewing this package! Your work is really appreciated.
Regarding to the extend_var.Rd comment: Removed the function from the documentation since it should only be called internally. Hence, I did not add a value to the .Rd file.
All other points have been fixed.
If there are references describing the methods in your package, please add these in the description field of your DESCRIPTION file in the form authors (year) authors (year, ISBN:...) or if those are not available: with no space after 'doi:', 'https:' and angle brackets for auto-linking. (If you want to add a title as well please put it in quotes: "Title")
Please add \value to .Rd files regarding exported methods and explain the functions results in the documentation. Please write about the structure of the output (class) and also what the output means. (If a function does not return a value, please document that too, e.g. \value{No return value, called for side effects} or similar) -> Missing Rd-tags: extend_var.Rd: \value
You write information messages to the console that cannot be easily suppressed. It is more R like to generate objects that can be used to extract the information a user is interested in, and then print() that object. Instead of print() rather use message()/warning() or if(verbose)cat(..) (or maybe stop()) if you really have to write text to the console. (except for print, summary, interactive functions) -> R/ARD.R
0 errors | 0 warnings | 1 note
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.