Recent changes to feature-requests

Publishing Client Compatible with ArcGIS 10.1

Rob Ward — Mon, 17 Sep 2012 09:11:58 -0000

Currently Publishing Client 1.2 is not compatible with ArcGIS 10.1

Publishing Client Compatible with ArcGIS 10.1

Rob Ward — Mon, 17 Sep 2012 09:11:58 -0000

Ticket 39 has been modified: Publishing Client Compatible with ArcGIS 10.1
Edited By: Marten Hogeweg (mhogeweg)
Status updated: 'open' => 'closed'

Add REST API as federated search option

David Neufeld — Thu, 24 May 2012 15:31:00 -0000

Consider adding the Geoportal REST API as a federated search option. This would allow more detailed and consistent search results across federated searches that share common property meaning and indexing strategies.

Use Case:
NGDC has a wms.resource.url that we can search on that will return all WMS services that are documented using ISO service elements. This returns more results that a simple text search for WMS. However federating a wms.resource.url search to other NOAA data centers will fail using CSW because the resource is not part of the core queryables. It's possible that I'm missing something on the CSW limitation here, but if not then adding the REST API as a federated search option would be valuable.

Thanks for considering.
-Dave

Add REST API as federated search option

David Neufeld — Thu, 24 May 2012 15:31:00 -0000

Ticket 37 has been modified: Add REST API as federated search option
Edited By: Marten Hogeweg (mhogeweg)
Status updated: 'open' => 'closed'

Add Flikr Federated search

Jacqueline Mize — Wed, 21 Mar 2012 13:10:00 -0000

I would like to see a Flikr search similar to the youtube seach ability.

Add Flikr Federated search

Jacqueline Mize — Wed, 21 Mar 2012 13:10:00 -0000

Ticket 36 has been modified: Add Flikr Federated search
Edited By: Marten Hogeweg (mhogeweg)
Status updated: 'open' => 'closed'

Details for federated metadata

Gianni Campanile — Tue, 20 Mar 2012 09:15:14 -0000

The details link is available only for "internal" records and not for federated catalogues. These records should be validated to match a defined style, but it's extremely useful to show the details page even if some mandatory values are not available. Thus, the details link should appear in any case.

Details for federated metadata

Gianni Campanile — Tue, 20 Mar 2012 09:15:14 -0000

Ticket 35 has been modified: Details for federated metadata
Edited By: Marten Hogeweg (mhogeweg)
Status updated: 'open' => 'closed'

Validate "against" a profile

Gianni Campanile — Tue, 20 Mar 2012 09:11:15 -0000

The interrogation mechanism of the Geoportal implies that when verifying a metadata record, the profile is determined by some values in the metdata record. Unfortunately there is no way to determine exactly the profile, so if the record, for example an ISO profile record, is recognized as an INSPIRE one, many validation errors are shown, because INSPIRE is much more restrictive than ISO. This is the reason why ISO and INSPIRE schemas should not be both activated in the schemas.xml, but inmany cases both schemas are needed. A solution could be to choose the schema agints which an external XML file could be validated. The default could be in any case the interrogation mode, identifying the record from the tag values.

Validate "against" a profile

Gianni Campanile — Tue, 20 Mar 2012 09:11:15 -0000

Ticket 34 has been modified: Validate "against" a profile
Edited By: Marten Hogeweg (mhogeweg)
Status updated: 'open' => 'closed'