search

cxcsds / ciao-contrib

Extra scripts and code to enhance the capabilities of CIAO.
GNU General Public License v3.0
8 stars 6 forks source link

allow catalog=latest for search_csc / obsid_search_csc? #850

Closed DougBurke closed 2 months ago

DougBurke commented 9 months ago

Using catalog=latest would mean the calls are made with no catalog version, which will then return the latest finalised version (so it's not the same as the current catalog=current).

It saves uses from caring about what catalog setting to use for people who just want the latest-and-greatest...

kglotfelty commented 8 months ago

Is there a way to know what release latest actually is?

DougBurke commented 8 months ago

I don't believe so (we could identify the latest ascds-release value, or whatever the column is, but that doesn't tell us anything that useful)

On Sun, Jan 14, 2024, 07:56 Ken Glotfelty @.***> wrote:

Is there a way to know what release latest actually is?

— Reply to this email directly, view it on GitHub https://github.com/cxcsds/ciao-contrib/issues/850#issuecomment-1890945571, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABW27QTQ44RJ3RHQNTAFXTYOPIWBAVCNFSM6AAAAABBVI4L66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQHE2DKNJXGE . You are receiving this because you authored the thread.Message ID: @.***>

kglotfelty commented 8 months ago

Humm ... that concerns me. In the short transition time between when 2.1 is released and when we release the updated code to allow the specific "2.1" option -- I'd rather see users continue to use 'current' or continue to use the 2.0 release. At least with current all bets are off (no idea if columns, joins, data products, etc) are correct whereas the actual releases are correct (for that specific release).