This is a fork of the official CKAN repository. This fork is being used for internal IDM purposes and not for public distribution. CKAN is an open-source DMS (data management system) for powering data hubs and data portals. CKAN makes it easy to publish, share and use data. It powers datahub.io, catalog.data.gov and europeandataportal.eu/data/en/dataset among many other sites.
UPDATE:
This task will track the collection of HIPAA info and updating Data Catalog to capture that info. The info will be collected manually by talking to researchers and entered into Data Catalog either manually.
CONTEXT:
Per conversation with Rob and Chris Werry, Dropbox and IV have both define special constraints around HIPAA data (Health Insurance Portability and Accountability Act) which includes PHI (Protected Health Information.) and PII (Personally identifiable information).
The action item for this project is to track this information for all datasets. Therefore, we need to add a field and make it required (drop down not a checkbox), so that researchers must declare whether a dataset contains HIPAA data.
In the context of parsing README files, we should be able to produce a report of datasets which don't have such a field in their README, so that we can follow up with maintainers and collect that information.
UPDATE: This task will track the collection of HIPAA info and updating Data Catalog to capture that info. The info will be collected manually by talking to researchers and entered into Data Catalog either manually.
CONTEXT: Per conversation with Rob and Chris Werry, Dropbox and IV have both define special constraints around HIPAA data (Health Insurance Portability and Accountability Act) which includes PHI (Protected Health Information.) and PII (Personally identifiable information).
The action item for this project is to track this information for all datasets. Therefore, we need to add a field and make it required (drop down not a checkbox), so that researchers must declare whether a dataset contains HIPAA data.
In the context of parsing README files, we should be able to produce a report of datasets which don't have such a field in their README, so that we can follow up with maintainers and collect that information.