re: appointed date (see US Attorneys)

Convert .json dates to human-friendly month day, year format
(conversely: change .json dates to human-friendly format. potential issue: organization)

Updating this old issue to serve as a base for new requests regarding additional filters.

We currently have a very simple filtering system which filters by role:

Now that we are collecting more demographic data, it would be great to have an additional filter to show the range (or lack of) of location, party, gender, race, age, etc.

Here is a screenshot from a prototype I created a few years ago:

While this new additional filter does not have to look like the prototype pictured above, it would be nice to have something with similar functionality.

I've created new issues for the following elements of the filter. Please choose one to contribute to, & I will assign you accordingly:

• Location: State (#109 - assigned to @erinborders)
• Appointed (#110 - assigned to @megabyte98)
• Party Affiliation (#111)
• Age Range (#112)
• Race Closed by @shariq1989 with #140
• Gender (#114 - assigned to @Zoe7)
• Location: County (#115 - assigned to @erinborders)

• about
• add
• main
• additional pages?

• Node.js RESTful API
  • beyond prototype: Amazon API Gateway
• Postman
• MongoDB

See: https://dumpcopcash.com/

Idea: Add boolean field in fundraising campaign under "Police Union Contributions"

Test & update headshot links from public

Separate tutorials for three steps:

1. Add Attorney Research
2. Add Research to Dataset
3. Add Data to Codebase

Potential:

• Party Affiliation
• Stance on Issues
• Sentencing History
• Demographics

When trying to use npm install in the repo/app, it provides an error saying that a certain package.json doesn't exist.

Steps to reproduce the behavior:
Try to npm install on Windows 10. I didn't do anything else.

I expected for the npm install to work.

npm provides a log of the error, listed below.

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session fcee3fa2142c0bca
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall [email protected]
7 info lifecycle [email protected]~preinstall: [email protected]
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 timing stage:loadCurrentTree Completed in 21ms
11 silly install loadIdealTree
12 silly install cloneCurrentTreeToIdealTree
13 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
14 silly install loadShrinkwrap
15 timing stage:loadIdealTree:loadShrinkwrap Completed in 112ms
16 silly install loadAllDepsIntoIdealTree
17 silly fetchPackageMetaData error for readable-stream@file:readable-stream@git+https:\github.com\meteor\readable-stream.git#2e9112d7d31a2af6e0682db0e18679b1e5fd4694 Could not install from "node_modules\meteor-node-stubs\readable-stream@git+https:\github.com\meteor\readable-stream.git#2e9112d7d31a2af6e0682db0e18679b1e5fd4694" as it does not contain a package.json file.
18 timing stage:rollbackFailedOptional Completed in 0ms
19 timing stage:runTopLevelLifecycles Completed in 285ms
20 silly saveTree [email protected]
20 silly saveTree +-- @babel/[email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | `-- [email protected]
20 silly saveTree +-- [email protected]
20 silly saveTree +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | |   `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | | +-- [email protected]
20 silly saveTree | | | | +-- [email protected]
20 silly saveTree | | | | +-- [email protected]
20 silly saveTree | | | | +-- [email protected]
20 silly saveTree | | | | | +-- [email protected]
20 silly saveTree | | | | | `-- [email protected]
20 silly saveTree | | | | `-- [email protected]
20 silly saveTree | | | +-- [email protected]
20 silly saveTree | | | | `-- [email protected]
20 silly saveTree | | | |   `-- [email protected]
20 silly saveTree | | | `-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | | +-- [email protected]
20 silly saveTree | | | +-- [email protected]
20 silly saveTree | | | | `-- [email protected]
20 silly saveTree | | | +-- [email protected]
20 silly saveTree | | | +-- [email protected]
20 silly saveTree | | | | +-- [email protected]
20 silly saveTree | | | | `-- [email protected]
20 silly saveTree | | | `-- [email protected]
20 silly saveTree | | |   +-- [email protected]
20 silly saveTree | | |   `-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | | `-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | | +-- [email protected]
20 silly saveTree | | `-- [email protected]
20 silly saveTree | +-- [email protected]
20 silly saveTree | `-- [email protected]
20 silly saveTree |   `-- [email protected]
20 silly saveTree `-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   | +-- [email protected]
20 silly saveTree   | | +-- [email protected]
20 silly saveTree   | | | `-- [email protected]
20 silly saveTree   | | |   +-- [email protected]
20 silly saveTree   | | |   +-- [email protected]
20 silly saveTree   | | |   `-- [email protected]
20 silly saveTree   | | |     +-- [email protected]
20 silly saveTree   | | |     `-- [email protected]
20 silly saveTree   | | `-- [email protected]
20 silly saveTree   | `-- [email protected]
20 silly saveTree   |   +-- [email protected]
20 silly saveTree   |   | `-- [email protected]
20 silly saveTree   |   +-- [email protected]
20 silly saveTree   |   +-- [email protected]
20 silly saveTree   |   `-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   +-- [email protected]
20 silly saveTree   | +-- [email protected]
20 silly saveTree   | `-- [email protected]
20 silly saveTree   |   +-- [email protected]
20 silly saveTree   |   `-- [email protected]
20 silly saveTree   `-- [email protected]
20 silly saveTree     +-- [email protected]
20 silly saveTree     `-- [email protected]
21 verbose stack Error: ENOENT: no such file or directory, open 'MyHomeDirectoryHere\prosecutor-database\app\node_modules\meteor-node-stubs\readable-stream@git+https:\github.com\meteor\readable-stream.git#2e9112d7d31a2af6e0682db0e18679b1e5fd4694\package.json'
22 verbose cwd MyHomeDirectoryHere\prosecutor-database\app
23 verbose Windows_NT 10.0.19041
24 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
25 verbose node v14.4.0
26 verbose npm  v6.14.5
27 error code ENOLOCAL
28 error Could not install from "node_modules\meteor-node-stubs\readable-stream@git+https:\github.com\meteor\readable-stream.git#2e9112d7d31a2af6e0682db0e18679b1e5fd4694" as it does not contain a package.json file.
29 verbose exit [ 1, true ]

Possible?

• HTML
• CSS
• Handlebars

Currently, light-pollution organizes via role:

Because the names of each role differ depending on the federal, state, and local level, this is problematic.

The new idea is to organize by zip code. User enters their zip code; light-pollution fetches all prosecutors in surrounding area.

A map would work, too, but design-wise is too clunky and unwieldy.

Search cycles through entire database; should include:

• buttons for filtering
  • alphabetical
  • state
  • demographics
  • role
• text search

Add an anonymous thumbnail for prosecutors without headshots.

• d3.js

This is about the USPD web app (NOT the GitHub repo)

Using BEF, the reset button doesn't appear if the filter is placed as a block (ex: sidebar).

Each prosecutor is listed in an Attorney Card for filtering on the homepage. Here's a gif by @06b demonstrating their responsiveness fix:

If you're a designer, ux/ui developer, or front-end developer, we need help making these Attorney Cards look great.

We're also looking for designers to overhaul the entire theme of the website, which you can read about here: #105

Something like, "we currently have [x] prosecutors listed."

Alternatively: "there are [x] prosecutors total. we currently have [x]."

Filter issue

Instead of infinite scroll, pagination would be wonderful.

Make a more efficient master to gh-pages workflow.

Resurrecting an old issue for Hacktoberfest 2020:

On an organizational/logic level, it is better to group by role/state/area rather than person, as the person can change but the position remains the same.

Potential idea: ability to filter based upon a specific office and read about the current & previous prosecutors. Can also help with identifying trends.

If you have any ideas, feel free to give this a shot.

🤯

Describe the bug
The README's installation instructions are not accurate and produce an npm error.

To Reproduce
Steps to reproduce the behavior:

1. Follow Advanced (Developer experience) instructions for local dev environment setup.
2. npm install will produce:

npm ERR! code ENOLOCAL
npm ERR! Could not install from "node_modules/meteor-node-stubs/readable-stream@git+https:/github.com/meteor/readable-stream.git#2e9112d7d31a2af6e0682db0e18679b1e5fd4694" as it does not contain a package.json file.

Expected behavior
Installing dependencies from a fresh repo should correctly install dependencies without error.

Fix
Update README to list correct installation instructions using meteor.

Current number of prosecutors in D8 instance: 485

Solves:

• Missing link between mLab instance & GitHub data contribs

Potential Issues:

• Keep or delete csv-json-data files?
• If delete: how to host an open/transparent dataset for non-devs, researchers, etc.?

On mobile view of the app, the "vote" ribbon gets in the way of the user experience.

(Additionally: need new link for the ribbon. Suggestions?)

Potential:

• Scrapping via Python scripts
• Requesting court records (fee)
• Utilizing crime statistics/data
• LexisNexis/WestLawNext legal libraries

Current:

• Googling candidate name; inserting data into a spreadsheet

🚀

Update wiki with complete steps on how to contribute

Bootstrap: https://www.bootstrapcdn.com/
Bootswatch: https://www.bootstrapcdn.com/bootswatch/?theme=17

🔥 Hacktoberfest Status: 7 District Attorneys to go! 🔥

Welcome, Hacktober participants! 👋🏽

This is a collaborative issue for Hacktoberfest 2020. Join us!

Why This Project?

If you're looking for a meaningful repo to contribute to, this is one. Our goal is to collect as much information as we can about District Attorneys because prosecutors are the only figures who can charge cops with police brutality. As such, we believe prosecutors are a key contributor to the ongoing police violence against unarmed individuals. Prosecutors who fail to hold cops accountable actively encourage police brutality. Our mission with this web app is to help educate voters so that they vote against prosecutors who let cops engage in this violence. (read more)

Who Can Contribute

This issue is perfect anyone looking to get their feet wet for Hacktober. From beginners learning to code or use GitHub, to intermediate & advanced developers who are interested in data science, we can use your help harvesting basic information about the nation's District Attorneys. (Unsurprisingly, a dataset of this magnitude does not already exist.) You can see what we currently have on our live web app.

Our Hacktober 2020 Goal: Add 100 District Attorneys 🎉

By the end of Hacktober, we hope to add 100 District Attorneys to our web app. We need your help with gathering basic information, including:

• name
• role
• state
• county
• party
• age range
• gender
• race
• appointed date OR elected date
• headshot (profile picture)
• website
• wikipedia entry
• targeted google news search
• social media (facebook, twitter, instagram, linkedin, youtube)
• office address
• contact info: email
• contact info: phone
• any relevant articles (link, title, summary, feature image)

Whew! You see why we're looking for as many people as we can to help. That's a lot of simple data to mine.

How You Can Help

Instructions For Setting Up Git / GitHub in Terminal / Command Line (OPTIONAL; if you've done this in the past, you don't have to do it again)

1.) Find your public SSH key:

cat ~/.ssh/id_rsa.pub

2.) Copy the key, including the ssh-rsa (but not your computer name)

3.) Go to your GitHub settings

4.) Paste in your SSH key

5.) You should be good to go! Email me if you have any trouble pushing to the repo.

Instructions For Setting Up Your Local Environment

1.) Fork this repo

2.) Clone the forked repo to your local environment:

git clone [email protected]:[your username]/prosecutor-database.git

3.) Make sure your branch is up-to-date with everyone else's work:

git fetch origin hacktober-data

4.) Create your branch:

git checkout hacktober-data

5.) Install the npm packages.

npm install

Instructions For Gathering Data

1.) Now, the fun part! It's time to start gathering data. Search through our web app for a District Attorney in a state of your choosing. Click through their profile to see what information we have so far. (Example: search "California" & filter for "District Attorney").

2.) Once you find a missing District Attorney (or missing Profile Information about a District Attorney), visit our Google Sheet: US Prosecutor Database - Profile Template. You can add it to your own Google Drive or download it directly to your computer as a CSV file.

3.) Time to Google! (Or Bing, or DuckDuckGo.) Use your favorite search engine to find information about District Attorneys in the state you chose. Start populating your Basic Prosecutor Profile sheet (aka, your CSV data) with whatever data you can verify. Help: you can help with the import by deleting any columns that you don't collect; for example, a lot of people leave the articles columns blank. Please delete any columns which you don't collect information for. Thanks in advance!

4.) Once you've finished populating your sheet, save/download the .CSV file to the repo folder.

5.) Open your Terminal / Command Line. Enter the following command: npm install -g csvtojson. This will install a package called csvtojson, which is a CSV to JSON converter tool.

6.) Next, enter this command: csvtojson [your-file-name-here].csv > [your-file-name-here].json. This will convert your Basic Prosecutor Profile from a .CSV file into a code format called JSON.

Instructions For Submitting Your Pull Request

1.) Time to add, commit, & submit your pull request:

git add .
git commit -m "[Your commit message goes here]"
git push origin hacktober-data:master

2.) Celebrate! 🎉 You'll receive a comment verifying I received your pull request. Once your PR has been merged, it'll be up on the live web app, & your GitHub profile will be added to the Contributors gallery.

Troubleshooting

Errors while trying to submit a pull request

1.) Have you connected your SSH key to GitHub? If not, go to "Step 1" in Instructions For Setting Up Git / GitHub in Terminal / Command Line (above). You might be getting an error because your SSH key isn't connected to GitHub.

2.) Are you getting a failed to push error? It looks like this:

To github.com:[your-username-here]/prosecutor-database.git
 ! [rejected]        hacktober-data -> master (non-fast-forward)
error: failed to push some refs to '[email protected]:[your-username-here]/prosecutor-database.git'
hint: Updates were rejected because a pushed branch tip is behind its remote

If you see this in your terminal / command line, try git push. After pushing, go to your forked repository on GitHub.com & press "Pull Request." Select hacktober-data for the branch for your forked repo and the main repo. Press "Create Pull Request" and type a title and description for your PR.

Additional thanks to @caseyryan22465 & @shariq1989 for contributing instructions

• HTML
• CSS

Read: https://blog.mlab.com/2018/10/mlab-is-becoming-a-part-of-mongodb-inc/

Additionally: consider alternatives to MongoDB.

Request
Though the app isn't actively being maintained, we're still looking for data help when it comes to configuring a reliable list of prosecutors. You can help by submitting a pull request with updated information about a state's prosecutors.

Happy #Hacktoberfest!

• websites
  • url
  • Google News
  • Wikipedia

• front links to individual page
• .hb page template

Consider everything upon a single page. Consider hiding. Click and seek.

An easy to read, simple, clean instruction manual for those who are not developers by trade.

• get data re: upcoming elections
• .JSON
• Handlebars

We've been manually Googling, copying, and pasting information about local prosecutors through their official websites, Wikipedia entries, and state attorney websites (if available).

It would be amazing if a data scraping method can be achieved. That way, the volunteer labor will go into verification instead of extensive Google researching.

Categories to start with (requirements):

• Name
• Role (ideally, District Attorney or Municipal/City/County Attorney)
• Location (state required; city and/or zip code optional)

Notes

State

• township/municipal (city) prosecutors
• county prosecutors (DA, ADA)
• state attorney general (state)

Federal

• us attorney general (federal)

Classification Ideas

• think about what each section is responsible for
  • unique authority type of each section (which the others don't have)
  • EX: zoning laws and ordinances = township/municipal (city)

Currently, headshots are hotlinked from the pages they were scraped from.

What's the most accessible & sustainable practice for collecting headshots, so that everyone can contribute to uploading them?

• write Election Data methodology
• update Election Data methodology

Needs:

• Headshot urls
• Social media links
• Recent articles
• etc.