...
| Code Block |
|---|
POST /rest/objects/sufia:123456789/fcr:new/fcr:content create a new child datastream (with an automatically generated unique identifier) with the content provided by the request body |
Children
/rest/{path}/fcr:children
- GET object children, optionally filtered by mixin
- POST unsupported?
- PUT unsupported?
- DELETE unsupported?
| Code Block |
|---|
GET /rest/objects/sufia:123456789/fcr:children
List all the child nodes (objects and datastreams) for sufia:12345689
GET /rest/objects/sufia:123456789/fcr:children?mixin=fedora:datastream
only list the `fedora:datastreams` that are children of /objects/sufia:123456789
o the fcrepo 3.x "object profile")
|
Versioning
/rest/{path}/fcr:versions
- GET the version history of the nt:file or the nt:folder (as appropriate) at {path}
...
/rest/fcr:tx
- POST create a new transaction session
/rest/{txid}/fcr:tx/{txid}
- GET the status of a transaction
/rest/{txid}/fcr:tx/{txid}/fcr:commit
- POST commit the transaction
/rest/{txid}/fcr:tx/{txid}/fcr:rollback
- POST abort the transaction
| Code Block |
|---|
POST /rest/fcr:tx retrievethe aLocation JSONheader orsends XMLyou transactionto object,the whichrepository alsoscoped containsby the transaction ID you requested (e.g. Location: /rest/tx:123456) POST /rest/tx:123456/fcr:new you can use that transaction ID at the beginning of (most) requests to execute that action within the context of the transaction POST /rest/tx:123456/fcr:tx/123456/fcr:commit and then save the transaction. Any operations you made within the scope of the transaction will be applied together, meaning if any of them fail, the whole transaction will fail. POST /rest/tx:123456/fcr:tx/123456/fcr:rollback roll it back and forget it ever happened |
...