Fwd: Updating Learning Registry APIs

[Steve Midgley]

We had a productive, open phone call on Wednesday about how we can update Learning Registry to suit the active community's needs, as well as set up LR to make it much (much!) easier to innovate and develop on top of it. 

Here is a somewhat detailed document describing the changes we propose: https://docs.google.com/document/d/1rA4hnCyemFG-FyV9YyA9O60WzR2K-J2h2xjjhDJXlGg/edit#

In summary:

• Migrate from CouchDB to Postgres on the bottom end
• Implement only a small subset of existing APIs
• Publish: stays the same but with a new JWT signing option.
• List-records: stays the same
• slice: access/data improvements, but keep the same stateless, restful, easy-to-use nature
• Drop everything else. No obtain, no harvest, no sword, no oai-pmh, no replication. (Speak up if this will affect you).
• Note the path to deprecating these APIs will be reasonably slow..
• Enable some new functionality (made much easier by the above changes) - these changes were requested by Illinois and may not be in the initial MVP:
• View updates and deletes as part of the existing record
• View merges of multiple records about the same learning resource (graph-like search)
• Enable authenticated search, so you only see the graph for publishers you trust.
• Backup up the public network to an Archive.org collection
• Instead of replication, we'll backup/restore to Archive.org
• Private communities can backup to private S3 buckets (feature TBD)

That's the bulk of it! Feedback welcome!

Steve