[SAC] [OSGeo] #1055: OSGeo Service Provider Directory Broken

Basques, Bob (CI-StPaul) bob.basques at ci.stpaul.mn.us
Wed Jan 9 10:50:13 PST 2013


Frank,

That's all I need to get something for review purposes together.

CSV would be fine.

Thanks

Bobb



>>  -----Original Message-----
>>  From: fwarmerdam at gmail.com [mailto:fwarmerdam at gmail.com] On
>>  Behalf Of Frank Warmerdam
>>  Sent: Wednesday, January 09, 2013 11:29 AM
>>  To: Basques, Bob (CI-StPaul)
>>  Cc: System Administration Committee Discussion/OSGeo
>>  Subject: Re: [SAC] [OSGeo] #1055: OSGeo Service Provider
>>  Directory Broken
>>  
>>  Bobb,
>>  
>>  Your ideas sound great.  If you have the energy, you have my
>>  support and I'm prepared to provide some support.
>>  
>>  I can look into dumping the existing database tables to .csv
>>  files or something similar if that would be a useful first step.
>>  
>>  Best regards,
>>  Frank
>>  
>>  On Wed, Jan 9, 2013 at 7:44 AM, Basques, Bob (CI-StPaul)
>>  <bob.basques at ci.stpaul.mn.us> wrote:
>>  >
>>  > Frank,
>>  >
>>  > We do the same for GeoMoose with regard to the linking.  I also
>>  immediately want to take this further, and discovered the
>>  limitation with the current system with regard to making
>>  architecture changes.
>>  >
>>  > My interest is in making it more accessible to new project
>>  service providers by replicating these types of links out into
>>  the projects themselves, complete with access to the forms for
>>  new registrations, I would also like to add in some optional
>>  extended attributes for the providers. Possibly even add in some
>>  methof for valididation of Emails by sending out periodic
>>  reminders, etc.
>>  >
>>  > The separation aspect really relates to me having the
>>  maintenance duties separated from everything else.  As far as the
>>  Styling, that should be dependent on the particular client, the
>>  linking to the new service from OSGEO would use the existing
>>  style, for example, while also allow projects the option of using
>>  their respective styles.
>>  >
>>  > Another thought that occurred to me after sending the initial
>>  email was the idea that being separated, the service provider
>>  directory could become a project of sorts unto itself, similarly
>>  to the LiveDVD.  It could be inserted into the LiveDVD for
>>  example at each stamping, dependent on some FORM checkbox.
>>  There's not really a method in the current OSGeo domain for
>>  anyone to provide feedback or introduce ideas about how things
>>  might be improved, other than this list (that I know of).
>>  >
>>  > Some of these thoughts are longer term, but you get the idea
>>  about why I think the separation aspect might be the thing to
>>  implement first.
>>  >
>>  > Bobb
>>  >
>>  >
>>  >
>>  > bobb
>>  >
>>  >>>  -----Original Message-----
>>  >>>  From: fwarmerdam at gmail.com [mailto:fwarmerdam at gmail.com] On
>>  Behalf
>>  >>> Of Frank Warmerdam
>>  >>>  Sent: Tuesday, January 08, 2013 6:14 PM
>>  >>>  To: Basques, Bob (CI-StPaul)
>>  >>>  Cc: System Administration Committee Discussion/OSGeo
>>  >>>  Subject: Re: [SAC] [OSGeo] #1055: OSGeo Service Provider
>>  Directory
>>  >>> Broken
>>  >>>
>>  >>>  On Tue, Jan 8, 2013 at 3:01 PM, Basques, Bob (CI-StPaul)
>>  >>> <bob.basques at ci.stpaul.mn.us> wrote:
>>  >>>  > Hi all,
>>  >>>  >
>>  >>>  > I'm just now reading this, (or figuring out what was being
>>  >>> talked about).
>>  >>>  >
>>  >>>  > I would like to volunteer to build this out into something
>>  >>> separate from the Drupal infrastructure, as I think it's
>>  better  off
>>  >>> that way over the long run.
>>  >>>  >
>>  >>>  > I would like to set up a Postgres database instead and set
>>  up a
>>  >>> simpler calling structure for displaying the Service Provider
>>  >>> information.
>>  >>>  >
>>  >>>  > I've been wondering for a while now how to set this up as
>>  a
>>  >>> service that could feed other sites.  The intent being to
>>  propagate
>>  >>> the information where it is needed.  It would be nice  for
>>  instance
>>  >>> for each project to be able to include a few links  related
>>  to their
>>  >>> project about service providers that are  available for their
>>  >>> product(s).
>>  >>>  >
>>  >>>  > All I need to get started would be a dump of the existing
>>  data
>>  >>> and I'll set something up for review.
>>  >>>
>>  >>>  Bobb,
>>  >>>
>>  >>>  Note that currently projects can already reference the
>>  Service
>>  >>> Provider Directory.  For instance GDAL links to the following
>>  which
>>  >>> gives GDAL related service providers:
>>  >>>
>>  >>>  http://www.osgeo.org/search_profile?SET=1&MUL_TECH[0]=00013
>>  >>>
>>  >>>  On the one hand, separating this from Drupal would make
>>  upgrading
>>  >>> Drupal easier.  On the other hand, at the time it was built
>>  it  was
>>  >>> perceived as helpful to build it into Drupal so it appears to
>>  be a
>>  >>> natural similarly styled part of the web site, and tied into
>>  the
>>  >>> existing LDAP infrastructure.  I'm a bit dubious on the value
>>  of
>>  >>> setting it up as a separate service.
>>  >>>
>>  >>>  Best regards,
>>  >>>  --
>>  >>>  ---------------------------------------+--------------------
>>  -----
>>  >>>  -------
>>  >>>  ---------------------------------------+------
>>  >>>  I set the clouds in motion - turn up   | Frank Warmerdam,
>>  >>>  warmerdam at pobox.com
>>  >>>  light and sound - activate the windows |
>>  >>> http://pobox.com/~warmerdam
>>  >>>  and watch the world go round - Rush    | Geospatial Software
>>  >>>  Developer
>>  >
>>  >
>>  
>>  
>>  
>>  --
>>  ---------------------------------------+-------------------------
>>  -------
>>  ---------------------------------------+------
>>  I set the clouds in motion - turn up   | Frank Warmerdam,
>>  warmerdam at pobox.com
>>  light and sound - activate the windows |
>>  http://pobox.com/~warmerdam
>>  and watch the world go round - Rush    | Geospatial Software
>>  Developer




More information about the Sac mailing list