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

Standardize a set of metadata that would be useful to scan a server and build an index of interviews for a site like courtformsonline.org #534

Closed
nonprofittechy opened this issue Jul 8, 2022 · 2 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@nonprofittechy
Copy link
Member

Or is it enough to scan all of the YAML files in the data/questions folder and see if we can find the metadata block?

Can we automate adding this file via PR to people's repos?

@nonprofittechy nonprofittechy changed the title Create a standard metadata file that can be put in the github repo Standardize a set of metadata that would be useful to scan a server and build an index of interviews for a site like courtformsonline.org Sep 12, 2022
@nonprofittechy
Copy link
Member Author

After looking into this more, the /list?json=1 endpoint will display the contents of a file's metadata block. So that's really where we should be focusing, not creating a new file.

@nonprofittechy nonprofittechy added the enhancement New feature or request label Sep 12, 2022
@nonprofittechy nonprofittechy added the duplicate This issue or pull request already exists label Aug 22, 2023
@nonprofittechy
Copy link
Member Author

This should include some information that helps track whether a form is up to date. A2J author calls this "citations".

From discussion today, it should be mostly an unstructured field. But we could nudge authors to include things like:

  1. Original court form number + date published
  2. Fee amounts (courts revise fee schedules)
  3. Original up to date law check (not exactly the same as the last date the GitHub repo was touched)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant