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

Issue with migration scripts and local files #1142

Open
dylan-sa opened this issue Aug 2, 2024 · 1 comment · May be fixed by #1147
Open

Issue with migration scripts and local files #1142

dylan-sa opened this issue Aug 2, 2024 · 1 comment · May be fixed by #1147
Assignees
Labels
impact: patch No new functionality or changes in human-readable semantics (e.g,. fixing a typo in an annotation)

Comments

@dylan-sa
Copy link
Contributor

dylan-sa commented Aug 2, 2024

One use case for the migration scripts is to run them over local ontology/vocabulary files to capture updates. Our README points out limited support for named graphs when the scripts are run over local files using onto-tool. Since named graphs are used in queries/action/default, running these queries over local files generates the following error (as expected):

raise Exception(
Exception: You performed a query operation requiring a dataset (i.e. ConjunctiveGraph), but operating currently on a single graph.

Commenting out the minus {named graph pattern} portion of these queries gets them to work. I think the queries in this directory will still work well when run from a triplestore, but I wonder if we can find a way to better accommodate the local file use case. This might just be adding some additional notes to the README or queries.

See also #1140.

@dylan-sa dylan-sa added the impact: patch No new functionality or changes in human-readable semantics (e.g,. fixing a typo in an annotation) label Aug 2, 2024
@rjyounes
Copy link
Collaborator

rjyounes commented Aug 8, 2024

Implement as documentation updates along with #1140.

@philblackwood philblackwood linked a pull request Aug 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact: patch No new functionality or changes in human-readable semantics (e.g,. fixing a typo in an annotation)
Projects
Status: In Triage
Development

Successfully merging a pull request may close this issue.

3 participants