ePADD is a software package developed by Stanford University's Special Collections & University Archives that supports archival processes around the appraisal, ingest, processing, discovery, and delivery of email archives.
After importing the corresponding Mbox file, the name John Miller is shown correctly in the list:
However, after restart, it is the email john.miller@gmail.com that is displayed:
This seems to happen when an Mbox file contains an email that is missing the name:
Cc: "john.miller@gmail.com" john.miller@gmail.com
And after that, an email containing both email and name:
To: "John Miller" john.miller@gmail.com
After import, ePADD correctly recognises that the name John Miller is associated with the email john.miller@gmail.com and correctly displays the name in the list of correspondents but after restarting ePADD, the list of correspondents shows the email instead.
Contacts are written to disk in serialised form, and when ePADD is restarted, contacts are deserialised. In this process, it is assumed that the line with the email address appears after a line with a name (if a name exists). If a name exists but occurs after the email, then for the contact ePADD assumes there is no name and sets the email as the name instead, and it seems that is what is happening here.
After importing the corresponding Mbox file, the name John Miller is shown correctly in the list:
However, after restart, it is the email john.miller@gmail.com that is displayed:
This seems to happen when an Mbox file contains an email that is missing the name:
Cc: "john.miller@gmail.com" john.miller@gmail.com
And after that, an email containing both email and name:
To: "John Miller" john.miller@gmail.com
After import, ePADD correctly recognises that the name John Miller is associated with the email john.miller@gmail.com and correctly displays the name in the list of correspondents but after restarting ePADD, the list of correspondents shows the email instead.
Contacts are written to disk in serialised form, and when ePADD is restarted, contacts are deserialised. In this process, it is assumed that the line with the email address appears after a line with a name (if a name exists). If a name exists but occurs after the email, then for the contact ePADD assumes there is no name and sets the email as the name instead, and it seems that is what is happening here.