Skip to content

[Concept] Automated PD Compliance#1650

Draft
JVickery-TBS wants to merge 3 commits intomasterfrom
feature/pd-compliance
Draft

[Concept] Automated PD Compliance#1650
JVickery-TBS wants to merge 3 commits intomasterfrom
feature/pd-compliance

Conversation

@JVickery-TBS
Copy link
Contributor

So the idea is that we already have all of this organization metadata on what an org needs to complete. And we already have all of the PD schemas, and direct access to the datastore via the CKAN Registry. So we can, in theory, make compliance dashboards inside of CKAN with Recombinant & DataStore.

Some general ideas on what is needed:

  • reporting_frequency key values for the PD genos;
  • any missing PDs in the org reporting_requirements;
  • view for org PD compliance, maybe select2 for PD type, then select reporting period based on reporting_frequency then show what has been reported. Put in edit links?
  • when user logs in, should see if their org has any upcoming PDs that they are missing data for, including NILs. This might be costly when user logging in, so might need some background job and database table;
  • some type of sysadmin view to show and download csv of PD compliance for a PD type

- Started proof of concept for pd compliance inside Registry.
- Started proof of concept for pd compliance inside Registry.
- Started on templates and views for organization summaries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant