Adding Metadata schema for WP1 for QEP-91 #4330

kalxas · 2017-04-04T18:43:41Z

Description

This PR introduces a QGIS metadata schema as part of WP1 of QEP-91.

Checklist

Commit messages are descriptive and explain the rationale for changes
Commits which fix bugs include fixes #11111 in the commit message next to the description
Commits which add new features are tagged with [FEATURE] in the commit message
Commits which change the UI or existing user workflows are tagged with [needs-docs] in the commit message and containt sufficient information in the commit message to be documented
I have read the QGIS Coding Standards and this PR complies with them
This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
New unit tests have been added for core changes
I have run the scripts/prepare-commit.sh script before each commit

nyalldawson · 2017-04-10T01:12:17Z

resources/qgis-resource-metadata.xml

+        <keyword>kw2</keyword>
+    </keywords>
+    <fees>None</fees>
+    <accessconstraints>None<accessconstraints>


accessconstraints isn't included in the .xsd

nyalldawson · 2017-04-10T01:14:12Z

Thinking out loud... could we add a travis check to run xmllint to validate the sample xml against the xsd?

nyalldawson · 2017-04-10T01:26:41Z

Can we also get documentation tags added to the xsd please?

nyalldawson · 2017-04-11T09:17:08Z

resources/qgis-resource-metadata.xsd

+            <xs:element name="keywords" type="rm:keywordsType" minOccurs="0" maxOccurs="unbounded"/>
+            <xs:element name="fees" type="xs:string" minOccurs="0"/>
+            <xs:element name="constraints" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
+            <xs:element name="rights" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>


Can we get an example rights and constraints added to the sample .xml file please?

I can't see any rights in there yet?

nyalldawson · 2017-04-12T00:49:05Z

resources/qgis-resource-metadata.xsd

+            <xs:element name="name" type="xs:string"/>
+            <xs:element name="organization" type="xs:string" minOccurs="0"/>
+            <xs:element name="position" type="xs:string" minOccurs="0"/>
+            <xs:element name="address" type="rm:addressType" minOccurs="0"/>


Should we allow multiple addresses for each contact? Eg postal address + street address?

good idea. Made address 1..n cardinality.

nyalldawson · 2017-04-12T02:33:29Z

resources/qgis-resource-metadata.xsd

+			</xs:element>
+			<xs:element name="parentidentifier" type="xs:string" minOccurs="0">
+				<xs:annotation>
+					<xs:documentation>A Refernece, URI, URL or some other mechanism that that a given resource is a part of (child).</xs:documentation>


Refernece -> reference

fixed thanks.

tomkralidis · 2017-04-12T02:33:51Z

@nyalldawson good idea! First pass docs/annotations added to XML Schema inline as discussed, for review/comment.

nyalldawson · 2017-04-12T02:45:46Z

resources/qgis-resource-metadata.xsd

+		<xs:attribute name="dimensions" type="xs:integer" default="2"/>
+		<xs:attribute name="crs" type="xs:string" use="required">
+			<xs:annotation>
+				<xs:documentation>Coordinate refernece system.</xs:documentation>


refernece -> reference

nyalldawson · 2017-04-12T02:49:48Z

resources/qgis-resource-metadata.xsd

+						* description: abstract text about link
+						* url: endpoint.  If the URL is an OWS server, specify the *base* URL only without parameters like service=xxx.....
+						* format: format specification of online resource.  Strongly suggested to use GDAL/OGR format values
+						* mimeType: MIME type represenative of the online resource response (image/png, application/json, etc.)


representative

nyalldawson · 2017-04-12T23:55:47Z

What do you think about adding an element:

<xs:element name="history" type="xs:string" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
    	<xs:documentation>Freeform description of the history or lineage of the resource.</xs:documentation>
</xs:annotation>
</xs:element>

This would allow users and processes to embed information about the history of a particular resource. I'd love to have something like this which could be used by processing to automatically append a history element to the existing metadata of a layer when an algorithm is performed. E.g. reprojecting a layer would add a "Reprojected to EPSG:4326 on 2017-04-11".

Then it'd be trivial to see exactly how a particular layer was derived - e.g.

Downloaded from xxxx on ####-##-##
Clipped by qgis:clip using overlay 'xxxx.shp'
Reprojected from EPSG:28356 to EPSG:4326 using qgis:reprojectlayer

(Potentially layer edit operations could also append to this history, e.g. "54 features added"/"3 features edited using node tool")

tomkralidis · 2017-04-13T00:59:07Z

Good idea @nyalldawson; added.

kalxas · 2017-04-14T16:15:34Z

Should I rebase to master head?

nyalldawson · 2017-04-18T00:26:29Z

In the interest of moving this forward, I propose:

we put a deadline of end of this week (21/4) for comments
put a final reminder out on the mailing lists notifying re the deadline
if no outstanding issues remain on the 21st, merge this and lock in the schema

nyalldawson · 2017-04-27T00:54:36Z

@timlinux @kalxas @tomkralidis what's the status here? Should we lock this in now?

