Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate old-style collections to triplestore #226

Open
jgonggrijp opened this issue Oct 3, 2024 · 2 comments
Open

Migrate old-style collections to triplestore #226

jgonggrijp opened this issue Oct 3, 2024 · 2 comments
Labels
blocking! Application cannot be deployed until we address this.

Comments

@jgonggrijp
Copy link
Contributor

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.

@jgonggrijp jgonggrijp added the blocking! Application cannot be deployed until we address this. label Oct 3, 2024
@jgonggrijp jgonggrijp added this to EDPOP Oct 3, 2024
@jgonggrijp jgonggrijp moved this to Todo in EDPOP Oct 3, 2024
@lukavdplas
Copy link
Contributor

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.

@jgonggrijp
Copy link
Contributor Author

Makes sense. That does mean we have to implement migrations for all three before we can deploy off develop again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocking! Application cannot be deployed until we address this.
Projects
None yet
Development

No branches or pull requests

2 participants