Draft
Conversation
- 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_frequencykey values for the PD genos;reporting_requirements;reporting_frequencythen show what has been reported. Put in edit links?