Make DQD available on CRAN

[AlexKnightHDR]

Some OMOP users operate in environments which are very strictly "locked down" in terms of what can be installed and run within them. For example, I understand that in the UK the National Health Service Secure Data Environment can only install packages that are available through CRAN.

I'm not sure how onerous the requirements are for submitting a package to CRAN, but it would make DQD - and hence high-quality OMOP data - available to users working in these environments - where the security is extremely tight but the data sets are large and the potential impact high!

[katy-sadowski]

Getting on CRAN is on our roadmap! The main blocker right now is the size of the package; the Shiny app was implemented in such a way that it takes up a lot of space. However, we're in the early stages of planning a v3 release which will include an overhaul of the user interface and hopefully with it a major slimming down of the code in this package (and ultimately, a submission to CRAN 😄 ).

Thanks very much for filing this issue and letting us know about your use case.

[AlexKnightHDR]

[like] Alex Knight reacted to your message:

…

________________________________ From: Katy Sadowski ***@***.***> Sent: Wednesday, December 6, 2023 2:46:04 AM To: OHDSI/DataQualityDashboard ***@***.***> Cc: Alex Knight ***@***.***>; Author ***@***.***> Subject: Re: [OHDSI/DataQualityDashboard] Make DQD available on CRAN (Issue #514) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Getting on CRAN is on our roadmap! The main blocker right now is the size of the package; the Shiny app was implemented in such a way that it takes up a lot of space. However, we're in the early stages of planning a v3 release which will include an overhaul of the user interface and hopefully with it a major slimming down of the code in this package :) Thanks very much for filing this issue and letting us know about your use case. — Reply to this email directly, view it on GitHub<#514 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7YNLPYQ6JJCKY7YS3DEPN3YH7L6ZAVCNFSM6AAAAABAHOEKEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBRHE4TOMBSGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>