9. Design considerations
• When creating a database backend, why not opening it
up for others to add / edit data?
• If others provide data, why not help them to retrieve
and access the data?
• Wikipedia as a model, but maps central & multi-lingual
• Map embeddable by other websites
• Open JSON API, Pelagios RDF, downloads
10. Core functionality
Users can add:
• Markers (since February 2012)
• Images (since May 2013)
• KML line tracings (March 2014)
.. but no real community supporting features as of yet.
18. User engagement
summarized
• 200 activated user accounts
• 68 users added markers
• 6073 markers added by users
• 90% of all markers were added by 9 users.
(June 2014)
19.
20.
21.
22.
23.
24.
25.
26.
27. Discussion
• How to attract users beyond NL, DE and BE?
• What did the 132 users that only registered expect?
• Populating the map ’enough’ appears to have been
essential in engaging users
• Will an investment in community features pay off?
• Stuck in the middle between science and
marketing?
Notes de l'éditeur
started as a father, not a scientist
work for KB, this spare time
fort vechten, water line defensive line, 19th century
learned there was also roman fort, a harbour, a road, vicus, etc. but where?
here we ‚see’ the site of the roman fort…
I wanted something like this
looked for info in the internet, to find what was where,
came across a small part of a copy of a roman map, played with it and made a small routeplanner
bumped into data by Richard Talbert, a map for the whole empire, pretty exciting, lots of media attention, but not my primary goal
returned to my original goal, be able to ‚see’ of what was where in roman times
started a simple webapp, markers, lines and overlay images, in need of a backend
origin of the users (June 2014)
adding markers
two thirds added by me by importing datasets from all over…