2. Request parameter “detail” doesn’t seem to be doing anything [in get and list communities, the only place this was tested]. Results appear the same for the three specified values “extended”, “standard” and “minimum”.

3. “Failure processing entity request” error in many places in the API due to badly handled context object. FIXED in many places in DSpace REST API in our branch on github.

4. Copyright and Intro text sections returned null in the API for /collections request. The issue was FIXED in our branch.

5. /collections/id/invalid_element should return BAD REQUEST error code but returns a response with NULL in the data attribute.

6. When fetching items, the field “collection” has a field “countItems” that is set to 0. This should be set to number of items in collections. The issue was FIXED in our branch.

7. In retrieving a specific item, the attribute “communities” should have the listed item in the “Recent Submissions” array within the community. But it does not have this.

8. When you retrieve a particular element for any entity, if the data for the element is of a simple data type (string/number/boolean), it is returned in the key “data” in the response object. However, if the data to be returned is another entity (in form of another JSON object) then the keys inside the expected JSON object are returned as a part of the response JSON object itself, instead of appearing as a JSON object value for the “data” field. For example, if we request “anchester” element on a specific community with a resquest such as GET community/1/anchester, we get the following structure:

{
“name”: ….,
“id”: …,
“collections”: …,
…
“entityURL”: …,
“entity”: …
}
Whereas the expected behaviour should be:

{
“data”: {
“name”:…,
“id”: …,
“collections”: …,
…
}
“entityURL”: …,
“entity”: …
}
NOTE: This behaviour is not exhibited when the requested element is a list of entities. (eg. collections).

9. Elements with “null” in data return with a “Not Found Exception” and a 404 status code rather than response JSON object with “data” key with null value. We are not sure whether this is the expected behaviour or a bug.

10. Handle for bitstreams is null. Is there supposed to be one?

11. Result count in search results returns “actual_count – 1″. So if the search returns 10 items then the item count will be 9.