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
One of the first things we're going to need to do is start parsing the NEF emails for links and other metadata that we can grab. I'll attach a few example emails in a sec.
The text was updated successfully, but these errors were encountered:
OK, getting these emails mostly anonymized took awhile, sorry for the delay. Here's two HTML emails (in a single file). I'm told there's also an option for plaintext emails, but I suspect few people actually want that and I guess we can put it off until the future if nobody actually turns that on (we'll get failing examples of those eventually if people are using it). nef-examples.mbox.txt
As far as fields for these go, I'd start by looking at the field names in the test assets directories, where we have dockets as HTML parsed to JSON. For example, these test fixtures probably have most if not all of the field names you need:
One of the first things we're going to need to do is start parsing the NEF emails for links and other metadata that we can grab. I'll attach a few example emails in a sec.
The text was updated successfully, but these errors were encountered: