Give me all the monuments within 10km of my home which
don't
have a photo yet.
I was precisely working on that :). Let's better not duplicate work; and
divide work. I can program in Python. But my program only works for Catalan
monuments, since I have my own way of accessing them. It's not easy to
export. IMHO, we should create a database (for example, in a XML way) common
to all countries with WLM. Everyone could therefore develop their own tools
and could be used anywhere. Shall we work on that? Maybe KML files would
work... I don't know.
Joan Creus.
2011/3/12 Maarten Dammers <maarten(a)mdammers.nl>
Hi Nuno,
Op 12-3-2011 21:40, Nuno Tavares schreef:
Maarten,
That was my point: establishing a common interface, instead of each
going its own way. I was building a tool like that, at
http://wlm.wikimedia.pt/tools/plist
http://wlm.wikimedia.pt/monumentos.php
(I think it's pretty straightforward playing around with the simple
filter box (caixa de filtros), but would help if you know portuguese,
though).
Looks good!
Based on our ETL, I've already detected some
errors on the structured
lists introduced by the bot conversion, which I hope I can fixed them in
time, so everyone can get clean (and complete) lists.
Btw, these lists are pretty old, and we're now updating it with official
lists in a versioned warehousing fashion. I was playing last nights
around (partial) dynamic statistics:
http://wlm.wikimedia.pt/tools/plist/stats.php
(You can easily see that there are more than 14 objects with images).
I'm also trying to add more internal information:
* I want to show progress graphs, I'm sure they'll motivate our
partners;
At the Dutch Wikipedia we maintain quite extensive progress statistics.
Next step would be to put these stats in a graph.
* How many of these have already articles -
done;
* How many of these (that have article) have already images - half-done,
I want to cross information from Commons, which we'll give far more
realistic results.
* We have different status/degrees of classification, I think that
should be kept.
The monuments_pt_(pt) table contains all the fields. Some drop off
in
the monuments_all table. I think I will just add more fields to the
monuments_all table to handle extended descriptions and classifications.
* We have multiple sources, so we have multiple
source ids, which should
be kept for update in the future.
* I want our system to allow easily corrections: mainly coordinates.
I'm not sure if both databases need to co-exist (yours being an exported
version of our own), as I'd like to have more detail than the
monuments_pt_(pt) table.
The monuments database resides on the shared account
"erfgoed" (heritage
in Dutch) at the Toolserver. We can easily give more people access so we
can use it as a shared development place.
Thanks for the tools information. Unfortuneately,
I don't do python.
That's no problem at all. The input side is python. You
probably want to
work on the output side. Php is more suitable for that anyway :-)
Maarten
Regards,
_______________________________________________
Wiki Loves Monuments mailing list
WikiLovesMonuments(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments
http://www.wikilovesmonuments.eu
_______________________________________________
Wiki Loves Monuments mailing list
WikiLovesMonuments(a)lists.wikimedia.org