Skip to content
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 curation exploration #145

Draft
wants to merge 26 commits into
base: main
Choose a base branch
from
Draft

Data curation exploration #145

wants to merge 26 commits into from

Conversation

jadudm
Copy link
Contributor

@jadudm jadudm commented Aug 28, 2024

Submitting this as a draft PR for reference. Branch render.

This PR provides exemplars of several things that may be of use/interest in the future.

  1. It provided draft text regarding data curation, including a draft process that would include our advisory committee and OMB.
  2. A framework for creating individual data issue files (largely templated) for documenting data curation concerns. Five known concerns are documented using this format as an example.
  3. An associated RSS/Atom feed for data concerns, so partner agencies and the public can subscribe to notices about data concerns as they are found/documented.
  4. A framework for documenting data curation actions (again, templated) so that fixes can be communicated/documented in a standard way.
  5. An associated RSS/Atom feed for curation actions.
  6. The branch demonstrates how our updates page could be converted to individual files, the updates page could be automatically generated from those files, and an RSS and Atom feed generated from those updates. (Example RSS feed)

The curation process may be of interest as the starting point for an ADR regarding how to curate data in a manner that is transparent and maintains the trust of our partner agencies as well as the public.

Offered as a draft for reference only; it can be closed as "not planned" as work proceeds elsewhere.

jadudm added 26 commits June 27, 2024 07:36
Includes JSON files that support some of the "how are things validated"
questions we will probably want to answer.

Committed for reference/discussion. Can be deleted when we have things
in place.
But, the nav is in the wrong place...
And, found a new one.
This introduces a new way to do the URLs.

It changes the build.

Adds more migration content.
Add URLs to glossary for consistency, fix URLs in tables.
Lots of config file changes, trying to make them consistent.

Would be nice if we could make it conditional based on env, so we only
had one
Tested with a command-line reader. More testing required, but the feeds
are compliant enough to be et.
:
This is tough, as the pages stand alone and are embedded.

This is the best approach I have at the moment.
There are pages with a lot of detail regarding validations, etc.

I've commented those out in this version. Why? Because those pages may
not be necessary, or may want more review, etc.

I think they're important, but we're aiming for an MVP.
Or, the baseURL is broken. Unsure.
Still working on why this does/doesn't work.
One step at a time.

We need a consistent way to reference URLs in our site.
Need to anchor the slugs correctly.
Making it work in branches.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant