[Live-demo] pycsw in OSGeo Live.

[Angelos Tzotsos]

+1 on a OSGeoLive metadata set for both Geonetwork and pycsw.


On 01/30/2012 12:47 AM, Alex Mandel wrote:
> On 01/29/2012 02:41 PM, Tom Kralidis wrote:
>>
>>
>>> Date: Sun, 29 Jan 2012 14:39:45 -0800
>>> From: tech_dev at wildintellect.com
>>> To: live-demo at lists.osgeo.org
>>> Subject: Re: [Live-demo] pycsw in OSGeo Live.
>>>
>>> On 01/29/2012 02:34 PM, Tom Kralidis wrote:
>>>>
>>>>
>>>>> Date: Sun, 29 Jan 2012 12:11:33 -0800
>>>>> From: hamish_b at yahoo.com
>>>>> Subject: Re: [Live-demo] pycsw in OSGeo Live.
>>>>> To: gcpp.kalxas at gmail.com; cameron.shorter at gmail.com
>>>>> CC: live-demo at lists.osgeo.org
>>>>>
>>>>> Last April Cameron wrote:
>>>>>> My initial feeling is that it would be great to
>>>>>> include pywcs in a future release of OSGeo-Live,
>>>>> (for the record we did ship it with the 5.0 release,
>>>>> just didn't list it on the contents page.)
>>>>>
>>>>>> but as pywcs is still only at a 0.1 release,
>>>>> version numbers are meaningless. ignore and forget
>>>>> them and judge the app on the app instead.
>>>>>
>>>> FYI pycsw is at 1.0.0 (which is what looks like is included with 5.0), with 1.2.0 scheduled for April 2012.  What's the timeline for the next livedvd release?
>>>>
>>>>>> without wide uptake yet,
>>>>> for FOSS that metric is rather impossible to know,
>>>>> but anyway if it is good, hence a great reason to
>>>>> include it on the disc- to get it wide exposure!
>>>>> chickens and eggs...
>>>>>
>>>> Agreed, we do know pycsw is being tested/prototyped in various environments, and that exposure on the livedvd would be beneficial for those looking for a Python CSW (many CSWs are Java-based).
>>>>
>>>>>> it is premature to include pywcs into the next
>>>>>> OSGeo-Live release.
>>>>> If it's buggy or incomplete that's one thing. If
>>>>> it is just unknown that's a very different matter,
>>>>> and something we can help with.
>>>>>
>>>>>
>>>> pycsw makes a point of passing OGC CITE and it's own testing framework as enhancements/fixes are commited.  We feel is complete enough for a user to stand up an operational CSW catalogue (with transactions if desired as well).
>>>>
>>>>> I suggest to review and improve the overview and
>>>>> quickstart reST pages, then make the final call on
>>>>> whether to keep it listed on the contents page once
>>>>> we get feedback from our beta testers. (a great
>>>>> incentive to make the overview page clear about
>>>>> what the user should expect, and to make the
>>>>> quickstart clear about how to go about doing it)
>>>>>
>>>>>
>>>> We would be glad to update these pages as appropriate.  Thanks!
>>>>
>>>> ..Tom
>>>>
>>> I would love to see an example CSW on the disc using the included
>>> datasets. The quickstart could include browsing using the CSW plugin in
>>> QGIS. I realize that might take some more work, but would be interested
>>> if not for this version trying to achieve that on version 6 in the Fall.
>>>
>>> Thanks,
>>> Alex
>>>
>> Are there any sample metadata on livedvd?  By default, pycsw always ships with the OGC CITE test metadata.
>>
>> ..Tom
>>
>>   		 	   		
> I haven't really checked, but will put that on the ToDo list since we
> are using NaturalEarth data and the GRASS North Carolina dataset. Would
> be interesting to generate on the fly OSM metadata as we install that on
> the disk too (only the bounding box changes occasionally).
>
> Hmm, maybe we need to recruit some metadata editors. I imagine we could
> work towards pycsw and geonetwork sharing a metadata set.
>
> Thanks,
> Alex
>
> _______________________________________________
> Live-demo mailing list
> Live-demo at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/live-demo
> http://live.osgeo.org
> http://wiki.osgeo.org/wiki/Live_GIS_Disc
>


-- 
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
http://users.ntua.gr/tzotsos