Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Glossary ] Clarify terminology for product use #478

Open
9 tasks
Tracked by #1286 ...
SamHyler opened this issue Feb 19, 2022 · 14 comments
Open
9 tasks
Tracked by #1286 ...

[Glossary ] Clarify terminology for product use #478

SamHyler opened this issue Feb 19, 2022 · 14 comments
Labels
dependency The issue or reason why this issue is in the icebox draft Not yet ready to be worked on feature: figma content writing issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks priority: low ready for content lead role: research UX and other research role: UX content writing size: medium size: 5pt Can be done in 19-30 hours

Comments

@SamHyler
Copy link
Member

SamHyler commented Feb 19, 2022

Dependency

#999 waiting on results from UXR in this issue. Update from UXR: issue 999 completed in March 2024. UXR Glossary linked in resources.

Dependency is related to the 3 key terms linked in the Research Plan of 999. The glossary created by this issue can be updated with those 3 terms when 999 is done.

Overview

Create a glossary of terms with their definitions. The glossary should clarify terminology around expungement and the related legal space, and potentially other complex language that can help the user navigate the site. The glossary should address terms that are on our site, the terms that they could be confused with (for example, the difference between expungement and record clearance, and why and when to use one or the other), and any potential terms that we may use in the future. It can include relevant contextual information.

There are currently 3 needs potentially identified for this issue, previously 2 needs. The first (Content) need was the original idea for the glossary from discussions with Bonnie.

  1. Content needs to create a glossary of user facing language for all legal terms used on the site and information about why to use which term and when. It will be used in, for example, tool tips. It should be written as ready-to-go modular copy.
  2. Research needs some kind of repository of information for legal information around expungement for internal purposes and to educate crossfunctional teams. ? Addressed in this separate issue Updating UXR understanding of current expungement laws and polices #1214 Suggestion that this issue come before glossary work
  3. Research needs a partner-facing glossary of terms for the wiki ?

Content is working with Dev to discuss building tool tips and other relevant features for the future site

Action Items

  • Establish collaboration between Content, UXR, and any other potential teams, identify needs, create a plan for working
  • Identify relevant terminology to include in the glossary together based on each team's knowledge base and needs
  • Discuss and decide together on how to create useful glossary documentation for the various teams' needs and where it should be stored for future use
  • Create a space to house the glossary that will be useful to all relevant teams after discussion (i.e. doc, figma page, figjam, sheet, or other tool)
  • Clarify legal terminology relevant for our website. Write a description for each
  • Save and compile sources and any useful links found along the way in the same doc at the end. Indicate if any are useful resources to potentially refer the users of our site onwards for more info
  • Recommend how to use terms and when/where on the website - UXR & Content
  • Content task: Update writing guidelines with instructions around terminology (how/when to use, this not that, etc.)
  • Content task: Create follow up issue to check product for consistency and make a list of changes needed

Resources/Instructions

Use resources available: website, Figma, FigJam, google doc, Content Writing Guidelines

Create a space to house the glossary that will be useful to all relevant teams after discussion.
Template to get started with brainstorming the glossary. Final format not decided.

Previous relevant docs to refer to:

Here is the UXR Glossary updated in March 2024.

This and this doc were created as content glossaries. Both are archived. Refer to the terms that are useful, and create a new workspace on the appropriate platform to start work again in 2024.

Refer also to this document to see previous work done in the expungement space.

For reference only, explorations on some parts of terminology under [Concept exploration](Concept exploration)

For extra context and project tracking - see related issue, now closed #598

@SamHyler SamHyler assigned SamHyler and unassigned SamHyler Feb 19, 2022
@SamHyler SamHyler changed the title Clarify terminology "expungement, clearance, reduction, etc." [Draft] Clarify terminology "expungement, clearance, reduction, etc." Feb 23, 2022
@ValeriyaMetla ValeriyaMetla changed the title [Draft] Clarify terminology "expungement, clearance, reduction, etc." Clarify terminology "expungement, clearance, reduction, etc." May 1, 2022
@ValeriyaMetla ValeriyaMetla added dependencies Pull requests that update a dependency file dependency The issue or reason why this issue is in the icebox and removed dependencies Pull requests that update a dependency file draft Not yet ready to be worked on labels May 2, 2022
@jamiesiu jamiesiu added this to the 09 W1 Content Development milestone Jun 13, 2022
@SamHyler SamHyler removed the dependency The issue or reason why this issue is in the icebox label Jun 14, 2022
@SamHyler
Copy link
Member Author

Came up in the UXR meeting: Some other terms that may or may not be related to personal statement/declaration letter/etc. is: rehabilitation letter, certificate of rehabilitation and pardon. Worth it to dig into - may not be the same thing at all but just putting this here to be sorted.

@SamHyler
Copy link
Member Author

@ana-lobos @cynphonic thanks for all the work on this so far! Can you update the Github issue with the link to the proposed document when it's ready? Go ahead and leave the two docs linked as a paper trail but make it clear which one is for use.

@cynphonic
Copy link
Member

@SamHyler Hi Sam, Ana and I discussed this in our meeting on Friday, and we wanted to stick with using the two documents that are already linked to this github issue. It's been edited to add a few terms that we want UXR to look into and/or discuss with a lawyer to double check all of the terminology we have listed. We have also included links to helpful resources we found.

@ana-lobos
Copy link
Member

Hi @SamHyler! As Irene mentioned, we've kept both of them. I've added a bit more info as to which issue is which for clarity.

@SamHyler
Copy link
Member Author

SamHyler commented Jul 1, 2022

Thanks @cynphonic and @ana-lobos , sorry I misunderstood from the last UXR when Ana spoke about it. Thank you both for your work on this issue! We can discuss in Content at the next meeting.

@sylvia-nam sylvia-nam added the role: research UX and other research label Feb 6, 2024
@sylvia-nam sylvia-nam assigned sylvia-nam and unassigned sylvia-nam Feb 20, 2024
@sylvia-nam
Copy link
Member

Here's the latest UXR Glossary

@SamHyler
Copy link
Member Author

adding draft label based on need for revision, roadmapping, and new priorities

@SamHyler
Copy link
Member Author

Added some revisions to create more clarity on this issue. There was a 3rd potential need identified, I will finish updating the issue with this soon, as well as finalize the issue before it's ready to be worked on and finished.

@SamHyler SamHyler added issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks size: medium size: 5pt Can be done in 19-30 hours and removed priority: high size: 1pt can be done in 6 hours or less labels Apr 22, 2024
@SamHyler SamHyler changed the title [Terminology ] Clarify terminology "expungement, clearance, reduction, etc." [Terminology ] Clarify terminology for product use Apr 23, 2024
@SamHyler SamHyler changed the title [Terminology ] Clarify terminology for product use [Glossary ] Clarify terminology for product use Apr 24, 2024
@emmathrash
Copy link
Member

For extra context and project tracking - see related issue, now closed #598

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency The issue or reason why this issue is in the icebox draft Not yet ready to be worked on feature: figma content writing issue level II: main issue tracking level I issues; often will be tracking cross-fuctional teams tasks priority: low ready for content lead role: research UX and other research role: UX content writing size: medium size: 5pt Can be done in 19-30 hours
Projects
Status: Prioritized Backlog
Development

No branches or pull requests