Add AspaceController to Curate

[abelemlih]

Backend portion of #85

• [ ] Add controller with the following methods: #repositories to fetch all repositories, and #find_by_id to fetch a resource by repository id and call number

• [ ] Format Aspace data to fit Curate's business logic. For language, we should use the ISO 639-2 standard. For holding repository and administrative unit, we should use the mapping in this document.

• [ ] Add routes to access Aspace data on Curate: /aspace/repositories and /aspace/find_by_id?repository_id=&call_number=

[abelemlih]

@erussey for testing, please provide a list of call numbers. I will then send you the JSON output for each call number for verification.

[erussey]

@abelemlih : Can you send me the following call numbers: Rose: Manuscript No. 1061, Manuscript No. 754 EUA: Series No. 19 Oxford: Series No. 010, Manuscript Collection No. 035 Pitts: Record Group No. 057

[abelemlih]

@erussey I emailed you the testing data, let me know if you have any questions/feedback.

[erussey]

@abelemlih : The holding repository information for Series No. 19 example isn't quite right. The holding_repository for Emory University Archives should be mapped to "Stuart A. Rose Manuscript, Archives, and Rare Book Library" . Otherwise looks good.

[abelemlih]

@erussey I added the change requested above, please refer to the updated response that I just emailed you. Let me know if you have any additional feedback.