...
Status | ||||||
---|---|---|---|---|---|---|
|
Anchor
...
Create a new automatically-named child node or datastream at the given pathCreate a new child node at the given path. Status colour Blue title POST
Query Parameters:
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||||
---|---|---|---|---|---|---|
|
Request Headers:
Lock-Token (Optional) a Lock-Token for any locks previously created on resources updated by this operation
Example (1):
Code Block |
---|
curl -X POST "http://localhost:8080/rest/" |
Response:
Code Block |
---|
Status: 201 Created
Headers:
Location: http://localhost:8080/rest/some/path/to/a/new/resource |
Example (2):
Code Block |
---|
curl -X POST "http://localhost:8080/rest/?mixin=fedora:datastream" # Create a fedora:datastream |
Status:
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||||
---|---|---|---|---|---|---|
|
Create a new node as a child of the given node Status colour Blue title POST
If the given resource path exists, a POST to that path will create a new node as a child of the given resource using a generated identifier.
Request Headers:
Status | ||||
---|---|---|---|---|
|
Lock-Token (Optional) a Lock-Token for any locks previously created on resources updated by this operation
Note |
---|
The slug you provide does not guarantee the location of the created node. Clients must check the Location header for the path to the created resource. For full control over the generated path, see POST Create a new node at the given path. |
Query Parameters:
Status | ||||
---|---|---|---|---|
|
Example (1):
Code Block |
---|
curl -X POST -H "Slug: new-node-name" "http://localhost:8080/rest/" |
Response:
Code Block |
---|
Status: 201 Created
Headers:
Location: http://localhost:8080/rest/new-node-name" |
Status:
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||||
---|---|---|---|---|---|---|
|
Create a new node and populate some properties Status colour Blue title POST
In addition to creating a new node, add the given properties to the object
Note |
---|
An RDF payload can be combined with any of the above forms. |
Note |
---|
RDF will be interpreted using the current resource as the base URI (e.g. <> will be expanded to the current URI). Namespaces must be declared in full. |
Request Headers:
Status | ||||
---|---|---|---|---|
|
Lock-Token (Optional) a Lock-Token for any locks previously created on resources updated by this operation
Query Parameters:
Status subtle true title checksum
Example:
Code Block |
---|
curl -X POST -H "Content-Type: text/turtle" --data-binary "@body.rdf" "http://localhost:8080/rest/node/to/create"
Request Body:
PREFIX dc: <http://purl.org/dc/elements/1.1/>
<> dc:title "some-resource-title"
|
Response:
Code Block |
---|
Status: 201 Created
Headers:
Location: http://localhost:8080/rest/node/to/create |
Status:
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||||
---|---|---|---|---|---|---|
|
Create a new node and execute a SPARQL-Update query Status colour Blue title POST
In addition to creating a new node, execute a SPARQL-Update query against the newly created node.
Request Headers:
Status | ||||
---|---|---|---|---|
|
Lock-Token (Optional) a Lock-Token for any locks previously created on resources updated by this operation
Query Parameters:
Status subtle true title checksum
Note |
---|
RDF will be interpreted using the current resource as the base URI (e.g. <> will be expanded to the current URI) |
Example:
Code Block |
---|
curl -X POST -H "Content-Type: application/sparql-update" --data-binary "@body.rdf" "http://localhost:8080/rest/node/to/create"
Request Body:
PREFIX dc: <http://purl.org/dc/elements/1.1/>
INSERT {
<> dc:title "some-resource-title" .
}
WHERE { }
|
Response:
Code Block |
---|
Status: 201 Created
Headers:
Location: http://localhost:8080/rest/node/to/create |
Status:
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||||
---|---|---|---|---|---|---|
|
Create a new resource with binary content Status colour Blue title POST
Note |
---|
If the binary content is RDF or a SPARQL-Update query, see Binary Content for an alternative way to create content |
Query Parameters:
Checksum of the binary content (in the form urn:sha1:<sha-hash>). If the checksum doesn't match, an error will be returned. Status subtle true title checksum
Header Parameters:
The filename provided in the content disposition header will be stored in a premis:hasOriginalName property. Status subtle true title Content-DISPOSITION
Lock-Token (Optional) a Lock-Token for any locks previously created on resources updated by this operation
Example (1):
(Optional) The filename provided in the content disposition header will be stored in a premis:hasOriginalName property. Status subtle true title Content-Disposition
(Optional) MIME type of the uploaded datastream or RDF content. Status subtle true title Content-Type
Note |
---|
If the MIME type corresponds to a supported RDF format or SPARQL-Update, the uploaded content will be parsed as RDF and used to populate the child node properties. RDF will be interpreted using the current resource as the base URI (e.g. <> will be expanded to the current URI). Namespaces must be declared in full. For other MIME types, the uploaded content will be used to create a datastream. |
(Optional) A Lock-Token for any locks previously created on resources updated by this operation. Status subtle true title Lock-Token
(Optional) A suggested name for the new child resource, which the repository may ignore. Status subtle true title SLUG
Note |
---|
The slug you provide does not guarantee the location of the created node. Clients must check the Location header for the path to the created resource. For full control over the generated path, see XXX. |
Example (1): Create a new child node
Code Block |
---|
curl -X POST "http://localhost:8080/rest/" |
Response:
Code Block |
---|
Status: 201 Created
Headers:
Location: http://localhost:8080/rest/some/path/to/a/new/resource |
Example (2): Create a new child datastream
Code Block |
---|
curl -X POST "http://localhost:8080/rest/?mixin=fedora:datastream" # Create a fedora:datastream |
Example (3): Create a new node with RDF properties
Code Block |
---|
curl -X POST -H "Content-Type: text/turtle" --data-binary "@body.rdf" |
Code Block |
curl -X POST --upload-file picture.jpg "http://localhost:8080/rest/binary/resource/to/create"/" Request Body: PREFIX dc: <http://purl.org/dc/elements/1.1/> <> dc:title "some-resource-title" |
Response:
Code Block |
---|
Status: 201 Created Headers: Location: http://localhost:8080/rest/binarynew/resource/to/create/fcr:contentnode/uri |
Example (24): Uploaded file with checksum
Code Block |
---|
curl -X POST --data-binary "@picture.jpg" "http://localhost:8080/rest/binary/resource/to/createparent/object?checksum=urn:sha1:cb1a576f22e8e3e110611b616e3e2f5ce9bdb941" |
...
Code Block |
---|
Status: 201 Created Headers: Location: http://localhost:8080/rest/binary/resource/to/createparent/object/auto/generated/ds/id/fcr:content |
Example (35): Uploaded file with checksum mismatch
Code Block |
---|
curl -X POST --data-binary "@picture.jpg" "http://localhost:8080/rest/binary/resource/to/createparent/object?checksum=urn:sha1:checksumdoesntmatch" |
...
Note |
---|
By convention, binary content is accessed using the REST endpoint path/to/resource/fcr:content. |
Status:
Status | ||||||
---|---|---|---|---|---|---|
|
Status | ||||||||
---|---|---|---|---|---|---|---|---|
|
Status | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
Modify the triples associated with the resource Status colour Yellow title PUT
...