Define which graph will store mint/official models.

[dgarijo]

The test database doesn't sound very permanent.
I agree that maybe the best way is to keep the MINT graph and then the users graph. The question is: shall we publish to the same endpoint or a different endpoint? Probably same endpoint make sense because then you can retrieve all queries. We make the graph configurable in the API call (it could be union graph or a particular graph).

• Remove reference to test database
• Create the mint graph
• Define the option: edit the queries or synchronize

[mosoriob]

The solution for me is to create a new graph called "mint."

However, this will affect other apps because the queries will need to change. So, I see two options

1. Edit the queries of the applications
2. Synchronize the default graph from the mint graph. The questions are:
   • Manually or automatically?
   • Do we want the same information on both graphs?

[dgarijo]

We should publish the current catalog in the "mint" graph, I agree. Or "Admin" graph. We can discuss this after this week, given the current deadlines