All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
In DSpace 5, the REST API adds authentication, allows Creation, Update, and Delete to objects, can access restricted materials if authorized, and it requires SSL.
For localhost development purposes, SSL can add additional getting-started difficulty, so security can be disabled. To disable DSpace REST's requirement to require security/ssl, alter [dspace]/webapps/rest/WEB-INF/web.xml
or [dspace-source]/dspace-rest/src/main/webapp/WEB-INF/web.xml
and comment out the security<security-
constraint constraint>
block, and restart your servlet container. Production usages of the REST API should use SSL, as authentication credentials should not go over the internet unencrypted.
...
Example usage from command line in XML format with pretty printing:
Code Block |
---|
curl -s -H "Accept: application/xml" http://localhost:8080/rest/communities | xmllint --format - |
Example usage from command line in JSON format with pretty printing:
Code Block |
---|
curl -s -H "Accept: application/json" http://localhost:8080/rest/communities | python -m json.tool |
For this documentation, we will assume that the URL to the "REST" webapp will be http://localhost:8080/rest/ for production systems, this address will be slightly different, such as: http https://demo.dspace.org/rest/. The path to an endpoint, will go after the /rest/, such as /rest/communities, all-together this is: http://localhost:8080/rest/communities
Another thing to note is that there are Query Parameters that you can tack on to the end of an endpoint to do extra things. The most commonly used one in this API is "?expand". Instead of every API call defaulting to giving you every possible piece of information about it, it only gives a most commonly used set by default and gives the more "expensive" information when you deliberately request it. Each endpoint will provide a list of available expands in the output, but for getting started, you can start with ?expand=all, to make the endpoint provide all of its information (parent objects, metadata, child objects). You can include multiple expands, such as: ?expand=collections,subCommunities.
...
...
Anchor |
---|
...
|
...
Login to the REST API using a DSpace EPerson (user). It returns a token, that can be used for future authenticated requests (as a value of the rest-dspace-token request header).
Example Request:
curl -H "Content-Type: application/json" --data '{"email":"admin@dspace.org", "password":"dspace"}' http://localhost:8080/rest/login
Example Response:
1febef81-5eb6-4e76-a0ea-a5be245563a5
Invalid email/password combinations will receive an HTTP 403 Forbidden.
|
DSpace 6.x supports pagination by allowing two query parameters: limit
and offset
. Note however that the aggregate results number is not supplied (see DS-3887). Endpoints which return arrays of objects, such as /communities, /collections or /items, are "paginated": the full list is broken into "pages" which start at offset
from the beginning of the list and contain at most limit
elements. By repeated queries you can retrieve any portion of the array or all of it. The default value of offset
is 0 and the default value of limit
is 100. So, as an example, to retrieve the sixth through tenth elements of the full list of Collections, you could do this:
Code Block | ||
---|---|---|
| ||
curl -s -H "Accept: application/json" |
...
Logout from the REST API, by providing a header rest-dspace-token. After being posted this token will no longer work.
Example Request:
...
http://localhost:8080/rest/collections?offset=5\&limit=5 |
Note |
---|
REST API Authentication has changed in DSpace 6.x. It now uses a |
Method | Endpoint | Description |
---|
GET | / |
REST |
Example Request:
curl http://localhost:8080/rest/test
Example Response:
REST api is running.
API static documentation page listing available endpoints and their function. Example: | ||
POST | /login | Login to the REST API using a DSpace EPerson (user). It returns a |
. Example Request: |
curl -X GET -H "Content-Type: application/json" -H "Accept: application/json" -H "rest-dspace-token: f2f478e2-90f2-4e77-a757-4e838ae94154" http://localhost:8080/rest/status
Communities in DSpace are used for organization and hierarchy, and are containers that hold sub-Communities and Collections. (ex: Department of Engineering)
Collections in DSpace are containers of Items. (ex: Engineering Faculty Publications)
Items in DSpace represent a "work" and combine metadata and files, known as Bitstreams.
Bitstreams are files. They have a filename, size (in bytes), and a file format. Typically in DSpace, the Bitstream will the "full text" article, or some other media. Some files are the actual file that was uploaded (tagged with bundleName:ORIGINAL), others are DSpace-generated files that are derivatives or renditions, such as text-extraction, or thumbnails. You can download files/bitstreams. DSpace doesn't really limit the type of files that it takes in, so this could be PDF, JPG, audio, video, zip, or other. Also, the logo for a Collection or a Community, is also a Bitstream.
You can access the parent object of a Bitstream (normally an Item, but possibly a Collection or Community when it is its logo) through: /bitstreams/:bitstreamID?expand=parent
As the documentation may state "You must post a ResourcePolicy" or some other object type, this means that there is a structure of data types, that your XML or JSON must be of type, when it is posted in the body.
In DSpace, Communities, Collections, and Items typically get minted a Handle Identifier. You can reference these objects in the REST API by their handle, as opposed to having to use the internal item-ID.
Assembling a full representation of the community and collection hierarchy using the communities and collections endpoints can be inefficient. Retrieve a lightweight representation of the nested community and collection hierarchy. Each node of the hierarchy contains minimal information (id, handle, name).
Note: since the schema object contains no data fields, the following method has not been implemented: PUT /registries/schema/{schema_id}
Reporting Tools that allow a repository manager to audit a collection for metadata consistency and bitstream consistency. See REST Based Quality Control Reports for more information.
Collection Report Tool on demo.dspace.org
Metadata Query Tool on demo.dspace.org
Here are all of the data types, not all fields are necessary or supported when posting/putting content, but the output contains this information:
Community Object
{"id":456,"name":"Reports Community","handle":"10766/10213","type":"community","link":"/RESTapi/communities/456","expand":["parentCommunity","collections","subCommunities","logo","all"],"logo":null,"parentCommunity":null,"copyrightText":"","introductoryText":"","shortDescription":"Collection contains materials pertaining to the Able Family","sidebarText":"","countItems":3,"subcommunities":[],"collections":[]}
Collection Object
{"id":730,"name":"Annual Reports Collection","handle":"10766/10214","type":"collection","link":"/RESTapi/collections/730","expand":["parentCommunityList","parentCommunity","items","license","logo","all"],"logo":null,"parentCommunity":null,"parentCommunityList":[],"items":[],"license":null,"copyrightText":"","introductoryText":"","shortDescription":"","sidebarText":"","numberItems":3}
Item Object
{"id":14301,"name":"2015 Annual Report","handle":"123456789/13470","type":"item","link":"/RESTapi/items/14301","expand":["metadata","parentCollection","parentCollectionList","parentCommunityList","bitstreams","all"],"lastModified":"2015-01-12 15:44:12.978","parentCollection":null,"parentCollectionList":null,"parentCommunityList":null,"bitstreams":null,"archived":"true","withdrawn":"false"}
Bitstream Object
{"id":47166,"name":"appearance and physiology 100 percent copied from wikipedia.pdf","handle":null,"type":"bitstream","link":"/RESTapi/bitstreams/47166","expand":["parent","policies","all"],"bundleName":"ORIGINAL","description":"","format":"Adobe PDF","mimeType":"application/pdf","sizeBytes":129112,"parentObject":null,"retrieveLink":"/bitstreams/47166/retrieve","checkSum":{"value":"62778292a3a6dccbe2662a2bfca3b86e","checkSumAlgorithm":"MD5"},"sequenceId":1,"policies":null}
ResourcePolicy Object
[{"id":317127,"action":"READ","epersonId":-1,"groupId":0,"resourceId":47166,"resourceType":"bitstream","rpDescription":null,"rpName":null,"rpType":"TYPE_INHERITED","startDate":null,"endDate":null}]
MetadataEntry Object
{"key":"dc.description.abstract", "value":"This is the description abstract", "language": null}
User Object
{"email":"test@dspace.org","password":"pass"}
Status Object
...
Example Response:
Example of using JSESSIONID cookie for subsequent (authenticated) requests:
Invalid email/password combinations will receive an Please note, special characters need to be HTTP URL encoded. | ||||||||
GET | /shibboleth-login | Login to the REST API using Shibboleth authentication. In order to work, this requires additional Apache configuration. To authenticate, execute the following steps: 1. Call the REST Shibboleth login point with a Cookie jar:
2. This should take you again to the IdP login page. You can submit this form using curl using the same cookie jar. However this is IdP dependant so we cannot provide an example here. 3. Once you submit the form using curl, you should be taken back to the /rest/shibboleth-login URL which will return you the JSESSIONID. 4. Using that JSESSIONID, check if you have authenticated successfully:
| ||||||
POST | /logout | Logout from the REST API, by providing a Example Request:
After posting a logout request, cookie is invalidated and the "/status" path should show you as unauthenticated (even when passing that same cookie). For example:
Invalid token will result in HTTP 400 Invalid Request | ||||||
GET | /test | Returns string "REST api is running", for testing that the API is up. Example Request:
https://demo.dspace.org/rest/test Example Response:
| ||||||
GET | /status | Receive information about the currently authenticated user token, or the API itself (e.g. version information). Example Request (XML by default):
https://demo.dspace.org/rest/status Example Request (JSON):
Example JSON Response:
|
Before Shibboleth authentication for the REST API will work, you need to secure the /rest/shibboleth-login
endpoint. Add this configuration section to your Apache HTTPD Shibboleth configuration:
Code Block |
---|
<Location "/rest/shibboleth-login">
AuthType shibboleth
ShibRequireSession On
# Please note that setting ShibUseHeaders to "On" is a potential security risk.
# You may wish to set it to "Off". See the mod_shib docs for details about this setting:
# https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPApacheConfig#NativeSPApacheConfig-AuthConfigOptions
# Here's a good guide to configuring Apache + Tomcat when this setting is "Off":
# https://www.switch.ch/de/aai/support/serviceproviders/sp-access-rules.html#javaapplications
ShibUseHeaders On
require valid-user
</Location> |
You can test your configuration in 3 different ways:
https://dspace.myu.edu/rest/shibboleth-login
, this should redirect you to the login page of your IdP if you don't have a Shibboleth session yet./rest/shibboleth-login
URL. You should then see a blank page but in the response headers, the JSESSIONID cookie should be present./rest/status
and you should see information on the current authenticated ePerson.Code Block |
---|
curl -v -L -c cookiejar "https://dspace.myu.edu/rest/shibboleth-login" |
/rest/shibboleth-login
URL which will return you the JSESSIONID.Using that JSESSIONID, check if you have authenticated successfully:
Code Block |
---|
curl -v "https://dspace.myu.edu/dspace-rest/status" --cookie "JSESSIONID=0633C6379266A283E53F65DF8EF61AB9" |
_shibsession_64656661756c74687...
You can also grab this cookie from your browser.Double check that the cookie you took is valid:
Code Block |
---|
curl -v 'https://dspace-url/Shibboleth.sso/Session' -H 'Cookie: _shibsession_64656661756c7468747470733a2f2f7265706f7369746f72792e636172646966666d65742e61632e756b2f73686962626f6c657468=_a8d3ad20d8b655250c7357f7ac0e2910;' |
Use this cookie to obtain a Tomcat JSESSIONID:
Code Block |
---|
curl -v 'https://dspace-url/rest/shibboleth-login' -H 'Cookie: _shibsession_64656661756c7468747470733a2f2f7265706f7369746f72792e636172646966666d65742e61632e756b2f73686962626f6c657468=_a8d3ad20d8b655250c7357f7ac0e2910;' |
Use the returned JSESSIONID to check if you have authenticated successfully:
Code Block |
---|
curl -v "http://dspace-url/rest/status" --cookie "JSESSIONID=0633C6379266A283E53F65DF8EF61AB9" |
Communities in DSpace are used for organization and hierarchy, and are containers that hold sub-Communities and Collections (ex: Department of Engineering).
For an alternative way to create a Community/Collection hierarchy to the REST API take a look at Importing Community and Collection Hierarchy.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /communities | Return an array of all the communities in the repository. The results are paginated. Example: |
GET | /communities/top-communities | Return an array of all top-level communities. The results are paginated. Example: |
GET | /communities/{community id} | Return the specified community. Example: https://demo.dspace.org/rest/communities/e97b847b-2fd5-4751-8d91-fcf0d8895b81 |
GET | /communities/{community id}/collections | Return an array of collections of the specified community. The results are paginated. |
GET | /communities/{community id}/communities | Return an array of sub-communities of the specified community. The results are paginated. |
POST | /communities | Create a new community at top level. You must POST a community object data type. |
POST | /communities/{community id}/collections | Create a new collections in the specified community. You must POST a collection object data type. |
POST | /communities/{community id}/communities | Create a new sub-community in the specified community. You must POST a community object data type. |
PUT | /communities/{community id} | Update the specified community. You must PUT a community object data type. |
DELETE | /communities/{community id} | Delete the specified community. |
DELETE | /communities/{community id}/collections/{collection id} | Delete the specified collection in the specified community. |
DELETE | /communities/{community id}/communities/{sub-community id} | Delete the specified sub-community in the specified community. |
Collections in DSpace are containers of Items. (ex: Engineering Faculty Publications).
For an alternative way to create a Community/Collection hierarchy to the REST API take a look at Importing Community and Collection Hierarchy.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /collections | Return an array of all the collections in the repository. The results are paginated. |
GET | /collections/{collection id} | Return the specified collection. |
GET | /collections/{collection id}/items | Return an array all items of the specified collection. The results are paginated. |
POST | /collections/{collection id}/items | Create an item in the specified collection. You must POST an item object data type. |
POST | /collections/find-collection | Find collection by passed name. Returns the first exact match or nothing. You must POST a single string, not a JSON object. |
PUT | /collections/{collection id} | Update the specified collection. You must PUT a collection object data type. |
DELETE | /collections/{collection id} | Delete the specified collection. |
DELETE | /collections/{collection id}/items/{item id} | Delete the specified item in the specified collection. |
Items in DSpace represent a "work" and combine metadata and files, known as Bitstreams.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /items | Return an array of all the items in the repository. The results are paginated. Example: |
GET | /items/{item id} | Return the specified item. |
GET | /items/{item id}/metadata | Return metadata of the specified item. |
GET | /items/{item id}/bitstreams | Return an array of all the bitstreams of the specified item. The results are paginated. |
POST | /items/find-by-metadata-field | Find items by metadata entry. You must POST a metadataentry object data type. |
POST | /items/{item id}/metadata | Add metadata to the specified item. You must POST an array of metadataentry object data type. |
POST/GET | /items/{item id}/bitstreams?name={file name} | Add bitstream to the specified item. You must POST the file data and include the name parameter with the value as {file name} in the URL posted to.
description: A description of the bitstream. groupId: Id of group to set item resource policy to. year: Year to set embargo date to month: Month to set embargo date to day: Day of month to set embargo date to Example: /items/{item id}/bitstreams?name=The%20Children%27s%20Crusade%3A%20A%20Duty-Dance%20with%20Death.pdf&description=All%20this%20happened%2C%20more%20or%20less.&groupID=1969&year=2045&month=2&day=13 |
PUT | /items/{item id}/metadata | Update metadata in the specified item. You must PUT a metadataentry object data type. Each metadata entry that will replace all prior matching metadata entries, i.e. if you submit n 'dc.subject' entries all pre-existing 'dc.subject' entries in the item will be deleted and replaced with the n entries |
DELETE | /items/{item id} | Delete the specified item. |
DELETE | /items/{item id}/metadata | Clear the metadata of the specified item. |
DELETE | /items/{item id}/bitstreams/{bitstream id} | Delete the specified bitstream of the specified bitstream. |
Bitstreams are files. They have a filename, size (in bytes), and a file format. Typically in DSpace, the Bitstream will the "full text" article, or some other media. Some files are the actual file that was uploaded (tagged with bundleName:ORIGINAL), others are DSpace-generated files that are derivatives or renditions, such as text-extraction, or thumbnails. You can download files/bitstreams. DSpace doesn't really limit the type of files that it takes in, so this could be PDF, JPG, audio, video, zip, or other. Also, the logo for a Collection or a Community, is also a Bitstream.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /bitstreams | Return an array of all the bitstreams in the repository. The results are paginated. Example: |
GET | /bitstreams/{bitstream id} | Return the specified bitstream. |
GET | /bitstreams/{bitstream id}/policy | Return bitstream policies. |
GET | /bitstreams/{bitstream id}/retrieve | Return data of bitstream. |
POST | /bitstreams/{bitstream id}/policy | Add policy to item. You must POST a resourcepolicy object data type. |
PUT | /bitstreams/{bitstream id}/data | Update the data/file of the specified bitstream. You must PUT the data. |
PUT | /bitstreams/{bitstream id} | Update metadata of the specified bitstream. You must PUT a bitstream, does not alter the file/data. |
DELETE | /bitstreams/{bitstream id} | Delete the specified bitstream. |
DELETE | /bitstreams/{bitstream id}/policy/{policy id} | Delete the specified resource policy of the specified bitstream. |
You can access the parent object of a Bitstream (normally an Item, but possibly a Collection or Community when it is its logo) through: /bitstreams/:bitstreamID?expand=parent
As the documentation may state "You must post a ResourcePolicy" or some other object type, this means that there is a structure of data types, that your XML or JSON must be of type, when it is posted in the body.
In DSpace, Communities, Collections, and Items typically get minted a Handle Identifier. You can reference these objects in the REST API by their handle, as opposed to having to use the internal item-ID.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /handle/{handle prefix}/{handle suffix} | Returns a Community, Collection, or Item object that matches that handle. |
Assembling a full representation of the community and collection hierarchy using the communities and collections endpoints can be inefficient. Retrieve a lightweight representation of the nested community and collection hierarchy. Each node of the hierarchy contains minimal information (id, handle, name).
HTTP method | REST endpoint | Description |
---|---|---|
GET | /hierarchy | Retrieve a lightweight representation of the nested community and collection hierarchy. |
HTTP method | REST endpoint | Description |
---|---|---|
GET | /registries/schema | Return an array of all the schema in the registry |
GET | /registries/schema/{schema prefix} | Return the specified schema |
GET | /registries/schema/{schema prefix}/metadata-fields/{element} | Return the metadata field within a schema with an unqualified element name |
GET | /registries/schema/{schema prefix}/metadata-fields/{element}/{qualifier} | Return the metadata field within a schema with a qualified element name |
POST | /registries/schema/ | Add a schema to the schema registry. You must POST a schema object data type. |
POST | /registries/schema/{schema prefix}/metadata-fields | Add a metadata field to the specified schema. You must POST a metadatafield object data type. |
GET | /registries/metadata-fields/{field id} | Return the specified metadata field |
PUT | /registries/metadata-fields/{field id} | Update the specified metadata field |
DELETE | /registries/metadata-fields/{field id} | Delete the specified metadata field from the metadata field registry |
DELETE | /registries/schema/{schema id} | Delete the specified schema from the schema registry |
Note: since the schema object contains no data fields, the following method has not been implemented: PUT /registries/schema/{schema id}
Reporting Tools that allow a repository manager to audit a collection for metadata consistency and bitstream consistency. See REST Based Quality Control Reports for more information or test the Collection Report Tool or Metadata Query Tool on demo.dspace.org.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /reports | Return a list of report tools built on the REST API |
GET | /reports/{nickname} | Return a redirect to a specific report |
GET | /filters | Return a list of use case filters available for quality control reporting |
GET | /filtered-collections | Return collections and item counts based on pre-defined filters |
GET | /filtered-collections/{collection id} | Return items and item counts for a collection based on pre-defined filters |
GET | /filtered-items | Retrieve a set of items based on a metadata query and a set of filters |
Here are all of the data types, not all fields are necessary or supported when posting/putting content, but the output contains this information:
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"id":456,
"name":"Reports Community",
"handle":"10766/10213",
"type":"community",
"link":"/rest/communities/456",
"expand":["parentCommunity","collections","subCommunities","logo","all"],
"logo":null,
"parentCommunity":null,
"copyrightText":"",
"introductoryText":"",
"shortDescription":"Collection contains materials pertaining to the Able Family",
"sidebarText":"",
"countItems":3,
"subcommunities":[],
"collections":[]
} |
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"id":730,
"name":"Annual Reports Collection",
"handle":"10766/10214",
"type":"collection",
"link":"/rest/collections/730",
"expand":["parentCommunityList","parentCommunity","items","license","logo","all"],
"logo":null,
"parentCommunity":null,
"parentCommunityList":[],
"items":[],
"license":null,
"copyrightText":"",
"introductoryText":"",
"shortDescription":"",
"sidebarText":"",
"numberItems":3
} |
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"id":14301,
"name":"2015 Annual Report",
"handle":"123456789/13470",
"type":"item",
"link":"/rest/items/14301",
"expand":["metadata","parentCollection","parentCollectionList","parentCommunityList","bitstreams","all"],
"lastModified":"2015-01-12 15:44:12.978",
"parentCollection":null,
"parentCollectionList":null,
"parentCommunityList":null,
"bitstreams":null,
"archived":"true",
"withdrawn":"false"
} |
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"id":47166,
"name":"appearance and physiology 100 percent copied from wikipedia.pdf",
"handle":null,
"type":"bitstream",
"link":"/rest/bitstreams/47166",
"expand":["parent","policies","all"],
"bundleName":"ORIGINAL",
"description":"",
"format":"Adobe PDF",
"mimeType":"application/pdf",
"sizeBytes":129112,
"parentObject":null,
"retrieveLink":"/bitstreams/47166/retrieve",
"checkSum":{"value":"62778292a3a6dccbe2662a2bfca3b86e","checkSumAlgorithm":"MD5"},
"sequenceId":1,
"policies":null
} |
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"id":317127,
"action":"READ",
"epersonId":-1,
"groupId":0,
"resourceId":47166,
"resourceType":"bitstream",
"rpDescription":null,
"rpName":null,
"rpType":"TYPE_INHERITED",
"startDate":null,
"endDate":null
} |
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"key":"dc.description.abstract",
"value":"This is the description abstract",
"language": null
} |
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"namespace": "example.org/myschema",
"prefix": "myschema"
} |
Anchor | ||||
---|---|---|---|---|
|
Code Block |
---|
{
"description" : "myschema test field",
"element" : "test",
"name" : "myschema.test",
"qualifier": null
} |
Code Block |
---|
{
"email":"test@dspace.org",
"password":"pass"
} |
Code Block |
---|
{ "okay":true, "authenticated":true, "email":"test@dspace.org", "fullname":"DSpace Test User", "token":"6d45daaa-7b02-4ae7-86de-a960838fae5c" } |
...
Property | rest.stats |
---|---|
Example Value | true |
Informational Note | Boolean value indicates whether statistics should |
be recorded for access via the REST API; Defaults to 'false'. |
Note that if the logging level (in the logging configuration) is set to DEBUG the REST API will output the entire transaction to the logs. In cases where changes are being made to metadata by automatic processes this can result in several gigabyte sized logs depending on the volume.
For the purpose of more accurate statistics, a web-based tool may specify who is using it, by adding parameters to the request:
Code Block |
---|
http://localhost:8080/rest/items/:ID?userIP=ip&userAgent=userAgent&xforwardedfor=xforwardedfor |
If no parameters are given, the details of the HTTP request's sender are used in statistics. This enables tools to record the details of their user rather than themselves.
The dspace-rest module is automatically configured to compile and build with DSpace 4.0, so a mvn+ant process will create the webapp. To make it work in your environment, you would just need to add a context entry for it in your servlet container. For example, in tomcat, one might alter $CATALINA_HOME/conf/server.xml and add:
Code Block | ||
---|---|---|
| ||
<Context path="/rest" docBase="/dspace/webapps/rest"/>
|
If no parameters are given, the details of the HTTP request's sender are used in statistics. This enables tools to record the details of their user rather than themselves.
Additional information can be found in the README for dspace-rest, and in the GitHub Pull Request for DSpace REST (Jersey).
Usage examples can be found at: https://github.com/BrunoNZ/dspace-rest-requests
A tutorial on item deposits, together with Postman examples is available at
Widget Connector | ||
---|---|---|
|