astoria-tech / 50-a-foil-status Goto Github PK

The links are the same as the ones in the navigation

Design and implement a new favicon for the site, replacing the default react favicon, or else remove the favicon entirely.

The columns of data in the foia list are not always aligned, depending on the data. The left edge of each column should always be aligned. This might involve re-writing the table markup to use another layout technique (e.g. divs and flex/grid).

Example of the problem:

Create an object (other construct) to map the machine friendly but ugly-looking status's returned by the API to human-readable versions, and use those human versions for display. The mapping should be as follows:

• ack → Acknowledged
• rejected → Rejected
• done → Done
• processed → Processed
• payment → Payment
• no_docs → No documents
• fix → Fix
• lawsuit → Lawsuit
• abandoned → Abandoned
• partial → Partial
• appealing → Appealing

Based on: https://docs.google.com/document/d/1CLRQBiWRAmvFXY5rf-yFn_ao6fptRByHCmVw6neBSDI/edit#

• Researching additional datasources to supplement muckrock
• Researching additional data within muckrock beyond just the Officer_Accountability user

https://nivo.rocks/funnel/
Based on 50-a request status.

The current page title is the default "React App". This should be changed to describe the project. Will need thought on what the text actually should be.

See back to top design and assets at the bottom of the figma design.

See @aniagaska 's comment in #56

The filter select menus and their labels are crammed together; the simplest solution is to put each label+select on their own line with some white space. That might be the best option, but the actual implementation is left to the developer's creativity.

Some specific issues to look at:

• The header icon shrinks to nothing at small widths
• The header text gets cut off at small widths

Design decisions are left to the developer's creativity on how to resolve.

This is wide open, but still could be a good first issue for someone who feels confident in testing and wants to help us get on good footing with testing. We'd love to have tests for both our Node.js backend and our React frontend.

If someone takes this on, it would be good to start splitting this out a bit from a monolithic "Write tests" issue :)

Currently says "Web site created using create-react-app"

1. Decide:

• Cloud-based solution
• File-based solution on GitHub repo

2. Implement the data model and data layer for jurisdiction and agency data ("stale data")

3. Create a manual script to write the "stale" data and store

4. Re-write the existing cron job

• Only call out to the foia data
• Read the "stale" data
• Combine the above and write out

5. Where do we store the above data:

• Redis
• File
• Memory (i.e., set to a variable)

Once this is done, everyone with a local repository will need to run these commands inside their repo to get everything working again.

git branch -m master main
git fetch origin
git branch -u origin/main main

For more info, see the official Github documentation.

Add hamburger menu following the design

Hashing out subdomain in #48

Something like the typical box-with-arrow icon

The times of requests displayed in the filterable foia list are in machine-readable ISO format, which is not very human friendly. Convert this to a human-readable format. We already include the luxon library, which is really nice for handling dates and times.

Here's the issue outlined in red.

This ticket should at the same time address the dates overlapping each other, simply by having shorter output. Here's that issue.

• Node version?
• Missing setup step?
• Simple datastore:init (tracked as #37)

• Server: npm run dev
• Browser: npm start

Muckrock doesn't expose the journal of each change to Foia Request statuses and other attributes. If we were able to capture that over time, we could give a much more data rich timeline of the lifecycle of freedom of information.