Changes between Version 9 and Version 10 of pstamp_2015-04-changes
- Timestamp:
- Apr 15, 2015, 1:08:29 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
pstamp_2015-04-changes
v9 v10 16 16 be more of an exceptions list and is not encouraged. 17 17 18 At this time no checks are made that an email address supplied through an IPP only request submission actually works.IPP portion of the system does not automatically send any email.18 At this time no checks are made that an email address in a request submitted outside of PSI actually works. It is really more of a token. IPP portion of the system does not automatically send any email. 19 19 20 20 If the email address' domain is unknown to the system. Postage stamp results will be given the default access level (1) unless the specific user has been flagged with greater access level. 21 21 A user with the default access level may get results from single frame observations made prior to 2015-03-01. Access to stacks 22 is controlled using a new accessLevelcolumn in the ippRelease table in the IPP database.22 is controlled based on a new column in the ippRelease table in the IPP database. 23 23 24 == The postage stamp simages and other results may be directed to a different data store location than previously ==24 == The postage stamp images and other results may be directed to a different data store location than previously == 25 25 26 26 Currently most postage stamp results are posted to filesets in a single data store product "pstampresults". This product is accessible through HTTP requests from … … 31 31 If the system can't figure out a specific product for the user the results will continue to go to pstampresults. 32 32 33 The data store links that PSI uses will automatically resolve to the new locations. 34 33 35 === Other implementation changes === 34 36 There are also some minor changes to the postage stamp implementation that are being made at this time. These primarily apply to requests submitted outside of PSI and are being made to improve 35 37 parsing performance. 36 38 37 * Currently if requests do not supply a survey or release the system for look ups by coordinate or skycell fall back to a list of "default data_groups". Over time this list has fallen woefullly out of date. (For an embarassingly long time PV3 was not included) This concept is removed. If no release parameters are included in the request SURVEY is set to 3PI. The DATA_GROUP column in the request specification is still respected but they havebeen obsolete since SURVEY and IPP_RELEASE were added.39 * Currently if requests do not supply a survey or release the system for look ups by coordinate or skycell fall back to a list of "default data_groups". Over time this list has fallen woefullly out of date. (For an embarassingly long time PV3 was not included) This concept is removed. If no release parameters are included in the request SURVEY is set to 3PI. The DATA_GROUP column in the request specification is still respected if supplied, but this parameter has been obsolete since SURVEY and IPP_RELEASE were added. 38 40 * For skycell images if a tess_id is not supplied with the request, it defaults to the most appropriate tessellation based on the survey. For 3PI the tess_id is set to RINGS.V3. For the medium deep fields tess_id is set to the V3 version. For example MD01.V3. 39 41
