Date: Fri, 29 Mar 2024 01:07:02 +0000 (UTC)
Message-ID: <874180883.21647.1711674427380@confluence>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_21646_129548692.1711674422366"
------=_Part_21646_129548692.1711674422366
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
The steps SUIT plan to access metaServ for information:
- get a list of databases, SUIT will provide this list to users as databa=
se options to choose.
- See PDAC, LSST Data =E2=86=92 Select Project, currently have thre=
e options
- Once user selects a database, SUIT will get a list of tables in this da=
tabase for users to choose
- See PDAC, Select Project =E2=86=92 wise 00, currently there are 5 =
tables under Catalogs and 4 under Images
- Once user selects the table to search, SUIT will get the list of column=
s for user to input search constraints
- See PDAC, the bottom section content changes as user selects different =
table
Details of information needed for each DB, table, column: (Please see th=
e two attached files as examples.)
- For each database, the following inform=
ation is needed"
- DB name,
- type (engineering data, prompt data, re=
lease data, user generated data)
- description,
- possible link to the formal document ab=
out this DB
- For each table, the following information will be needed:<=
br>
- Table name,
- type (image metadata, catalog - source/=
forced source, EFD-related),
- description,
- possible link to the formal document ab=
out this table
- For each column in a table, the following informatio=
n will be needed:
- UID (to identify columns that hold the =
primary position: ra and dec, filter band, unique objectID , image corners)=
- UType (extra =
info like the 4 corners of an image, ...),
- Column name,
- description,
- (?) short description to display in too=
ltips,
- unit,
- data type
- More information to facilitate a better user experience in=
UI design (this will need further discussion among SUIT and DAX teams)
- the name of multie=
poch photometry table, which contains the single-exposure measurements for =
every deep detection,
for example 'Science_Ccd_Exposure' for SDSS, 'allwise_p3as_mep' for WISE. T=
his is assuming there is one such table per database/schema.
- when a table has unique objectID, what is the name of mult=
i-epoch (forced photometry) table to get light curve queries for a unique o=
bjectID. This will enable the portal to provide a function linking the obje=
ctID to light curve data query directly.
- for deep coadd image meta data table, the name of the PVI =
meta data table so we can find the PVIs that were used to make the dee=
p coadd image.
- relationship with columns in other table ( objectID in object table t=
o objectID in source table), unless this relationship can be determin=
ed using UCDs
The reason behind the requests for the information:
- SUIT needs to provide a capability for users to browse all=
the possible metadata so users can decide what they want to explore furthe=
r.
- SUIT needs to display different UI depending on what user =
is interested in: catalogs, images, time series data, anything else.<=
/li>
- SUIT needs to overlay catalog sources and image footprints=
on a coverage image.
- SUIT needs to be able to display light curves of an object=
in various bands.
Security/data access concerns
Since all=
users will login to the system, the permission of access level will be con=
trolled by User Authorization system.
Concerns about handling LSST data types in dbserv.
- We'd like to keep getting metadata with the result set fro=
m dbserv to be able to interpret the result set without an extra call neede=
d. (Yes from DAX)
- Currently flag fields (bit type in db) is passed to us as =
string fields, ex. "b'\x00'". All int fields are passed as long. In general=
, I am concerned about custom python code, which converts mySQL types. (`https://gith=
ub.com/lsst/dax_dbserv/blob/master/python/lsst/dax/dbserv/compat/fields.py<=
/a>`) (may have been fixed)
- MySQL gives a hint of the display width of the field. Can =
we carry it over? (No for now)
- When the result set is empty, we should=
still get the metadata. (Yes from DAX)
=
------=_Part_21646_129548692.1711674422366
Content-Type: image/svg+xml
Content-Transfer-Encoding: 7bit
Content-Location: file:///C:/144eb07090dc8e0a44ce7e04a3c61370