REST API Needs (for an Angular 2 UI)

DSpace-Labs / angular2-ui-prototype

(OBSOLETE: Use https://github.com/DSpace/dspace-angular) Ongoing work on Angular UI has moved to DSpace/dspace-angular

https://github.com/DSpace/dspace-angular

Other

7 stars 10 forks source link

REST API Needs (for an Angular 2 UI) #154

Open tdonohue opened 8 years ago

tdonohue commented 8 years ago

This ticket is simply a list of known "gaps" in the current (DSpace 5/6) REST API which were encountered during the building of the Angular 2 Prototype.

Please feel free to add to this list!

REST API Needs:

CORS Headers - Currently this prototype "injects" such necessary headers via a Proxy
~~Recently Added Items~~ item sorting parameters (for homepage / Community/Collection homepages)
Search capabilities (via Solr)
Counts of sub-communities / collections in a Community request (see https://jira.duraspace.org/browse/DS-3126)

tdonohue commented 8 years ago

MIT has developed their own "read-only" backport DSpace REST API, which is an entirely custom implementation. This may be a resource for ways to simplify our existing REST implementation: https://github.com/MITLibraries/backrest

helix84 commented 8 years ago

What Richard also suggested we use instead of REST API is GraphQL, which gives API clients much bigger flexibility to specify what exactly they want instead of asking for fields (default set of fields or all fields) and then throwing most of them away.

To get the idea of GraphQL in a few words, see: https://medium.com/chute-engineering/graphql-in-the-age-of-rest-apis-b10f2bf09bba#44f9