new API call: get_device_history

[hburgund]

Allow a client to make a call to the server requesting info about the previous sessions, envelopes, assets, etc that pertain to a particular device. This will enable us to build a "My RW" section in apps that let users go back and look at their previous activities and share them as well. It will be a nice way of preserving continuity between usages without requiring accounts to be created.

Request would take the device_id as parameter:

http://roundware.org/roundware/?operation=get_device_history&device_id=hfywkae9834hfibf49w7b29b

device_id is connected to session_id which is connected to envelope_id and asset_id.

The response should look something like this, but most likely with more asset info like tags etc:

    {
        "session_ids" [ 12,13,14,15],
        "envelopes": [
        {
            "envelope_id": 1,
            "assets": [ 
                { 
                    "asset_id": 1,
                    "asset_url": "http://roundware/org/rwmedia/asset1.mp3",
                    "mediatype": "audio"
                },
                { 
                    "asset_id": 2,
                    "asset_url": "http://roundware/org/rwmedia/asset2.jpg",
                    "mediatype": "photo"
                }
             ]
        },
        {
            "envelope_id": 2,
            "assets": [ 
                { 
                    "asset_id": 3,
                    "asset_url": "http://roundware/org/rwmedia/asset3.mp3",
                    "mediatype": "audio"
                },
                { 
                    "asset_id": 4,
                    "asset_url": "http://roundware/org/rwmedia/asset4.txt",
                    "mediatype": "text"
                }
             ]
        }
        ]
     }

May cause some issues with client devices handed out by museum, but there are ways of handling this.

[hburgund]

Eventually we can add things like how many likes/votes each of a user's assets have garnered. And even which assets a user has liked or otherwise voted on. Lots of potential here.

[13rac1]

Hmm.. This will probably be something like GET /user/[uid]/ or perhaps a subdirectory below that.