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

Add policy titles #97

Open
gregjd opened this issue Mar 16, 2017 · 2 comments
Open

Add policy titles #97

gregjd opened this issue Mar 16, 2017 · 2 comments

Comments

@gregjd
Copy link
Member

gregjd commented Mar 16, 2017

Those can be a combination of:

  • custom legal means (Local Law)
  • specific identifiers (Local Law 11, Executive Order 2016-1)
  • specific names (Open and Protected Data Policy)

This will eliminate the need for the legal_custom field, as well as the titles that are sometimes found at the top of policy text.

Something that should happen alongside this is filling in the standardized legal means for all policies.

@gregjd
Copy link
Member Author

gregjd commented Mar 17, 2017

Method to get titles:

  • Use all legal_custom values as the default titles
  • Look through the top of the text for each policy to see if there's an obvious title
    • Finding an automatic way of doing this would be cool but could take a while
    • Could just have a human do it

Method to get standardized legal means (once we decide on what those are):

  • For legal_custom values where there's a clear corresponding standardized category, use that
  • For the rest, someone will need to go through manually and decide

And in the future, the intake form can ask these two things separately.

@gregjd
Copy link
Member Author

gregjd commented Apr 10, 2017

If this isn't done by the summer, this "finding an automatic way" method could be an interesting task for a summer fellow.

We can't label standardized legal means until we decide on what the categories will be.

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

No branches or pull requests

1 participant