allella
commented
1 month ago @bogdankharchenko thanks for moving this along. I'll defer to @JSn1nj4 or @zach2825 on the technical end.
From the UI and data perspective, here are a few notes:
- Nvite is no longer a company (bought many years ago), so we could remove it from the system
- On the list view, I think showing the API key there could be more valuable than the created date.
- We don't have exact days, or even months, when orgs were started. We could make that an int and store the years if we wanted to keep it simple.
- I don't see it, but we have been saving the "field_year_inactive" in the old API. That's proven to be useful when looking back at the history. In fact, last night Robert Roskam and I were looking at that inactive list and when groups were started and ended while talking about the history of the javascript groups.
- Similarly, we have a "description" field on the old API. Robert and I were also using that last night while being reminded that one of the javascript groups started as a React group and changed it's name, as noted on the description field. We didn't expose that in the orgs API, but it has been a handy internal field to capture other notes and history when groups go inactive.
- This isn't for this PR, but since we're replacing the Orgs API, we're replacing all of the organization pages on data.openupstate.org like https://data.openupstate.org/organization/hackgreenville . I'm not sure we want / need a URL and actual page for each organization. Though, I think it would good if we at least planned for the https://hackgreenville.com/orgs being able to show these extra details about the org with a modal, drop-down, pop-up or whatever the current UI best practices are for show/hide of extra details without needing to go to a new URL
- I can't tell from the screenshot, but I wondered if the tags UI element is multi-select. I know the org_tags table exists, so I'm assuming we can do 1 to many. We mostly have only used the tags for OpenWorks, but at one point we tagged open-source groups for some potential use-case, so we do have some groups with multiple tags and I could see that being the same.
- I like the field groupings in the admin.
- I don't suppose we're going to tax the system with our pagination, so perhaps we raise that up to a higher number so all of the orgs show without needing to page. Maybe 100 per page? Or, do we think the "search" feature makes viewing a larger set less necessary?
- I suspect we'd want to sort the orgs by title in the list view
bogdankharchenko
Resolves: https://github.com/hackgvl/hackgreenville-com/issues/210