-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This check the output file name not the data value in the data frame #126
Comments
I realised that it can be renamed after output by |
I have investigated this issue.
The check is performed on the filename used to name the XPT file. This name is a metadata in the xpt and it is not updated when the XPT filename is changed.
The underscores are allowed in xpt but it was not allowed in FDA sdTCG. I checked the latest version of the FDA sdTCG and it is not clear if underscores are allowed or not. FDA sdTCG Version October 2023 I tested the conversion from XPT to SAS7BDAT with SAS, and I observed that the name of the dataset is derived from the metadata name, not the file name. If the filename is renamed, the SAS dataset is not renamed. I think using the filename as the name of the xpt is a good approach. This is also requested in the FDA sdTCG . I don’t think we can do anything regarding the change of the xpt name when the filename is renamed. Something to check, if underscores are allowed or not. And, update the name check accordingly in |
@cpiraux So we can close this issue as out of scope and make an additional issue regarding underscores? |
@cpiraux Thank yor for detailed explanation. my suggestion is if we can add |
Closes #126 - Update check for filename to allow underscore
https://github.com/atorus-research/xportr/blob/231e959b84aa0f1e71113c85332de33a827e650a/R/write.R#LL33C1-L33C82
Could you please confrim this check refer to the output file name not the data value?
For the file name, if the DM_F can be used when the
strict_checks = FALSE
,and the DM_F means the full SDTM that contains the parent DM and SUPPDMThank you very much.
The text was updated successfully, but these errors were encountered: