Release to staging: SDI metadata extraction, %sdi and %metadata magics (ref #306883) - #71
Merged
Merged
Conversation
Release 0.1.18: Redmine notes from local git hooks, ref #308939
Release 0.1.19: remove Redmine hook test file, ref #308939
Redmine-Hook: v1
- sdi: SdiController.get_xml(uuid) downloads a record's ISO 19115-3 XML
from the SDI (GeoNetwork) REST API and checks it; push_to_dds() uploads
it to {dds_path}/metadata/{uuid}.xml as a document (not an ingest),
comparing with the DDS copy first; resolve_series() finds a series'
current release.
- dds_documents: DocumentsClient (put/get/exists/list) for plain files in
DDS folders. The endpoints are assumptions to confirm with the DDS team.
- %sdi magic over SdiSession, built like %catalog/%ingest from the kernel
environment; DDS_BASE_URL is read from the nearest .env.
- Test notebook debugger/sdi_session_example.ipynb, run_sdi_extract() in
debug_run.py, README section, complete .env.example, and the
development plan in docs/sdi-integration-plan.md (publication to SDI
deferred).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Redmine-Hook: v1
- %sdi (SdiSession) now only reads SDI: get_xml, resolve_series. - %metadata (MetadataSession) pushes metadata files to DDS: push_to_dds (defaults to the record %sdi get_xml fetched last) and dds_base_url. DDS_BASE_URL is read from the nearest .env when the session is built. - Tests, test notebook, README and plan updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Redmine-Hook: v1
SDI metadata extraction to DDS, %sdi and %metadata magics (ref #306883)
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| monkeypatch.chdir(nested) | ||
|
|
||
| assert find_dotenv() == tmp_path / ".env" | ||
| assert MetadataSession(env={}).dds_base_url().startswith("https://dds.parent.test") |
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
2 participants
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.
Promotes
developmenttostaging. Ref #306883.What's in it
eea_datalakehouse.sdi:SdiController.get_xml(uuid),push_to_dds()andresolve_series().eea_datalakehouse.dds_documents:DocumentsClient, which uploads documents and never ingests.%sdireads SDI (get_xml,resolve_series) and%metadatapushes to DDS (push_to_dds,dds_base_url).debugger/sdi_session_example.ipynb, README section, completedebugger/.env.example, and the plan indocs/sdi-integration-plan.md.Before the first real upload
dds_documents/client.pystill need confirming with the DDS team.Tests
444 passed, 1 skipped (the live SDI test).
🤖 Generated with Claude Code