Closed jordanpadams closed 1 week ago
What is the relationship between this issue and https://github.com/nasa-pds/pds-api/issues/148 ?
Can we document whether and where this feature is needed?
As I understand the conversation we had at https://github.com/nasa-pds/pds-api/issues/148, there is no deprecated context product LID that has a known referrer.
Isn't true that this feature would only be needed if there was a deprecated LID that had a referrer? Do we agree that this feature is not needed in any way to support context products? Where then is it needed?
@matthewtiscareno sorry I missed this. this ticket is a more simplified parent release theme that we track in our schedule. You are correct that the actual requirement is NASA-PDS/registry-api#427. there will be other follow-ons to NASA-PDS/registry-api#427 that will be sub-tasks for this ticket.
per the referrers, that may be the case for context product LIDs, but does not apply to M2020. we still need to get that list from them.
note: you probably cannot see the sub-tasks. I think if you install the ZenHub extension you should be able to see them.
📆 February Status: Task start delayed. May be descoped from build delivery due to other higher priority tasks. Will be included in point build if needed.
📆 March status: Descoped from B13.1 and discussed with SWG. Awaiting input from DDWG design for handling this to come up with a solid solution. Will add to end of B14.0 plans in hopes that design will be forthcoming.
Closing. Duplicate of https://github.com/NASA-PDS/registry-api/issues/427
💡 Description