Add a new column about particle type in the HE Obscore extension

[bkhelifi]

For the advanced products (e.g. maps, spectra), it is very usefull that one can query of type of particules (e.g. proton, antiproton, neutrino tau). Adding a collumn will be usefull for that.

To implement that, one should find a solution to handle both use cases:

• product generated by one single particule type (e.g. antiproton)
• product generated by a set of particles (e.g. proton and antiproton, or iron group, or all cosmic rays)

As reminder, decoding a string (for a list) into a query field is a bit unefficient. But it can be a reasonable cost.

Any thought @kosack and YouSchnabel ?

[iannevans]

For the advanced products (e.g. maps, spectra), it is very usefull that one can query of type of particules (e.g. proton, antiproton, neutrino tau). Adding a collumn will be usefull for that.

To implement that, one should find a solution to handle both use cases:

• product generated by one single particule type (e.g. antiproton)
• product generated by a set of particles (e.g. proton and antiproton, or iron group, or all cosmic rays)

As reminder, decoding a string (for a list) into a query field is a bit unefficient. But it can be a reasonable cost.

Any thought @kosack and YouSchnabel ?

Francois pointed out that there is an IVOA vocabulary for messengers that is used by the registry: https://www.ivoa.net/rdf/messenger/2020-08-26/messenger.html

It's not particularly complete in the HEA regime, but may be a good starting point. We could consider adding an attribute
obscore_hea.messenger_type (or obscore_hea.messenger) as a string that can take the values suggested in the vocabulary, and suggest additions to the vocabulary to cover the other cases we need (e.g., Cosmic-ray, Lepton, Hadron, ... ???).