You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I merged #181, started working on #224 and then realized that all my collections were gone. Or rather, they don't appear in the frontend anymore because my old testing collections are stored in the relational database while the backend now attempts to retrieve them from the triplestore.
This needs to be addressed before we can deploy from the develop branch.
The text was updated successfully, but these errors were encountered:
There is a convert_legacy_data module in the backend which defines functions for this, but it's not used.
I believe the reason why collections are not migrated in #181 was the interdependencies between records, collections, and annotations; this makes it difficult to migrate one model but not the other.
I merged #181, started working on #224 and then realized that all my collections were gone. Or rather, they don't appear in the frontend anymore because my old testing collections are stored in the relational database while the backend now attempts to retrieve them from the triplestore.
This needs to be addressed before we can deploy from the
develop
branch.The text was updated successfully, but these errors were encountered: