Publish dp02Schema tap-schema to -stable,-int, and idfint

[fritzm]

No description provided.

[gpdf]

I realize that this is not final. However, before its first deployment, can we at least harmonize the top level with what was done for DP0.1. The "schema" for DP0.1 was named "dp01_dc2_catalogs". Here it's just named "dp02". I think the same logic applies for including "_dc2" this time, so we should just do that. Regarding appending "_catalogs", that depends on whether the intent is to include the image metadata tables (the original "Exposure" and "Visit" tables) in the same "schema" (in the TAP sense of the word) as the catalogs.

One argument against doing so (and therefore keeping "_catalogs" for DP0.2) is that we've talked about a model (in the final system) where we host the catalog tables only on Qserv, and the image metadata tables both on Qserv and in the Consolidated Database, because the image metadata tables are useful in both contexts.

[gpdf]

For today's deployment I'll be happy if we just change to "dp02_dc2_catalogs", because there are no image metadata tables in this schema yet.

[fritzm]

@gpdf done re. dp02_dc2 rename (though not sure why that was a particularly good name choice the first time?)

Is there also a preference/direction on top level "@id:" for dp0.2 here?

[gpdf]

It was decided in collaboration with the CET, to make it clear right up front that the delegates were working with DC2 data.

[rra]

I don't really know much about this and will leave the review to Gregory.

requests addressed