External API dependecies crash DAMAP during export #470
Description
Changes
Right now, if e.g. re3data is down and we try to export, DAMAP crashes with a 500 error. This is of course bad, since we tie our tool to the whims of the re3data API. To remedy this, first find all instances of external APIs being called during the export. Then wrap them all with try catch. If you catch an error, due to an external service being unavailable, replace the text with a reminder that we couldnt fetch the info there. E.g. re3data is down, so in the place of the repository description, we write something like re3data was not available. This shopuld be the description fetched from re3data. To get this information, please try tzo export at a a later date. (For the exact verbiage, consult Christiane)
Additional notes
This solution was discussed with Tomasz.
Acceptance Criteria
Export does not crash when external dependecies are down. Instead of the text that would have been fetched, a remindertext is exported. Also please write comments onw hy this try catch is there.