Thanks to the 12 people from 8 universities that joined our inaugural OGP Tech Talk.
Berkeley’s project is to add OGP support for layers with a bounding box but that are not georeferenced was well received. To support the effort, Tufts will add a new field to the Solr schema. This will be in the OGP point release created at the end of January. Support for non-georeferenced could also help us deal with collection level data. The roll-out of this change to the Tufts production server will be coordinated other OGP sites relying on the Tufts Solr instance.
Tufts will initiate a discussion about moving from setting map server locations in a config file to using the existing “location” field in the Solr schema.
Getting OGP authentication to work with central authentication servers is a challenge. We need to document thoroughly Harvard’s solution and understand the issues with Berkeley’s system. This issue is critical because authentication is required for access to licensed/restricted data. Dave Siegel at Harvard has started to document his solution at http://code.google.com/p/opengeoportal/wiki/PINAuthentication . Berkeley will be sending code that demonstrates their authentication issue for troubleshooting.
There is very broad interest in shared cloud based OGP resources. To quote MIT, “instead of figuring out how and when to harvest metadata from many sites/systems, we’d like to explore all sites contributing metadata to one shared site that can be easily searched by all
instanced of OpenGeoPortal”. Tufts will take the lead by generating a beta proposal and starting a discussion within the community. The current OGP functionality of each institution controlling whose data they see will be preserved. It will likely require metadata standards. We envision administration access similar to the OGP source repository; staff from multiple institutions will have commit privileges. Such a system will eventually require we handle cross-institution de-duplication.
We will likely hold another OGP Tech Talk meeting at the end of January. It may use a telephone based conference call to provide high quality audio and Adobe Connect for chat and screen sharing. Please let Steve know if that would be a problem for you.
Additionally, feel free to use the mailing list for questions, meeting agenda items and announcements.