-
Notifications
You must be signed in to change notification settings - Fork 5
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
As a user, I want to search for all versions of a product where the LID changed during the product history #427
Comments
merged per NASA-PDS/registry-mgr#46 |
this was not actually closed out. this is only supported via registry, not the API |
Discussed at the management council:
|
It is very distressing to learn that examples of this issue exist. The first job of a LID is never to change. We have some formation rules for LIDs, but we need to make it more clear for future cases that those formation rules do not take precedence over the more important rule that a LID should never change. How many superseded LIDs are there? The issue report mentions only one. How easy would it be to obtain a complete list? Furthermore, how easy would it be to obtain a list of the data products that use superseded LIDs? Most importantly, we need an SCR to make it more clear for future cases that any LID formation rules do not take precedence over the more important rule that a LID should never change. This may involve a change to the Standards Reference and possibly other things as well. Comments regarding this? |
We've only changed (deprecated then replaced) LIDs that 1) have incorrect format based on the current formation rules, and 2) have no known referrers. The full list of deprecated LIDs (252 total):
|
@rchenatjpl can we actually have a CSV for this?
This is so we can track the mapping between the 2. |
Two of the old LIDs converted into multiple LIDs, so the .csv actually has 4 comma-separated columns |
Thank you, @rchenatjpl !! You say that all deprecated LIDs have no known referrers, though I think this statement is confined to context product LIDs. Be that as it may, shouldn't it be true (at least for domains within which it's true that deprecated LIDs have no referrers) that the issue in the initial request is not needed? |
Funny. If you type |
💪 Motivation
...so that I can browse through the provenance of a product
📖 Additional Details
Per the parent epic, and the design we need to update the API to implement these changes so we can sufficiently understand the version history.
For example,
Product A
changes its logical identifier from version "1" of the product (lid_x
) to version "2" (lid_y
), we want to know that these are actually revisions of the same product.NOTE: The versions may not be in appropriate ascending order, e.g. you could have
lid_x::1.0
andlid_y::1.0
, but reallylid_x::1
==Product A v1
andlid_y::1.0
==Product A v2
⚖️ Acceptance Criteria
Given the context products urn:nasa:pds:context:instrument:crs.vg1::1.0 and urn:nasa:pds:context:instrument:vg1.crs::1.0 ingested into the registry
When I perform a query of the API for
products/urn:nasa:pds:context:instrument:crs.vg1/all
Then I expect to see 2 records returned for
urn:nasa:pds:context:instrument:crs.vg1::1.0
andurn:nasa:pds:context:instrument:vg1.crs::1.0
Given the context products urn:nasa:pds:context:instrument:crs.vg1::1.0 and urn:nasa:pds:context:instrument:vg1.crs::1.0 ingested into the registry
When I perform a query of the API for
products/urn:nasa:pds:context:instrument:vg1.crs/all
Then I expect to see 2 records returned for
urn:nasa:pds:context:instrument:crs.vg1::1.0
andurn:nasa:pds:context:instrument:vg1.crs::1.0
Here are some more specific examples, let's say we have:
urn:nasa:pds:context:instrument:crs.vg1::1.0 (actually version 1 of this product)
urn:nasa:pds:context:instrument:vg1.crs::1.0 (actually version 2 of this product)
urn:nasa:pds:context:instrument:vg1.crs::2.0 (actually version 3 of this product)
/products/urn:nasa:pds:context:instrument:vg1.crs
I will geturn:nasa:pds:context:instrument:vg1.crs::2.0
(API defaults to latest version)/products/urn:nasa:pds:context:instrument:crs.vg1
I will geturn:nasa:pds:context:instrument:vg1.crs::2.0
(API defaults to latest version)/products/urn:nasa:pds:context:instrument:crs.vg1/latest
, I want to get backurn:nasa:pds:context:instrument:vg1.crs::2.0
/products/urn:nasa:pds:context:instrument:crs.vg1/all
, I want to get back all 3 versions (ordered by creation date time)./products/urn:nasa:pds:context:instrument:crs.vg1::1.0
, I want to get back 1 producturn:nasa:pds:context:instrument:crs.vg1::1.0
⚙️ Engineering Details
The text was updated successfully, but these errors were encountered: