<div dir="ltr">Dear Colleagues,<div>thanks, if I may weigh in here re. metadata:</div><div><br></div><div>Metadata remain key to whatever you do in computing and in the public eye.</div><div>Lack of standardized, and good and accepted, visionary metadata, are the wide failure</div><div>of most (software) projects, and if they want to remain and be of wider, global relevance.</div><div>While additional internal notes might be good, or useful, metadata must all be public, as a scheme.</div><div><br></div><div>Now, people have thought about it for decades already,</div><div>and there are FGDC geospatial metadata to work from and to use.</div><div>Those are the high detail ISO standards, and beyond.</div><div>Without following those logics, and also the libraries, governments, science funders etc </div><div>and their online repositories to link to, the metadata will go nowhere.</div><div><br></div><div>Metadata cannot, and must not, be done as a home brew and as a quick fix.</div><div>We see wide failures there in R and its analysis tools, or in GRASS GIS etc.</div><div>(=hand drawn manuals or internal reviews are not cutting it).</div><div><br></div><div>I refer people to the Metadata Wizard by USGS as one of several 'rocks'</div><div>and main pillars to consider here. Using Metadata Light instead are not cutting it.</div><div><br></div><div>Arguably, innovation in metadata is good, but I assume technically it is</div><div>XML as the platform with the stylesheets etc in ISO.</div><div><br></div><div>Just my few 2 cents on the issue.</div><div>Very best</div><div> Falk</div><div><br></div><div>PS There is an earlier plugin in QGIS that does FGDC metadata but it does not work. Any pointers</div><div>on how to fix it ? That would be VAST progress and benefit QGIS indeed.</div><div> </div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 31, 2019 at 9:52 PM Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com">nyall.dawson@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 1 Nov 2019 at 02:42, Alessandro Pasotti <<a href="mailto:apasotti@gmail.com" target="_blank">apasotti@gmail.com</a>> wrote:<br>
<br>
> IMO what is missing here is a bridge between the new metadata API in QGIS core and the "old" QGIS server metadata API.<br>
<br>
It was always a deliberate choice to keep these two separate. The<br>
thinking was that the metadata you use for your local projects and<br>
layers isn't necessarily going to match what you want to publish and<br>
advertise to external users. You might have sensitive information in<br>
there, or just "internal only" details which you don't want/need to<br>
publish.<br>
<br>
I think all that's missing here is a button to auto-populate server<br>
metadata by copying it from the project or layer metadata. It'd give a<br>
quick way to initial populate the published metadata, which you could<br>
then tweak as needed...<br>
<br>
Nyall<br>
<br>
<br>
><br>
><br>
>><br>
>> On Thu, Oct 31, 2019 at 11:47 AM Paolo Cavallini <<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>> wrote:<br>
>> ><br>
>> > Thanks Ale for the explanation. Indeed, a suboptimal situation.<br>
>> > Perhaps worth an ad hoc crowdfunding.<br>
>> > Cheers.<br>
>> ><br>
>> > Il 31/10/19 16:40, Alessandro Pasotti ha scritto:<br>
>> > ><br>
>> > > On Thu, Oct 31, 2019 at 4:28 PM Paolo Cavallini <<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a><br>
>> > > <mailto:<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>>> wrote:<br>
>> > ><br>
>> > > Hi all,<br>
>> > > apparently our server does not expose the metadata stored in the project<br>
>> > > and layer properties:<br>
>> > > * is this true?<br>
>> > ><br>
>> > ><br>
>> > > There is a metadata section in the server configuration (Service<br>
>> > > Capabilities) of the project properties, modeled on WMS/WFS metadata,<br>
>> > > they are exposed. The sad thing is that when the new metadata framework<br>
>> > > was developed it was not connected with the existing server metadata, so<br>
>> > > we currently have two separate APIs for metadata, the old very limited<br>
>> > > one for the server and the new one. On the other hand, the old existing<br>
>> > > API is exactly what was required by WMS/WFS.<br>
>> > ><br>
>> > ><br>
>> > > * is there any reason for this, besides the usual lack of resources to<br>
>> > > implement it?<br>
>> > ><br>
>> > ><br>
>> > > Not that I'm aware of.<br>
>> > ><br>
>> > ><br>
>> > > * anyone has estimates or plans to implement it?<br>
>> > ><br>
>> > ><br>
>> > > Not that I'm aware of.<br>
>> > ><br>
>> > > I though about it for WFS3 but I couldn't find the time/resources to do<br>
>> > > anything (mainly because of missing API in the server), for now I've<br>
>> > > just implemented what was available in the server's WFS code.<br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > > Moreover, I wonder how users are managing their metadata from QGIS, now<br>
>> > > that several plugins that helped compiling them are not available for<br>
>> > > current versions. Any feedback will be appreciated.<br>
>> > > Cheers.<br>
>> > > --<br>
>> > > Paolo Cavallini - <a href="http://www.faunalia.eu" rel="noreferrer" target="_blank">www.faunalia.eu</a> <<a href="http://www.faunalia.eu" rel="noreferrer" target="_blank">http://www.faunalia.eu</a>><br>
>> > > <a href="http://QGIS.ORG" rel="noreferrer" target="_blank">QGIS.ORG</a> <<a href="http://QGIS.ORG" rel="noreferrer" target="_blank">http://QGIS.ORG</a>> Chair:<br>
>> > > <a href="http://planet.qgis.org/planet/user/28/tag/qgis%20board/" rel="noreferrer" target="_blank">http://planet.qgis.org/planet/user/28/tag/qgis%20board/</a><br>
>> > > _______________________________________________<br>
>> > > QGIS-Developer mailing list<br>
>> > > <a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a> <mailto:<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a>><br>
>> > > List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> > > Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > > --<br>
>> > > Alessandro Pasotti<br>
>> > > w3: <a href="http://www.itopen.it" rel="noreferrer" target="_blank">www.itopen.it</a> <<a href="http://www.itopen.it" rel="noreferrer" target="_blank">http://www.itopen.it</a>><br>
>> > ><br>
>> > > _______________________________________________<br>
>> > > QGIS-Developer mailing list<br>
>> > > <a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
>> > > List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> > > Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> > ><br>
>> ><br>
>> > --<br>
>> > Paolo Cavallini - <a href="http://www.faunalia.eu" rel="noreferrer" target="_blank">www.faunalia.eu</a><br>
>> > <a href="http://QGIS.ORG" rel="noreferrer" target="_blank">QGIS.ORG</a> Chair:<br>
>> > <a href="http://planet.qgis.org/planet/user/28/tag/qgis%20board/" rel="noreferrer" target="_blank">http://planet.qgis.org/planet/user/28/tag/qgis%20board/</a><br>
>> > _______________________________________________<br>
>> > QGIS-Developer mailing list<br>
>> > <a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
>> > List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> > Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> _______________________________________________<br>
>> QGIS-Developer mailing list<br>
>> <a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
>> List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
><br>
><br>
> --<br>
> Alessandro Pasotti<br>
> w3: <a href="http://www.itopen.it" rel="noreferrer" target="_blank">www.itopen.it</a><br>
> _______________________________________________<br>
> QGIS-Developer mailing list<br>
> <a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
> List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
> Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote></div>