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

Data Catalogs as Spreadsheets and Participate in Meetups for Feedback on Data Science on HHS Data Sets #36

Closed
brandniemann opened this Issue Jun 3, 2015 · 4 comments

Comments

Projects
None yet
4 participants
@brandniemann

brandniemann commented Jun 3, 2015

Chris, David, and Damon, Thank you for an excellent DataLab session at HDP 2015.

My suggestions are:

Provide Health.data.gov and cms.data.gov data catalogs in spreadsheet format with web links to metadata, data, and data dictionaries; and

Participate in our Federal Big Data Working Group Meetups to provide feedback to agencies and OMB on data science results (e.g. our USDA Data Science MOOC is our more recent best practice example):http://www.meetup.com/Federal-Big-Data-Working-Group/events/221457264/.­ Best regards, Brand

@dportnoy

This comment has been minimized.

Show comment
Hide comment
@dportnoy

dportnoy Jun 6, 2015

Member

@brandniemann Thank you for your entry. Will process shortly.

Member

dportnoy commented Jun 6, 2015

@brandniemann Thank you for your entry. Will process shortly.

@marks

This comment has been minimized.

Show comment
Hide comment
@marks

marks Jun 20, 2015

@brandniemann - some of what you are looking for should be in the Project Open Data files for data.cms.gov (at http://data.cms.gov/data.json) and healthdata.gov (https://healthdata.gov/data.json).

You might also want to check out the Project Open Data project at https://project-open-data.cio.gov/v1.1/schema/ to advocate for more metadata fields such as data dictionaries, etc. to be included in the standard

marks commented Jun 20, 2015

@brandniemann - some of what you are looking for should be in the Project Open Data files for data.cms.gov (at http://data.cms.gov/data.json) and healthdata.gov (https://healthdata.gov/data.json).

You might also want to check out the Project Open Data project at https://project-open-data.cio.gov/v1.1/schema/ to advocate for more metadata fields such as data dictionaries, etc. to be included in the standard

@dportnoy dportnoy added use case and removed use case labels Jul 16, 2015

@dportnoy dportnoy removed the use case label Sep 27, 2015

@dportnoy

This comment has been minimized.

Show comment
Hide comment
@dportnoy

dportnoy Oct 18, 2015

Member

@brandniemann, thank you for your suggestion.

+1 on @marks comment noting that there's a well defined DCAT-complaint schema described at https://project-open-data.cio.gov/v1.1/schema/. It's used throughout all of federal government and harvested up to http://data.gov.

However, there hasn't been wide adoption of indexing of the field-level data dictionary. If there are sufficient resources, we would like to eventually add this capability to HealthData.gov. Doing so would also provide for a more powerful discovery at the field level and enable a feature that assists in linking across datasets. Adding semantic tagging to field definitions would make it even more powerful. I've written a couple posts on this topic:


That said, your entry is categorized as a general suggestion. It must me noted that to be a workable use case, a request must be achievable, measurable, and specific, with a well defined value proposition. So working within the context of a DDOD use case, we need to close this item. Thank you for your involvement and being such an active participant in the user community. Your suggestions are always welcome.

Member

dportnoy commented Oct 18, 2015

@brandniemann, thank you for your suggestion.

+1 on @marks comment noting that there's a well defined DCAT-complaint schema described at https://project-open-data.cio.gov/v1.1/schema/. It's used throughout all of federal government and harvested up to http://data.gov.

However, there hasn't been wide adoption of indexing of the field-level data dictionary. If there are sufficient resources, we would like to eventually add this capability to HealthData.gov. Doing so would also provide for a more powerful discovery at the field level and enable a feature that assists in linking across datasets. Adding semantic tagging to field definitions would make it even more powerful. I've written a couple posts on this topic:


That said, your entry is categorized as a general suggestion. It must me noted that to be a workable use case, a request must be achievable, measurable, and specific, with a well defined value proposition. So working within the context of a DDOD use case, we need to close this item. Thank you for your involvement and being such an active participant in the user community. Your suggestions are always welcome.

@brandniemann

This comment has been minimized.

Show comment
Hide comment
@brandniemann

brandniemann Oct 19, 2015

David, Thank you. I have found a way to do this semantic linking and index searching in Spotfire and will show that for the DataAct Data sets at our November 16th meetup:

http://www.meetup.com/Federal-Big-Data-Working-Group/events/225137696/

Best regards, Brand

From: David X Portnoy [mailto:notifications@github.com]
Sent: Saturday, October 17, 2015 11:10 PM
To: demand-driven-open-data/ddod-intake ddod-intake@noreply.github.com
Cc: brandniemann bniemann@cox.net
Subject: Re: [ddod-intake] Data Catalogs as Spreadsheets and Participate in Meetups for Feedback on Data Science on HHS Data Sets (#36)

@brandniemann https://github.com/brandniemann , thank you for your suggestion.

+1 on @marks https://github.com/marks comment noting that there's a well defined DCAT-complaint schema described at https://project-open-data.cio.gov/v1.1/schema/. It's used throughout all of federal government and harvested up to http://data.gov.

However, there hasn't been wide adoption of indexing of the field-level data dictionary. If there are sufficient resources, we would like to eventually add this capability to HealthData.gov. Doing so would also provide for a more powerful discovery at the field level and enable a feature that assists in linking across datasets. Adding semantic tagging to field definitions would make it even more powerful. I've written a couple posts on this topic:


That said, your entry is categorized as a general suggestion. It must me noted that to be a workable use case, a request must be achievable, measurable, and specific, with a well defined value proposition. So working within the context of a DDOD use case, we need to close this item. Thank you for your involvement and being such an active participant in the user community. Your suggestions are always welcome.


Reply to this email directly or view it on GitHub #36 (comment) . https://github.com/notifications/beacon/AA-W4CWyS9g5FJuqrwuqHCSKIFcUNKzWks5o8wUNgaJpZM4E2H4z.gif

brandniemann commented Oct 19, 2015

David, Thank you. I have found a way to do this semantic linking and index searching in Spotfire and will show that for the DataAct Data sets at our November 16th meetup:

http://www.meetup.com/Federal-Big-Data-Working-Group/events/225137696/

Best regards, Brand

From: David X Portnoy [mailto:notifications@github.com]
Sent: Saturday, October 17, 2015 11:10 PM
To: demand-driven-open-data/ddod-intake ddod-intake@noreply.github.com
Cc: brandniemann bniemann@cox.net
Subject: Re: [ddod-intake] Data Catalogs as Spreadsheets and Participate in Meetups for Feedback on Data Science on HHS Data Sets (#36)

@brandniemann https://github.com/brandniemann , thank you for your suggestion.

+1 on @marks https://github.com/marks comment noting that there's a well defined DCAT-complaint schema described at https://project-open-data.cio.gov/v1.1/schema/. It's used throughout all of federal government and harvested up to http://data.gov.

However, there hasn't been wide adoption of indexing of the field-level data dictionary. If there are sufficient resources, we would like to eventually add this capability to HealthData.gov. Doing so would also provide for a more powerful discovery at the field level and enable a feature that assists in linking across datasets. Adding semantic tagging to field definitions would make it even more powerful. I've written a couple posts on this topic:


That said, your entry is categorized as a general suggestion. It must me noted that to be a workable use case, a request must be achievable, measurable, and specific, with a well defined value proposition. So working within the context of a DDOD use case, we need to close this item. Thank you for your involvement and being such an active participant in the user community. Your suggestions are always welcome.


Reply to this email directly or view it on GitHub #36 (comment) . https://github.com/notifications/beacon/AA-W4CWyS9g5FJuqrwuqHCSKIFcUNKzWks5o8wUNgaJpZM4E2H4z.gif

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment