This section explains the following REST operations regarding the collection which have been secured with OAuth 2.0.
| Note |
|---|
The following terms explains the meaning of the parameters passed with the below REST URIs | Parameter | Explanation |
|---|
| collection path | Path of the resource | | OAuth access token | Authorized access token per user for an hour by default | | user | username of the user |
When user adds a collection to the registry, user has to specify the Content-Type of the collection in the request. The Content-Type for the collection is "application/atomcoll+xml". If user specifies a different content-type for the collection, the resource to be added wont be considered as a collection. |
...
| Attributes | Values |
|---|
| HTTP Method | GET |
| Request URI | /artifact/{ collection path }?user={ user name } |
| HTTP Request Header | Authorization: Bearer { OAuth access token } |
| Description | Retrieves the content of the requested collection |
Add a Collection
| Attributes | values |
|---|
| HTTP Method | PUT |
| Request URI | /artifact/{ complete path of the collection to be added }?user={ user name } |
| HTTP Request Header | Authorization: Bearer { OAuth access token } |
| HTTP Request Content TypeHeader | Media-Type: application/atomcoll+xml |
| Description | It adds the specified collection |
Delete a Collection
| Attributes | values |
|---|
| HTTP Method | DELETE |
| Request URI | /artifact/{ collection path }?user={ user name } |
| HTTP Request Header | Authorization: Bearer { OAuth access token } |
| Description | It deletes the requested collection if it exists. |
...