Investigate use of graphql api by data science team for collecting submission data

[Cooryd]

We have been asked if it would be possible/ feasible to expose submission data through the graphql api served by the application for use by the data science team. If not would it be possible to run another service that exposed a graphql interface to the submission data.

Questions

• What impact might scraping the data from the production application make in terms of performance for users?
• If running another service for the sole purpose of data presentation, is graphql the best choice over REST?
• Would existing/ planned queries be sufficient for use by the data team? What are we currently exposing, what else needs exposing?
• Access control when querying submissions through public app, what changes would be needed?

Found problems

• Or schema view is currently broken probably due to how we are breaking up the schema fragment in the app. This should be fixed if the app is going to be used to query data.