Cindy Wang [X] and I explored the initial Footprint-display UI this afternoon. After some discussion about how to handle on-image UI selection of Footprints, something which becomes more complicated when deblended Footprint parents and children are displayed at once, we developed the notion that it may be useful to Firefly to have the IDs of parents and children carried along in the JSON structure. While they will also be in the Object tables from which the Footprints will be taken, we do not yet have the structural metadata (e.g., a VO-DML data model) that would allow Firefly to recognize which columns carry this data, and in any event we cannot rule out a user wanting to browse an Object query result in which they didn't ask for the parent/child columns to be returned.
So I would ask David Shupe to look into a way to add this information to the JSON.
Cindy Wang [X] and I explored the initial Footprint-display UI this afternoon. After some discussion about how to handle on-image UI selection of Footprints, something which becomes more complicated when deblended Footprint parents and children are displayed at once, we developed the notion that it may be useful to Firefly to have the IDs of parents and children carried along in the JSON structure. While they will also be in the Object tables from which the Footprints will be taken, we do not yet have the structural metadata (e.g., a VO-DML data model) that would allow Firefly to recognize which columns carry this data, and in any event we cannot rule out a user wanting to browse an Object query result in which they didn't ask for the parent/child columns to be returned.
So I would ask David Shupe to look into a way to add this information to the JSON.