Based on @rkaufman13's UX interviews, policing seem like it should be in issues.

I'll leave this issue open for anyone to fix, but I'll see if I can figure it out myself otherwise 😛

I'd love to get more headway on this project worked on. Jaoyi and the User Research team in Code for SF are looking into methods of project matching in partnership with Brigadehub, and standardizing the taxonomy is kind of the first step for that.

I have a list of different tags that have been used by various projects in the C4SF brigadehub instance, and I can get that linked/dumped into this repo for future parsing, I'm wondering if @themightychris has access to some of tags that are being used within Laddr.

Once we've dumped these into a common location, Jaoyi is looking into doing some user research on the parsed list to see if there are any that we've missed or if there are related tags or fields that haven't been listed. With any luck, the user research forms they make can be reused in Philly or any other brigade to get a more global perspective on it.

Overview

Do we need Taxonomies? There are several taxonomies. Identify if all are needed for Project Index.

Assumptions

• We need a taxonomy for the brigades to use for project topics, technologies, skills
• It is crucial for success that all the brigades that will participate in Project Index will use the same taxonomy.

Action Items

• Challenge the assumptions by identifying other options
  • Identify pros and cons of other options
• Define what would be gained by using taxonomies over other options.

explain the research process and methodology that went into designing and populating the taxonomy

#17 added a tool to populate a mysql database with current github data

• Deploy a mysql database to the nac-sandbox cluster
• Create a github action to deploy the taxonomy to it

Make drag&drop work properly.
Add mechanism to save as PR to change toml files in the repository.

Change name, from editor-ui to ui.
It'll require changes to some deployment scripts.

Thinking to use the synonyms approach.

Build and deploy swagger of the API.

Overview

Identify most recent and official taxonomies and identify issues of using them inside of Project Index

Action Items:

Review all the Taxonomies identified by CfA and Brigade champions who are working in this area

• Identify pros and cons of resources
• Identify challenges in sustainability that might impact Project Index.

mostly cosmetic, css to make it similar to project index.

The tree shows very little when showing on phone.

What process might work for maintaining taxonomies?

Overview

If taxonomies are integral to Project Index then adoption user research is key to planning broad deployment.

Action Items:

Talk with project leads at our brigades and find out:

• Are they are willing to use a common taxonomy?
• Do they approve of the current taxonomy or do they have changes to it?
• How do they want to contribute to an updated Taxonomy?
• How should we handle updating taxonomy (e.g., updating LGBT to LGBTQ to LGBTQ+ or LGBTQI, etc) after projects have integrated older terminology into whatever data standard Project Index requires?

Putting this here more so I can revisit it later.

https://gist.github.com/therebelrobot/131ba50a38a9d8b5fd673f639d5ef5a3

Change 1st Amendment to Free Speech and 2nd Amendment to Gun Violence

Pinging @mstem who's been working on the Civic Tech Field Guide for a few years now: https://civictech.guide

This page has some categories that we could consider integrating. We would then be able to contribute our projects back to the civic tech field guide, which would be sweeeeeeeeeet.

This might be a bit challenging:

• The categories are hierarchical -- do we want to incorporate hierarchy? (My vote: No)
• Do we need a new top-level concept than "topics" to represent these categories? These groupings in the CTFG feel a bit different than the focus area of the product. But I could see keeping everything as denormalized tags as being beneficial.

Thoughts?

Create a relational database with a schema allowing to store organizations, projects, tags, topics and their relationships.

Right now we only have the editor UI page, we want one just for view the finalized taxonomy.

1st Amendment and 2nd Amendment are understood only in the USA.
These two should be changed to "Free Speech" and "Gun Violence".
There may be other such items.

Try with https://www.npmjs.com/package/rc-tree ?

We show the label but we would like to tell people to use the ID.
Labels can have spaces, for example "Benefits and Tax Credits" but that can't be used as a GitHub tag (can't have spaces). In this case, the ID is already set to benefits-taxes. If as one of the first usage of taxonomy is to suggest people how to tag their project, we need to convey that they need to use the ID instead of the label. For items at top level, the ID is shown on mouse-hover, I doubt it is enough and currently the ID doesn't show for lower level items.