gioman · 2017-04-27T10:25:32Z

This would allow users and processes to embed information about the history of a particular resource. I'd love to have something like this which could be used by processing to automatically append a history element to the existing metadata of a layer when an algorithm is performed. E.g. reprojecting a layer would add a "Reprojected to EPSG:4326 on 2017-04-11".

Then it'd be trivial to see exactly how a particular layer was derived - e.g.
Downloaded from xxxx on ####-##-##
Clipped by qgis:clip using overlay 'xxxx.shp'
Reprojected from EPSG:28356 to EPSG:4326 using qgis:reprojectlayer
(Potentially layer edit operations could also append to this history, e.g. "54 features added"/"3 features edited using node tool")

wow! this is really super cool. Thanks!

nyalldawson · 2017-05-03T21:29:16Z

Feedback has slowed here - I think we're safe to merge

kalxas · 2017-05-11T12:34:03Z

Thanks @nyalldawson

kalxas and others added 3 commits April 4, 2017 21:38

Added draft XML schema for QGIS metadata

5c4a332

Added sample XML document for QGIS metadata

5e2611b

update schema lineage

efa6e43

nyalldawson reviewed Apr 10, 2017

View reviewed changes

nyalldawson mentioned this pull request Apr 11, 2017

New QgsRange template based class for storing interval ranges #4353

Merged

8 tasks

nyalldawson reviewed Apr 11, 2017

View reviewed changes

tomkralidis added 2 commits April 11, 2017 16:56

Update qgis-resource-metadata.xml

759842e

Update qgis-resource-metadata.xsd

6eb0478

nyalldawson reviewed Apr 12, 2017

View reviewed changes

tomkralidis added 3 commits April 11, 2017 21:06

Update qgis-resource-metadata.xsd

399e6f0

Update qgis-resource-metadata.xml

343281b

add docs to XSD

3b833d4

nyalldawson reviewed Apr 12, 2017

View reviewed changes

tomkralidis added 2 commits April 11, 2017 22:35

Update qgis-resource-metadata.xsd

7211cc2

Update qgis-resource-metadata.xsd

a92fde7

nyalldawson reviewed Apr 12, 2017

View reviewed changes

Update qgis-resource-metadata.xsd

b8e27c1

nyalldawson mentioned this pull request Apr 12, 2017

Implement Metadata store (WP2 for QEP-91) (part 1) #4356

Merged

8 tasks

Update qgis-resource-metadata.xsd

b8a6965

Update qgis-resource-metadata.xsd

944ce5f

nyalldawson merged commit 9e662a7 into qgis:master May 3, 2017

kalxas deleted the metadata_schema branch May 21, 2017 20:53

Gustry mentioned this pull request Mar 8, 2018

Add description of Information and Metadata tabs qgis/QGIS-Documentation#2395

Merged

qgib mentioned this pull request May 24, 2019

Automatically create spatial index on shape file when adding it to project #15276

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adding Metadata schema for WP1 for QEP-91 #4330

Adding Metadata schema for WP1 for QEP-91 #4330

kalxas commented Apr 4, 2017 •

edited by timlinux

nyalldawson Apr 10, 2017

tomkralidis Apr 11, 2017

nyalldawson commented Apr 10, 2017

nyalldawson commented Apr 10, 2017

nyalldawson Apr 11, 2017

tomkralidis Apr 11, 2017

nyalldawson Apr 12, 2017

tomkralidis Apr 12, 2017

nyalldawson Apr 12, 2017

tomkralidis Apr 12, 2017

nyalldawson Apr 12, 2017

tomkralidis Apr 12, 2017

tomkralidis commented Apr 12, 2017

nyalldawson Apr 12, 2017

tomkralidis Apr 12, 2017

nyalldawson Apr 12, 2017

tomkralidis Apr 12, 2017

nyalldawson commented Apr 12, 2017 •

edited

tomkralidis commented Apr 13, 2017

kalxas commented Apr 14, 2017

nyalldawson commented Apr 18, 2017

nyalldawson commented Apr 27, 2017

gioman commented Apr 27, 2017

nyalldawson commented May 3, 2017

kalxas commented May 11, 2017

Adding Metadata schema for WP1 for QEP-91 #4330

Adding Metadata schema for WP1 for QEP-91 #4330

Conversation

kalxas commented Apr 4, 2017 • edited by timlinux

Description

Checklist

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nyalldawson commented Apr 10, 2017

nyalldawson commented Apr 10, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tomkralidis commented Apr 12, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nyalldawson commented Apr 12, 2017 • edited

tomkralidis commented Apr 13, 2017

kalxas commented Apr 14, 2017

nyalldawson commented Apr 18, 2017

nyalldawson commented Apr 27, 2017

gioman commented Apr 27, 2017

nyalldawson commented May 3, 2017

kalxas commented May 11, 2017

kalxas commented Apr 4, 2017 •

edited by timlinux

nyalldawson commented Apr 12, 2017 •

edited