Following up on your suggestion, here is how I approached this. I am quite happy with the result, but of course I welcome suggestions if you feel I may be going off track. I’m sharing this in some details also to facilitate replication if this may be of any use to others.
First, since no DC core property seemed fitting (and also keeping in mind that anyway mapping data is not by default recorded in a DC property), I generated a custom property through the Custom Ontology module.
I then created a custom vocabulary with the Custom Vocab module, with four options:
- precise location
- approximate location
- uncertain location
- generic/village level location
I then added the property to the relevant resource templates.
This looked all good, but not quite ideal, in particular for those exploring contents through the “map-browse” function, as they would not have an easy way to remove generically geolocated items.
To facilitate showing on the map only items that are precisely geolocated, I added a link just below the map in the “map-browse” page, by editing the Mapping module directly. More specifically, I edited the file modules/Mapping/view/mapping/site/index/browse.phtml
, and added after the div with the map (<div id="mapping-map"
), something along these lines:
<div><p style="text-align:center;"><a href="map-browse?fulltext_search=&property[0][joiner]=and&property[0][property]=304&property[0][type]=eq&property[0][text]=Precise+location">Click here to see only items which have been precisely geolocated.</a></p></div>
(notice that the property number - 304 - depends on your installation).
If users click on that link, they just see the same interface with the relevant property pre-selected, making it much more intuitive to use.
Of course, I’ll need to remember to add this again each time the Mapping module is updated.
I still feel this may be something that is included in the mapping module itself, but I’ll try to have this set up working for a while and perhaps file an issue once I am more confident that this solution is indeed useful.