Update object/lightcurve fetching

[RoyWilliams]

This morning's discussion raised the point that Lasair doesn't offer the ability for a user to fetch everything that LSST gave us. I have looked at the two API methods we have now, which have of course grown by accretion:

• the API method lightcurves returns object_lite
• the API method objects returns object_lite + lasair_added

where object_lite means a few selected attributes from the sources and forced sources:

    SELECT diaSourceId, midPointMjdTai, ra, decl, band, psfFlux, psfFluxErr from diaSources
    SELECT midPointMjdTai, band, psfFlux, psfFluxErr from diaForcedSources

and lasair_added means Lasair added value, such as:

• ra, dec, min/max time, ecliptic/galactic
• sherlock for this object,
• annotations this object has,
• image_urls for all cutouts,
• TNS information,

My suggestion going forward adds a new object_full that can be fetched, with everything from LSST. The suggested action plan is then:

• remove the lightcurves method from API
• the object method can be called with two extra arguments
  • lite=True/False
  • lasair_added=True/False
• remove the ability to resolve a list of objects, so you just pass one diaObjectId

[RoyWilliams]

Let's add to lasair_added all the features added by Lasair

SELECT * FROM objects_core WHERE diaObjectId=999999

where objects_core is a VIEW of the extended table -- chosen columns from objects

[gpfrancis]

Agree in principle, but I think the terminology should be consistent with what we do in the UI, e.g. "core" vs "extended" attributes. We should therefore hold off on implementation until we've go that sorted.

[RoyWilliams]

Is every core attribute also in the extended, or are they disjoint?