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

RECAP Email: Confirm if additional data needs to be replicated to subdockets #4830

Open
albertisfu opened this issue Dec 16, 2024 · 1 comment

Comments

@albertisfu
Copy link
Contributor

In #4665 I suggested that we'd need to apply a similar approach for RECAPEmail data.

However, this issue might already be resolved. Currently, we parse the "multi-NEF" format, which includes docket entries associated with multiple cases. During this process, we parse the entry, document, and attachments (if available) and replicate them across all related cases.

I'd like to confirm whether multi-nefs are the same as dopeldockets. If so, the work for RECAP emails might already be complete. Below are some examples of multi-NEFs for reference:

https://github.com/freelawproject/juriscraper/blob/main/tests/examples/pacer/nef/s3/jpml_1.json
https://github.com/freelawproject/juriscraper/blob/main/tests/examples/pacer/nef/s3/nysd_3.json

Additionally, is it guaranteed that a RECAP email will always include all its subdockets, or is it possible for only some of them to be listed? If the latter is true, we would still need to identify and process any subdockets that might not be included in the email content.

@mlissner
Copy link
Member

is it possible for only some of them to be listed?

I admit I don't know, unfortunately, but sounds like we can let this be for a bit after fixing the other issues and see if it's still an issue.

@mlissner mlissner moved this to Backlog Jan 6 - Jan 17 in Sprint (Web Team) Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog Jan 13 - Jan 24
Development

No branches or pull requests

2 participants