v2: new data source - Githubissues

josh-chamberlain commented 6 months ago

part of #248

[ ] uses the app/submit route
[ ] replaces airtable form
- [ ] uses a typeahead endpoint for agencies, with a "not found" option in the typeahead (not its own form field)
  - allow people to enter their own agency name in this case, like the original
- [ ] follows the same conditional logic for "agency supplied data no" and "agency originated data no"
- [ ] shows "other" string field for "data portal type other"
[ ] when a URL is pasted, let's check in the background to see if we already have it in the db
- for duplicates, display a message: "We already have this URL in the database, with an approval status of <status>."
[ ] hide most properties (new idea): this is not in the wireframe, but let's only show the contact info, source url, and the agency typeahead—with a secondary option to "show more properties", whereupon they appear.
- Rationale: these fields are all firmly optional, and showing them is intimidating for someone who's just trying to submit a source real quick.
[ ] consider: select menus are tricky to support, and not always the best user experience. we should think carefully about each property which currently uses one, and whether it should be something else.

mbodeantor commented 6 months ago

I'm definitely pro replace Airtable. I feel confident Retool can serve any needs we have that don't seem worth building a whole app for from scratch

mbodeantor commented 5 months ago

@josh-chamberlain Do we want to go with an approval_status of "needs identification" for new sources or something else?

josh-chamberlain commented 5 months ago

@mbodeantor let's do intake, we just have it null by default now

maxachis commented 5 hours ago

@josh-chamberlain Do clarify, because it's a tad ambiguous -- is this going to be on Retool, or the web app?

Police-Data-Accessibility-Project / data-sources-app