-
Notifications
You must be signed in to change notification settings - Fork 2
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
Store records in their own repository contexts #6
Conversation
…generated by DAO instead of JOPA. This allows knowing the identifier before persist.
…ding to their identifiers. The record identifier is now based on its key, so that they can be derived from each other.
The configuration includes automatic repository creation.
This ensures only known roles are mapped, and they are mapped correctly to types used by the record manager.
Also add setup guide for the Docker Compose deployment.
Since this PR has not been merged, yet, the new changes implementing kbss-cvut/23ava-distribution#11 have been automatically added to it. |
Also I noticed that there is a draft of a ticket for migrating Record Manager from RDF4J to GraphDB. The Docker Compose setup I created uses GraphDB, so maybe that ticket can be closed as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just minor suggestions.
Co-authored-by: Miroslav Blaško <blcham@gmail.com>
Co-authored-by: Miroslav Blaško <blcham@gmail.com>
Co-authored-by: Miroslav Blaško <blcham@gmail.com>
Co-authored-by: Miroslav Blaško <blcham@gmail.com>
Co-authored-by: Miroslav Blaško <blcham@gmail.com>
Co-authored-by: Miroslav Blaško <blcham@gmail.com>
Implements kbss-cvut/23ava-distribution#10
Note that these changes are not compatible with existing data.