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

Update response to move meta/node_name to meta/Tracking_Meta/curating_node_id #136

Open
jordanpadams opened this issue May 19, 2022 · 3 comments

Comments

@jordanpadams
Copy link
Member

💡 Description

Applies to pds4+json, pds4+xml, application/xml, and application/json response formats.

@alexdunnjpl
Copy link
Contributor

alexdunnjpl commented May 1, 2023

@tloubrieu-jpl @jordanpadams is this - specifically the renaming of the property from node_name to curating_node_id - actually supportable without either rehavesting everything, or manually rewriting that property for every registry document, with a registry-sweeper?

From what I've seen so far, it looks like the object properties from the registry docs are identified by their names (in this case "ops:node_name") and restructured by openapi-generator according to the specified schema in the swagger.yml

So unless there's support for ad-hoc mutation of keys, which I haven't found any reference to yet, this is probably a more significant change than intended (i.e. will be a registry-sweeper task, and ideally harvest would write the correct key during harvest going forward).

@alexdunnjpl
Copy link
Contributor

Breakout resolution - implement sweeper, fix harvest, deprecate sweeper some period of time later.

@alexdunnjpl
Copy link
Contributor

Deprioritized for the time begin, per Jordan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ToDo
Development

No branches or pull requests

4 participants