Search Results LINK: FGDC HTML Formatted View

Question

I worked with our web developer to add an HTML view of the metadata in our Geoportal (v9.3.1.sp1) for easier metadata review. This customized code added to the results.jsp file displayed a link in the search results called "FGDC Formatted XML." A user can click on the link and another page pops-up with a user-friendly view of the metadata (as opposed to viewing raw XML).

The problem is that when I migrated this code to the same file in Geoportal (v10), it no longer worked properly. (It broke 🙂 We tried to trouble-shoot this problem, after giving consideration to the metadata itself, we concluded the XSL we were currently using should work because the metadata in our Geoportal (v10) database is the same as what was in the previous (9.3.1.sp1) database.

Even if we had Upgraded our metadata to ArcGIS 10 Metadata --> it would still only contain the FGDC elements Exported to XML --> then Published to Geoportal (v10).

It's just strange that the links don't work in FGDC Plus, and the font doesn't wrap for items like Abstract and Purpose in FGDC Classic when applied in Geoportal (v10).

Now we are wondering if the problem is related to the server, or changes to the underlying code and configuration files in support of new functionality in Geoportal (v10)? Does anyone have any helpful thoughts or tips we could try?

Search_Results_links.jpg

Vitridodac.rar

tikola_0-1783057542010.png

KristenWobbe · Answer

I discovered the mystery about why the text in the Abstract & Purpose were not wrapping in version 10 Geoportal.

Well as it turns out, it may not be a version 10 problem at all!  A metadata writer in our group was typing the Abstract and Purpose in Notepad, and then copying and pasting that into the metadata.  We came across it and noticed it when he published a batch of metadata in 9.3.1.sp1 recently.  I recommend he changed his workflow and type in Word, or Wordpad.  He made the change and it worked.  So hopefully this is the answer, and was easily resolved.
...~Kris

KristenWobbe · Answer

Hi Marten: Here is the rest of the code to complete the story. I hope this helps in assisting you to build a sample customization for the Geoportal Server to share on http://esriurl.com/geoportalserver! Maybe I could benefit from that, because this solution has a couple of minor problems in v10. Here's the code from our Web Developer Chris Zwemke: "Here is how it works. 1. Edit the results.jsp file with a simple bit of JavaScript. (This by the way, is the only thing I have written originally) /** On link clicked, change the href to include the info from the previous link @param clickedLink is the DOM object clicked **/ function orwaFGDCLinkage(clickedLink ) { baseURL = "http://web.or.blm.gov/gis/metadata/?xmlfile="; xmlURL = clickedLink .previousSibling.href; clickedLink .href = baseURL + xmlURL; } And this code is used down the page ......... ......... <% // Custom hard coded link to xsl %> FGDC Formatted XML <% // Zoom map to this metadata extent %>

KristenWobbe · Answer

Hi Marten:
Our web developer is out today, and there is a portion of this code that works outside the Geoportal because it ties to a similar solution we use on our external website: http://www.blm.gov/or/gis/data.php
When you download a GIS dataset you can view the full metadata.

The reason I blogged about it was because this works perfectly in GPT version 9.3.1.sp1, but the links don't work in GPT version 10 for the FGDC Plus stylesheet, and the font doesn't wrap for items like Abstract and Purpose in the FGDC Classic view when applied in Geoportal (v10). See attachments!

Did you notice this? Can you think of any new code in the v10 results.jsp file that would affect this?

I know our "web guy" was looking for a XSL file that might work better with GPT v10, and was thinking he may have to re-write the solution. We'll talk when he returns. I think we would like to work with you on the code sample customization for the Geoportal Server for the web page you described (http://esriurl.com/geoportalserver). What is the protocol? How do we go about it?
 
Thanks for your reply. 
...~Kris

FGDCplus_noLinks.jpg

FGDCclassic_noWrap.jpg

Error.jpg

arcdata-js-api-widgets.zip