openaire / guidelines-literature-repositories

OpenAIRE Guidelines for Literature Repository Managers based on Dublin Core and DataCite Metadata Kernel
https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/
11 stars 13 forks source link

21. Geolocation Tag - Appl.Profile Overviewer, Literature Repo.: example and question #10

Open ACz-UniBi opened 5 years ago

ACz-UniBi commented 5 years ago

another Example, with separated geoLocation's

<geoLocations> <geoLocation> <geoLocationPoint>29.952944 -28.592028</geoLocationPoint> <geoLocationPlace>Meteor Seamount</geoLocationPlace> </geoLocation> <geoLocation> <geoLocationBox>41.090 -71.032 42.893 -68.211</geoLocationBox> <geoLocationPlace>Atlantic Ocean</geoLocationPlace> </geoLocation> </geoLocations>

and question:

Is the use of geoLocationBox and geoLocationPoint and/or geoLocationPolygon in the same geoLocation tag possible and wishing?

joschirr commented 5 years ago

I don't know if it makes sense but obviously this is supported: http://schema.datacite.org/meta/kernel-4.1/metadata.xsd

ACz-UniBi commented 5 years ago

Yes, the schema of datacite mixed this too. It makes sense if a

geoLocationPolygon/Box is mixed with geoLocationPoint and one geoLocationPlace which describe the whole area in a geoLocation tag. But it doesn't make sense if more the one geoLocationPlace are written in a geoLocation tag because the relation between placeName and geoPlace is lost.

This example separates this and makes it clearer, I think.