-
Notifications
You must be signed in to change notification settings - Fork 3
Web services
kutila edited this page Oct 22, 2012
·
76 revisions
The main interface to the PODD system consists of a set of RESTful web services as described below.
The location of these web services are of the form:
http:/<host>:<port>/podd/<service_name>
- Add a new schema ontology to PODD
- Add a new object (i.e. Project).
- Maps to the previous “Object Creation Service”
- Update a schema ontology by uploading a new version of it.
- The application should be in maintenance mode for this service to be used.
- The application needs to be put into a read-only state (for artifacts) when a schema ontology version update is occurring.
- Download a copy of the specified schema ontology.
- Maps to the previous “Concept Details Service”.
- Allows an authorized user to edit an existing PODD object.
- DECIDE: Should only Top Objects be editable?
- QUESTION: Do we save this as a new version of the object or overwrite the current object?
- Previous "Edit object service"
- Previous "Delete object service"
- A PODD Top object (i.e. project) that has a status of "complete" can be published by a suitably authorized user.
- Publishing results in the project/top object being made read-only and being given a stable URI.
- Previous "Publish Project Service"
- This web service makes it possible to attach existing files to a PODD artifact by defining references to it without having to explicitly upload the files. This is especially useful for very large files that would take up too much bandwidth if uploaded to PODD directly. This also leaves the responsibility of file management to the remote data store of the files.
- QUESTION: Is this service needed?
- Not in prototype
- Not in prototype
- TAB submission service – TAB import will be implemented as a client side utility. PODD itself will not support TAB format.
- Local File attachment service – Was deprecated.