myDepartmentsMembers

URI

<myDepartments_uri>/members[.<format>]

Supported methods

GET, HEAD

Parent resource

myDepartment

Introduction

myDepartmentsMembers resource is the member list information of all the departments where the current user locates.

Supported Methods:

Supported output formats: rjson, json, html, xml.

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiportal is the server name, with rjson being the output format.

http://supermapiportal:8090/iportal/web/mycontent/departments/members.rjson

GET request

Gets the member list information of the departments where the current user locates.

Response structure

Sending GET request to myDepartmentsMembers, the member list information of the departments where the current user locates will be returned. The detail description is as follows:

Field Type Description
departmentId Integer The department id.
id Integer The id field.
nickname String The member nickname.
userName String The member name.

Response example

The returned rjson format representation after implementing the GET request on the myDepartmentsMembers resource http://localhost:8090/iportal/web/mycontent/departments/members.rjson is as follows:

[

    {

        "departmentId": 3,

        "id": 1,

        "nickname": "user1",

        "userName": "user1"

    },

    {

        "departmentId": 3,

        "id": 2,

        "nickname": "user3",

        "userName": "user3"

    },

    {

        "departmentId": 3,

        "id": 3,

        "nickname": "user2",

        "userName": "user2"

    },

    {

        "departmentId": 2,

        "id": 4,

        "nickname": "user5",

        "userName": "user5"

    },

    {

        "departmentId": 2,

        "id": 5,

        "nickname": "user4",

        "userName": "user4"

    }

]

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can be used to check if the myDepartmentsMembers resource exists, or if the myDepartmentsMembers resource can be accessed by clients. It can also determine if the myDepartmentsMembers resource supports an output format <format> if performed on a URI with .<format> included.

See