Web Service Method: Store Project Data on Server
Web Service Method: Store Project Data on Server
Description |
---|
Exports data from a project in RDF format and stores it on the server. The service returns the URL of the stored file on the server. |
Note
This service is the equivalent to the PoolParty frontend functionality Save Export File on Server
URL: /PoolParty/api/projects/{project}/store
Request
Supported Methods |
---|
GET |
POST |
Variable | Comment |
---|---|
| The UUID or the URI supplement (textual identifier) of the project to be used. |
Parameter | Comment | Type | Required |
---|---|---|---|
format | The RDF format in which the returned data should be serialized. You can use these RDF serialization formats as parameter value. | String | true |
modules | The list of project modules that should be exported. You can use these PoolParty project modules as parameter value. NoteTo learn more about the syntax to request a list of modules in a single request, please see: Using a list of request parameters | String | true |
Note
Export of multiple modules only works when you use serialization formats that support named graphs. See comments in RDF serialization formats
If you try to export multiple modules in a single request using a serialization format that does not support graphs, you will retrieve the following error message:
{ "errorMessage": "Serialization formats that do not support named graphs can only export exactly one module", "status": 400 } |
Response
URI of the stored file containing the project data.
Basic Pattern
http://<server-url>/PoolParty/api/projects/<project>/store?format=<serializationFormat>&modules=<projectModule>
Examples
Example Request
http://vocabulary.semantic-web.at/PoolParty/api/projects/1DCE0ED2-D7E8-0001-86A1-18652DF0D7A0/store?format=TriG&modules=concepts&modules=history
Example Response
"https://preview.poolparty.biz/PoolParty/OpenConfigPathResourceProvider/backuproot?fileName=1DDFE02B-C836-0001-DBFA-E300246D1D70/pp_project_iptcimporttest.trig"