As a user, I want to use properties common to multiple LDD across products, without caring about the actual LDD used.

[tloubrieu-jpl]

Checked for duplicates

Yes - I've already checked

🧑‍🔬 User Persona(s)

Data user.

💪 Motivation

...so that I can search for these properties accross missions and so that I don't need to know the specific property name for each mission.

📖 Additional Details

Details from Jordan's email on 04/05/2024:
Something we need to think about is how we can map all of these “different” attributes into 1. E.g. mission_phase_name is in almost every mission LDD, but an end user does not care that it is called vgr:Voyager_Timing.vgr:mission_phase_name for Voyager, cassini:Cassini_Timing.cassini:mission_phase_name for Cassini, or coolmission:Class:mission_phase_name for Cool Mission. We will need to figure out how to abstract this, not just through updart, but potentially through the Search API as a whole. This is where maybe something similar to those copyFields in Solr could really come in handy. Just things to think about.

Acceptance Criteria

Given a registry api service
When I perform I can select all the products related to mission phase
Then I expect all the product related to this phase, across mission

⚙️ Engineering Details

We need to discuss/be aware, that all the mission phase name enumeration might not be consistent across missions.