VoSpace 2.x

MoveNode

Move a node within a VoSpace service.

Note that this does not cover moving data between separate VoSpace services.

Moving nodes between separate VoSpace services should be handled by the client, using the import, export and delete methods.

Parameters

• Target - The URI of an existing data node. note
  • vos://[service]/000-517
  • vos:///000-517
  • vos://[service]/path/my%20results
  • vos:///path/my%20results
  • vos:///my%20results

• Parent - The URI of an existing parent node. note
  • vos://[service]/path/path/
  • vos:///path/path/
  • vos://[service]/
  • vos:///

• Name - A (optional) human readable name for the new node
  • my results

• Properties - An optional set of name value properties for the node

Returns

A full <node> element for the node, containing

• The full URI encoded identifier for the node. note
  • vos://[service]/000-517
  • vos://[service]/my%20results
  • vos://[service]/path/path/my%20results

• The node name as a plain string
  • 000-517
  • my results

• Type - The URI of the node type
  • ivo://org.astrogrid.vospace/types/data.node

• Properties - The set of name value properties for the new node

Again, an XML friendly way to include any additional type specific data could be to use a generic <node> element, and then use xsi:type attribute to extend it as required.

Throws

• The service will throw a NodeNotFound exception if the target node does not exist.
• The service will throw a NodeNotFound exception if the parent node does not exist.
• The service will throw a DuplicateNode exception if a node already exists with the same name.

• The service may throw an InternalFault exception if an operation fails.
• The service may throw a PermissionDenied exception if the user does not have permissions to perform the operation.

• The service will throw a LinkFound exception if the target path includes a link. note
• The service will throw a LinkFound exception if the target node is a link. note

• The service will throw a LinkFound exception if the parent path includes a link. note
• The service will throw a LinkFound exception if the parent node is a link. note

Notes

• There is a strong case for making this an asynchronous operation.
• Moving a large data set within a space service may involve transferring the data from one physical disk to another, which may take time to complete.

• The <target> identifier in the request can be full a URI including the service identifier and node path.
  • vos://[service]/000-517
  • vos://[service]/path/my%20results

• The <target> identifier in the request can be a relative URI just containing the node path.
  • vos:///000-517
  • vos:///path/my%20results

• The <parent> identifier in the request can be full a URI including the service identifier and node path.
  • vos://[service]/
  • vos://[service]/path/path/

• The <parent> identifier in the request can be a relative URI just contianing the node path.
  • vos:///
  • vos:///path/path/

• The <node> identifier in the response must be full a URI including the service identifier and node path.
  • vos://[service]/000-517
  • vos://[service]/path/my%20results

• Link nodes are not part of the V1.0 specification, they will be defined in a future version of the specification.
• LinkFound exceptions are defined in this version of the specification to enable future versions to extend the current interface, rather than require a completely new interface type.

Questions

• Should we allow null <parent> to indicate change of name only ?
• Should we allow null <name> to indicate move but keep same name ?

-- DaveMorris - 18 May 2006