Marten

have you checked the logs? I suspect an issue in the connection to SQL Server and there are a few common issues: https://github.com/Esri/geoportal-server/wiki/Database-problems

Integration with the service checker is out of the box: https://github.com/Esri/geoportal-server/wiki/FGDC-Service-Checker-Integration and there is more to it than just providing an ATOM feed (on both sides).

Torrin, not sure what is the issue. The endpoint is registered with the FGDC service checker and there is where you provide account information so that the service checker can...

ok. this will require a modification to the [ErosQueryServlet](https://github.com/Esri/geoportal-server/blob/8239d91333aa354a6a5172dc43c0de79b44116c9/geoportal/src/com/esri/gpt/server/erosfeed/ErosQueryServlet.java) class to remove the authentication requirement. In Geoportal Server 2 we did decide to make the Eros endpoint open.

we will provide a servlet that does not require authentication

thanks! assigned to dev team.

We have released Geoportal Server 1.2.9 where we have addressed many of these issues. In this release we no longer use Struts, but have switched to Tiles.

correct, we only harvest the service endpoints in the harvester. I have published this [script](https://gist.github.com/mhogeweg/95717823010fd5149b9be7312e4454ff) that loops through the image server and generates an FGDC XML document for every image....

that is a generic concern with transforming between metadata specifications. even from the verbose metadata specs like FGDC/ISO to the 'brief' open data specs leads to issues as for example...

would be good if you can create a wiki page for that process and example