create initial version of end points that are compatible with RISE Repo

[gdevanla]

The PR addresses the following:

1. End points required to be compatible with the Rise Repository API has been provided.
2. Separate end points have been created and does overlap with current end points. Feedback on how to unify these is welcome
3. The collection UUID is hard-coded to 1.0 since corpus-db does not currently have an notion of collections.

@JonathanReeve I spoke to @pbelouin and have added these changes as a follow up to that conversation. This is a first iteration therefore feel free to provide feedback to streamline this API and make it better.

[JonathanReeve]

Looks good to me. Only thing I'd suggest is adding documentation for these points on the docs page. Ideally, there would be a way of automatically generating docs from the Haskell code (haddocs?), but I haven't learned how to do that, yet. I'll merge this now, and recompile the version on the server, as soon as I get a chance to test it, and open an issue for the documentation.

[pbelouin-mpiwg]

Hi Jonathan and Guru, thanks for this! Some documentation is available here: https://rise.mpiwg-berlin.mpg.de/pages/doc_for_resource_providers
Would this be a good starting point? If so I can probably clean it up and add it somewhere that you would deem appropriate?

[JonathanReeve]

Awesome. We can just copy-and-paste that, more or less, into the corpus-db docs. Pascal Belouin <notifications@github.com> writes:

…

Hi Jonathan and Guru, thanks for this! Some documentation is available here: https://rise.mpiwg-berlin.mpg.de/pages/doc_for_resource_providers Would this be a good starting point? If so I can probably clean it up and add it somewhere that you would deem appropriate? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.*