Unknown macro: {next_previous_links}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

This section explains the following REST operations regarding the collection which have been secured with OAuth 2.0.

The following terms explains the meaning of the parameters passed with the below REST URIs

ParameterExplanation
collection pathPath of the resource
OAuth access tokenAuthorized access token per user for an hour by default
userusername 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.

Get the Content of a Collection

AttributesValues
HTTP MethodGET
Request URI/artifact/{ collection path }?user={ user name }
HTTP Request HeaderAuthorization: Bearer { OAuth access token }
Description                 Retrieves the content of the requested collection

Add a Collection

Attributesvalues
HTTP MethodPUT
Request URI/artifact/{ complete path of the collection to be added }?user={ user name }
HTTP Request HeaderAuthorization: Bearer { OAuth access token }
Request Content Typeapplication/atomcoll+xml
DescriptionIt adds the specified collection

Delete a Collection

Attributesvalues
HTTP MethodDELETE
Request URI/artifact/{ collection path }?user={ user name }
HTTP Request HeaderAuthorization: Bearer { OAuth access token }
DescriptionIt deletes the requested collection if it exists.

 

 

  • No labels