Skip to content

Latest commit

 

History

History
74 lines (50 loc) · 11.9 KB

README(LABS34).md

File metadata and controls

74 lines (50 loc) · 11.9 KB

Product Mission and Goals

Human Rights First (HRF) is a non-profit, nonpartisan, 501(c)(3), international human rights organization based in New York, Washington D.C., Houston, and Los Angeles. HRF works to link immigration attorneys and advocates with asylum seekers and provide those attorneys with resources to best represent their clients. Our application leverages historical data to better inform advocates of a judge’s past decisions. The hope is that advocates for asylum seekers can use our tools to tailor their arguments before a particular judge and maximize their client's chances of receiving asylum.

Architecture and Team Roles

Architecture

To get started

API documentation

Our Role

  • Database changes: Removed newCase table with that change all cases approved and pending stored in the same table with a status tag(approved or pending). Database seeds match with the schema.
  • Superuser role added. Superuser can add, remove, and edit users.
  • Users be able to edit their information including email address, name, etc.
  • Superuser and admins have more item in navigation bar that new items leads to admin only features such as manage users and approve cases.
  • Back-End be able to programatically upload files to s3 bucket
  • Currently, some endpoints require authentication. In the future, auth will need to be added to all endpoints however it has not been done yet to make it easier for the entire team to work with the data.
  • Authentication middleware ./middleware/authRequired.js is fully functional needs to be added to each endpoints which needs authentication.
  • The .env.sample file contains all of the environment variables needed and where to find the values in order to run the project locally.
  • There`s a API endpoint implemented by previous teams called Swagger docs API information in these documantation is not accurate. Swagger docs needs to be cleaned from code. For accurate and up-to-date API documantation please refer to this file

Codebases

Front-End

Uses NodeJS to create the web-based user interface for uploading case documents, managing users, and viewing data in the form of tables and visualizations.

Back-End

Uses Javascript, Express, and Postgres to manage databases containing tables for users, judges, and cases.

Data Science

This part of the application uses optical character recognition (OCR) to convert pdf images into text data that can be searched via natural language processing (NLP) techniques. Key data, which we refer to as structured fields, are extracted from the text data and sent to the back-end for storage.

Known Bugs

Please see KnownDefects file

Contributors

Labs33

Senih Aydin Christina Melchor Cameron Mirza
Rees Harper Matthew Justice

Labs29 - Team A

Ava Wingfield Tom Bauer Ryan Lee
Linkedin Linkedin Linkedin

Labs30 - Team A

Tzong-Lian Tsay Trevor Beadle Reuben Palumbo
Linkedin Linkedin Linkedin
Anna Brander Maycie Morris Lynda Santiago
Linkedin Linkedin Linkedin