Skip to content

feat: button to magically LLM generater metadata via woo-hoo service - #253

Open
morrieinmaas wants to merge 2 commits into
GPP-Woo:mainfrom
morrieinmaas:feat_get_metadata_button
Open

feat: button to magically LLM generater metadata via woo-hoo service#253
morrieinmaas wants to merge 2 commits into
GPP-Woo:mainfrom
morrieinmaas:feat_get_metadata_button

Conversation

@morrieinmaas

@morrieinmaas morrieinmaas commented Jan 27, 2026

Copy link
Copy Markdown

Adds a button to the UI to call woo-hoo service (unreleased) to generate metadata based on official xml schema via LLM (Mistral).

Needs woo-hoo service released and deployed. Also first attempt - maybe there are better ways?

@felixcicatt felixcicatt Feb 3, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

something weird is going on with the path of this file. it makes it impossible for me to switch to your branch:
error: invalid path 'odpc.client/obj\Debug/\package.g.props'. can you check if you can delete the file and get it into the gitignore?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure will have a look

:gekoppelde-waardelijsten="gekoppeldeWaardelijsten"
/>

<div v-if="isAvailable && existingDocuments.length && !isReadonly && !hasError" class="generate-metadata">

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool! I think it might be wise to split the template parts into separate components as much as possible, to reduce potential merge hell whenever 'regular' features go to main

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure! makes total sense

@morrieinmaas

Copy link
Copy Markdown
Author

thanks already @felixcicatt for the feedback. There's some more work needed and some reconciliation with some furtehr changes from #262 but not all obviously. we can discuss shortly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants