Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/NQYTK5QGDK7QHWLS5FHV6DDTL4WBNBON/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "NQYTK5QGDK7QHWLS5FHV6DDTL4WBNBON",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/MLFEGZA2EDWDVJTSOBNSY2GI3FV45MJ5/?format=api",
    "sender": {
        "address": "amsat-bb (a) wd9ewk.net",
        "mailman_id": "21664df01bef4757931b7cdb42a9e768",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/21664df01bef4757931b7cdb42a9e768/emails/?format=api"
    },
    "sender_name": "Patrick STODDARD (WD9EWK/VA7EWK)",
    "subject": "[amsat-bb] Re: LOTW - improperly coded satellite contacts?",
    "date": "2011-02-21T16:07:27Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/MLFEGZA2EDWDVJTSOBNSY2GI3FV45MJ5/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Bill!\n\n> I just upload several hundred sat contacts to LOTW.  Many matches were returned,\n> BUT many of them were credited for \"VUCC 144 mhz\" or \"VUCC 432 mhz\" and NOT\n> for \"VUCC Satellite\", which is how they should be credited.\n>\n> Does this mean that the person on the other side of the QSO did not properly\n> encode the log entry as a satellite QSO?  Or is there some glitch in the LOTW\n> program?  I would have guessed that, if I encoded the QSO as Satellite and the\n> guy on the other side did not, it would not show as a match at all.\n\nMost likely, the other station didn't include one or both of the fields\nused to mark a QSO as a satellite QSO (Propagation Mode, Satellite\nName).  I've seen this on a handful of QSOs I've uploaded in the past\nfew weeks.\n\n> Anyone know how this is handled?\n\nAssuming your log has all the necessary fields for a satellite QSO (all\nof the QSLs I've gotten from you are showing as satellite QSOs, so I\ndon't think your logs are missing anything), there is only one way to fix\nthis - the other station has to upload the QSO record(s) again, this time\nmaking sure those additional ADIF fields are in their log.  As long as the\nother QSO details like date, time, your call, etc. are the same, the new\nupload replaces what was originally uploaded.\n\nIf the other station's log has the satellite-related fields, then an e-mail to\nlotw-help @ arrl.org is necessary.  There could be errors in how ARRL's\ndatabase queries run to match up QSO records and make QSLs.  ARRL\nwill not fix problems with other stations' log uploads, and everything has\nto be in there correctly in order to use the resulting QSLs toward awards.\nI found this out recently, as I accumulated just enough grids from satellite\nQSOs to apply for my satellite VUCC using LOTW.  It's been almost 2\nweeks since I filed for that, and hopefully there is some movement with\nmy application soon.\n\n73!\n\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\n\n",
    "attachments": []
}