Skip to content
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

recommended export options #17

Closed
aghaynes opened this issue May 9, 2019 · 6 comments · Fixed by #119
Closed

recommended export options #17

aghaynes opened this issue May 9, 2019 · 6 comments · Fixed by #119
Projects

Comments

@aghaynes
Copy link
Member

aghaynes commented May 9, 2019

Add a screen shot with recommended export options

@PatrickRWright
Copy link
Collaborator

Do we have agreement on what those should be?

@aghaynes
Copy link
Member Author

I dont think so, but I would suggest something like this
image
I'm not sure about the parts in yellow though. They can be useful sometimes
Shorten names I'm not so concerned about, as secuTrialR handles that either way.
Character Encoding might be an issue - UTF-8 perhaps?
Maybe it would be good to mention the date-time defaults, as that will avoid introducing NAs and the user then has control over what it is entered if something is missing, rather than us...

@PatrickRWright
Copy link
Collaborator

I think UTF-8 is good. Once we have agreed on the recommended set we should maybe also add an FYI warning when the export is being loaded and some things differ.

@aghaynes
Copy link
Member Author

Sure. Most of that can then go into the export options function I suppose...
Did you agree with my suggestion then or would you go a different route?

@aghaynes aghaynes added the question Further information is requested label May 20, 2019
@PatrickRWright
Copy link
Collaborator

I just had another look at this and think "Queries and Comments", "SDV", "Missing Values" and "Audit trail" can all be ticked too.

@aghaynes
Copy link
Member Author

as recommended? I'm not so convinced. They're very specific and not useful for a whole lot (normally). The audit trail gives particular difficulties with dates, factors etc as you have to assume that any form beginning with at is an audit trail, although there may be hacks to get around that. It also slows down exports dramatically (particularly for large databases).
Is missing value the MIV file? Might that be another way to do this missing data thing you're currently doing with that other validation export....?
I have no idea what SDV (source data verification) would be useful for.

@markomi markomi added this to New in dev Jul 16, 2019
@PatrickRWright PatrickRWright removed the question Further information is requested label Nov 15, 2019
dev automation moved this from New to Done Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
dev
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants