regan-sarwas
commented
5 years ago An example of two layers that seem fine, but do not work in Theme Manager are:
- Alaska Region Theme List\YUCH Themes\Administrative / Infrastructure\YUCH Coal Creek Archeology Survey- 2004 to 2005\Coal_Creek_Nat_Hist_District
- Alaska Region Theme List\YUCH Themes\Administrative / Infrastructure\YUCH Coal Creek Archeology Survey- 2004 to 2005\Dredge_Tailing
These two give: Unable to stylize the metadata content: The request was aborted: Could not create SSL/TLS secure channel. deep inside the system after Stylesheet.TransformText() (line 57) is called
Metadata can be displayed in ArcCatalog (it is FGDC, so a upgrade notice is given, but that also happens for other datasets that work). Theme Manager has a summary/description for these themes, so Metadata.GetInfo() works. It must be a stylesheet processing issue.
It would be nice to test that all XML metadata can be rendered to HTML. This is generally true, but there may be a few bad XML files out there to track down (could limit testing to just XML files, and ignore XML in a geodatabase, since that is managed by esri software, it should work, and if it doesn't there is nothing I can do to fix it, and it will throw errors in esri software as well).
This could be done by refactoring a simple method in metadata.cs to load the content and transform it. I can check the resulting html for null, but mostly I will be looking for exceptions thrown by the stylesheet transformer. To avoid stylesheet problems, best to use the unformatted XML stylesheet.