Repository navigation
feat(metadata): edit every Dublin Core term, and export or import RDF from the app - #83
Merged
Merged
Conversation
… from the app The metadata editor gains a "More Dublin Core" section (place, period, audience, source, alternative title and the rest of DCMI Metadata Terms), listing the RDF statements an import kept so they can be removed. The metadata page and a namespace's Collection page get an RDF menu (save as Turtle, JSON-LD, RDF/XML or N-Triples; copy the linked-data URI), and the Collection page an "Import RDF" dialog that previews before importing. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RtRigWmLLWqBHqWmJ8CvA1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Before: the RDF export and import from #79 and #82 were available only through the API. The metadata editor had no way to set Dublin Core terms such as place, period, audience or source.
After: the metadata editor has a new "More Dublin Core" section. It has one row per value, you pick the term from the full DCMI list, and it also lists the RDF statements an import kept, each with a button to remove it. The metadata page and each namespace's Collection page get an RDF menu to save as Turtle, JSON-LD, RDF/XML or N-Triples, or to copy the linked-data URI. The Collection page also gets Import RDF: you choose a file or paste it, see a preview of what would change and what matched nothing, and then import.
How:
components/iiif/rdf.tsxadds the menu, the import dialog and helpers. TheDublinCorefield is inmetadata-fields.tsx.metadata-model.tsnow knows thetermsandstatementsfields, with validation and history wording. No backend change.Tests:
__tests__/rdf-ui.test.tsxcovers the model, the helpers, editing terms and the import dialog. The full jest suite (574), eslint, tsc and prettier pass. Not checked in a browser.🤖 Generated with Claude Code
https://claude.ai/code/session_01RtRigWmLLWqBHqWmJ8CvA1
Generated by Claude Code