Service Provider Directory

A frequent request of organizations wanting to use open source geospatial software, is for suggestions on individual consultants, or companies providing services for the various software packages. In the past some projects have made an effort to list those offering services around the project, but a more holistic approach to this by OSGeo would be of substantial value to the projects, the service providers, and most importantly to the organizations looking to implement solutions.

However, maintaining a list service providers is fraught with peril for OSGeo. It is important that we do so in a manner that is fair to the service providers (impartial), but avoids OSGeo judging or recommending service provider capabilities.

Provider Details

It is proposed that WebCom maintain a service provider registry on the web site with the following attributes for each service provider:

• Organization (or individual) name.
• URL to service providers off-site web page with service details, etc.
• A list of packages/technologies the service provider provides services for (from a predefined pick list).
• A list of (human) languages the organization can provide service in.
• A list of office locations (perhaps city/country with lat/long coordinates) for the service provider.
• An employee count for the organization.
• An email contact for the organization (not normally displayed - used for administrative purposes)
• The date of last information update (not normally displayed - used for administrative purposes)

Vetting

It is important to realize that OSGeo does not have the resources to review and "vette" the entries in any great detail. We are essentially providing a mechanism for service providers to list themselves, but we make no specific effort to determine if the information they provide is correct. We will have to publish appropriate disclaimers to this effect.

It is possible we will need a mechanism to deal with complaints about the accuracy/appropriateness of a directory entry. Not anticipating many complaints, I would suggest that WebCom be responsible for preliminary negotiation of complaints. If the complaintant or service provider is not satisfied then the issue be bumped up to the board. If this turns out to be a frequent problem we can develop a more streamlined procedure.

Web Display

The web page for the service provider directory should ultimately provide means to query based on each of the attributes (packages, languages, location, and employee count), though to start we might just offer the whole list. The directory should be randomly ordered, so that no service provider gets top billing by virtual of when they registered.

Updates

Entries should be updated annually. On or near a year from the last update, the contact address should be emailed, and the service provider encouraged to update their page - even if only to save it "as is" updating the last update date. Any entry not updated for 24 months should be dropped, and the contact notified by email.

This all assumes the entries can be maintained by a logged in user to the Drupal site, and that an entry, once created, would be "owned" by a drupal user.

Prototyping

Tyler has already prototyped this capability on the Drupal site...

however, I'm not sure where the entry point is to it off hand.