An example of this is that the data catalogue contains about 200 studies for Wales the country, but the geocoding process put the location as Wales in a village near Sheffield; the method I used to extract the data from the public Open Archives Initiative Application Program Interface (OAI API) lost the some of the contextual information as it pulled lebanon rcs data the data out into a set of data tables. When viewing the record on our website, the information tells you that the data coverage is Europe and that it contains countries England, Wales and Germany, but to the automatic geocoding process it was presented with addresses that state Europe or England or Wales or Germany, without the contextual information to geocode to a country rather than to a place.
Another area I wanted to explore was a way to highlight the access conditions of each study. Our access conditions cover the open data we hold to data, which are controlled access because they contain personal data or are covered by specific licence conditions. This map shows all the studies, but each study is colour coded by the access level of the data. I thought this map worked quite well, you are able to click on a data collection and the caption that appears contains a link to the record in Discover. We discovered a limitation, however, where if multiple studies geocoded to the same point the user can only click on the first data collection presented. A work-around for this could be to offset each data collection a little, creating cluster points at that location. An alternative would be to display a table below the map which could display all the data collections for that location.
All the maps I’ve produced are purely proof of concept, but we are planning on incorporating some of these ideas to enhance the user experience of our website with our Innovation Fund partners Audiencenet, who are consulting widely with people across a range of sectors on the user experience of our website.