These are chat archives for fgpv-vpgf/rcs

8th
Feb 2016
Aly Merchant
@alyec
Feb 08 2016 14:18

Here's my suggestion for the RCSv2 registration format. Core request:

{
  endpoint: 'service endpoint (even a data URL will likely work)',
  name: 'service name (overrides anything we can scrape',
  metadata: { catalogue_url: 'link to the catalogue', metadata_url: 'direct link to an XML file with HNAP data' }
}
required: ['endpoint']

We can compose this with:

{
  service_type: 'esriFeature, esriDynamic, ogcWms, ...'
  options: { }
}

options would be type specific, ex:

{
  service_type: 'esriFeature'
  options: {
    loading_mode: 'snapshot',
    max_allowable_offset: 5,
    display_field: 'fancy_title'
  }
}
This allows catalogue to largely reuse the existing system (with some renaming) while allowing us to add support for more feature types without drastically changing the schema.
Dan Bowerman
@dan-bowerman
Feb 08 2016 14:22
Looks really good to me. Much less impact on GeoCat who have questionable development cycles right now.
jsmoreau
@jsmoreau
Feb 08 2016 15:41
I agree. Do we need to convert existing entries?
Aly Merchant
@alyec
Feb 08 2016 16:14
I think we should. We can either go with a migration script, or build something into RCSv2 which updates old entries when it retrieves them.
jsmoreau
@jsmoreau
Feb 08 2016 16:17
I think old entries should be updated upon retrieval. That way we won't have to remember to run a migration script before deployment.