lemmalegalconsulting/docassemble-gblsletters

Letter Suite for Greater Boston Legal Services.

docassemble.GBLS

Letter Suite for Greater Boston Legal Services.

Author

Stavros Constantinou, [email protected]

docassemble-gblsletters's Issues

Create custom questions for the templates that require them

Only questions not coming from/defined by legal server should be asked and/or customized

Example:

This should be a custom question:

Options to include are in the doc, once question is written and in interview, remove yellow from doc and upload new doc to trello board:

Incorporate a demo of a few of the OpenAI integration layers

The idea is to inspire the GBLS staff with the possibilities of the OpenAI integrations. This could be in a standalone YAML that also gets data from Legal Server.

• Transform text with LLM
• Goal satisfy
• Extract fields from open text

Check all docs for use of `other_parties` variable and make sure it is used properly to refer to the defendant / other party

@nonprofittechy will Legal Server have other_parties info ?

Potentially find a way to control question order

1. Maybe add questions that appear in every letter (ie clients name, clients address, attorneys name, attorneys address, etc) to an order block to control the order of those questions and everything else will come in a random order
2. Use signature final method to make sure signature comes last (ask Quinten for formatting)

Remove upload template feature and create screen with each form as an option to generate

Review this interview that generates different kinds of motions for an idea of what we are looking for: https://apps.motenanthelp.org/run/MOHUDEvictionProject/motion_tester

Compare all current docs to original docs from Sharepoint to see if overgeneralized

Remove unneeded questions

• intro
• unit

address asked before download

Issue from #15

@h-mcguire
Member
Author
h-mcguire commented 7 hours ago
Thanks! I think it is about the download in AL. It calls CASLS_Retainer_Agreement['final'] and then looks for the clients address set that includes zip. For each variable in the set the interview would look for the object with "_label" after.

So it looked for clients[0].address.address and pulled up the question block that gathers that, then it looked for clients[0].address.address_label. Then it moved to another variable from the set doing the same thing, ending on clients[0].address.zip_label. Not sure if this is helpful or makes sense.

@miabonardi
Member
miabonardi commented 7 hours ago
Can you commit the code that was getting this error?

@h-mcguire
corrected error using [i] in order block; address gather error still …
4881045
@h-mcguire
Member
Author
h-mcguire commented 6 hours ago
Just committed! The address gather problem also happens when you try to do other documents, see the no contact letter for a quick example.

In the CASLS Retainer there is also a problem where it seems like it is gathering legal_problems before clients[0].name.full despite it being after the name gather. Or more specifically, legal_problems use of ${ clients[0].name } is what triggers the name gather. If you click the dev mode when it gathers name it makes it seem like legal_problems is what triggers the question - not the main order block.

@miabonardi
Member
miabonardi commented 3 hours ago
@nonprofittechy Is there a way to disable the collection of an address on download or preset it in AL?

@nonprofittechy
Member
nonprofittechy commented 2 hours ago
Yes, look for the store_variable_snapshot line that is calling for users[0].address.zip

@miabonardi
Member
miabonardi commented 2 hours ago
That's what I thought it was too, but couldn't find it when I looked. Will try again

@nonprofittechy
Member
nonprofittechy commented 1 hour ago
That's what I thought it was too, but couldn't find it when I looked. Will try again

You can also use the icon in the playground to browse through mentions of any reference to users[0].address.address, and of course try the developer information button </> in the browser when you're running the interview.

image

@miabonardi
Member
miabonardi commented 1 hour ago
I did that for store_variable_snapshot and found nothing. For users[0].address.address and users[0].address.zip only mentions are coming in from ql_baseline.yml. I wonder if something in the al_visual file could be causing this? Should this file be in this repo?

@nonprofittechy
Member
nonprofittechy commented 16 minutes ago
al_visual should be fine for this package. It definitely doesn't mention users[0].address.address

Possibly this could be coming from the work @tobyfey was doing on the legal server integration, but I can't think there's anything in the Assembly Line that would force the address to get gathered.

I think the court gathering used to trigger address, but I don't think it does for a year or more.

@tobyfey
Member
tobyfey commented 11 minutes ago
With GBLS, I also had users[0].address.address being called when it wasn't in the interview or the templates. It would be called during document production, so I assumed it was in the documents, and later realized it wasn't (after I added a code block that set it to GBLS main office).

Create light branding: logo and match GBLS colors

Incorporate https://github.com/networkninja/docassemble-LegalServerLink

https://github.com/networkninja/docassemble-LegalServerLink

See instructions here: https://help.legalserver.org/article/2754-docassemble-integration

We also must map all of the Legal Server variable names to the Assembly Line variable name conventions. We should do this in a modular way (maybe its own YAML file) as I would like to help more legal aid programs with this.

Add `_Retainer` to the end of Affirmative debt collection doc title and any variables in the interview

Remove `_working` or `_draft` from document names and variables

Rename this repo; it conflicts with https://github.com/gblS/docassemble-GBLS

Maybe docassemble-GBLSLetters

Make all individual letters independent interviews + publish them on LS