You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: