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/XHZR5H57T2LM6DFM44LHQIVK3W4MVATF/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "XHZR5H57T2LM6DFM44LHQIVK3W4MVATF",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/XHZR5H57T2LM6DFM44LHQIVK3W4MVATF/",
    "sender": {
        "address": "dave (a) thejohnsonsonline.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "David Johnson",
    "subject": "[amsat-bb] FUNcube Data Warehouse Realtime Min Max Values",
    "date": "2014-02-12T22:28:35Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi,\n\nSince deployment, we have been capturing the minimum and maximum \nRealtime values for each channel when they have been uploaded by a \ngroundstation. This has given us a good overview for the early operation \nand initial commisioning.\n\nWe have now moved into a steady state of operation and need to check for \nlong-term trends. To achieve this, we have changed the min-max data \ncollection such that it resets every 7 days and we capture the values \neach time it does so. At reset you will see the reference date change on \nthe page and the min/max values converge. They will diverge again within \nan orbit.\n\nWe did think about a rolling 7 day period but that is quite a \nheavywieght process on the server as it has to be run each time we get \nan upload!\n\nAs always, many thanks to all those who are uploading data to the warehouse.\n\nAny feedback to the forum as usual please: http://forum.funcube.org.uk\n\n73\n\nDave, G4DPZ\n\nFUNcube Team Member\n\n",
    "attachments": []
}