Add NDA support to @recap.email
After reviewing the error on #2145 we realized that is due to a parsing error originated because these notifications are NDA (Notice of Docket Activity).
Some changes on NotificationEmail are needed in order to parse properly NDA notifications and get their metadata and send docket alerts based on these notifications.
@mlissner some questions about this:
I saw that NDAs are notifications specifically for appellate courts.
If I'm not wrong. The metadata that we need to fill an appellate case is similar that the retrieved by AppellateDocketReport, right?
Comparing some test examples I can see that some data are not available in NDAs and seems mandatory in order to add a new docket for an appellate case, e.g:
appeal_from, fee_status, originating_court_information, panel

To retrieve the document for this kind of case seems possible. I saw that since there's no document number the pacer_doc_id is used. Also seems that the document link in NDAs is also a free-look download link.
What should we do if we receive an NDA for a case that doesn't exist in CL already? Should we only add the document as an orphan document?
Seems like the missing piece is:
Comparing some test examples I can see that some data are not available in NDAs and seems mandatory in order to add a new docket for an appellate case, e.g: appeal_from, fee_status, originating_court_information, panel
Why do you say those are mandatory?
Sorry I got confused because of this code:
(but this is just for updating metadata)
I've done a test removing these fields that we don't have in an NDA and the docket was added even though some fields are blank.
So yes, seems it's possible to add the docket and documents from NDAs, working on it.