Skip to content

Compare metadata workflow - #103

Draft
mairasalazar wants to merge 3 commits into
inveniosoftware:mainfrom
mairasalazar:compare-metadata-workflow
Draft

mairasalazar wants to merge 3 commits into
inveniosoftware:mainfrom
mairasalazar:compare-metadata-workflow

Conversation

@mairasalazar

Copy link
Copy Markdown
Collaborator

Description

  • refactor(tests): move activity tests to dedicated directory
  • feat(workflow): add compare_metadata workflow
    Add the compare_metadata_with_llm activity to compare pairs of metadata fields (suggested vs current metadata). The LLM judges whether the current metadata describes the underlying file.
    The CompareMetadata workflow calls the PDF text extraction, LLM metadata suggestion, vocabulary resolution, and the new comparison activity.
  • feat(schema): match and normalize for comparison pair
    Add matches()/normalize_for_comparison() to Creator, ResolvedLicense and ResolvedFunding so _align() can pair suggested vs. current metadata fields (from the deposit form).
    Since normalize_for_comparison() requires the funder's name from the id, we also move FUNDER_ROR_IDS to extracted_metadata.py and derive FUNDER_NAMES_BY_ROR_ID from it.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

  1. You license your contribution under the same terms as the current repository’s license.
  2. You agree that you have the right to license your contribution under the current repository’s license.

Add `matches()`/`normalize_for_comparison()` to Creator, ResolvedLicense
and ResolvedFunding so `_align()` can pair suggested vs.
current metadata fields (from the deposit form).

Since `normalize_for_comparison()` requires the funder's name from the
id, we also move FUNDER_ROR_IDS to extracted_metadata.py and derive
FUNDER_NAMES_BY_ROR_ID from it.
Add the `compare_metadata_with_llm` activity to compare pairs of
metadata fields (suggested vs current metadata). The LLM judges whether
the current metadata describes the underlying file.

The `CompareMetadata` workflow calls the PDF text extraction, LLM
metadata suggestion, vocabulary resolution, and the new comparison
activity.
@mairasalazar
mairasalazar force-pushed the compare-metadata-workflow branch from ded7a39 to f4297d8 Compare September 11, 2026 12:16
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.

1 participant