View Source

Develop a job that deletes old log files.
Delete old (older than 365 days) measurements.
Verify security of Sesame Server. Do I need to set up User/Password? |Priority=5| http://rivuli-development.com/further-reading/sesame-cookbook/basic-security-with-http-authentication/
Read this http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.161.8030&rep=rep1&type=pdf |Priority=2|
Check the update feature of Sesame. Some towns/nodes should have their info updated accordingly.
See together with ETSI if we can use the ontology as we want, giving them the right credits..
Review the Users for Geonames and the Google Maps API
Develop a backup system for the entire RDF repository.
Next version may include Groups (Regions).
Document updating war file.
Provide more information under images in http://pingerlod.slac.stanford.edu/ visualizations

About Schools |Priority=3|

Search about Lucene+Sparql to increase and enhance the results for querying over School Names. |Priority=3|
Search data sets about schools other than DBPedia.
There are some endowment and number of students from DBPedia that are not execatly numbers. For example, "app. 95,000". Right now I am discarding this kind of data. Maybe I should retrieve the number information from these data .

Create a package under the package 'general' to write the ontology. Create constant classes for each prefix. Then, when programming, instead of writing strings for each statement, you would refer to the constants created. For example, create a class called GNONT with a constant called NAME. Then, when programming you would use GNONT.NAME. |Priority=2|
The method pinger.rest.HttpGetter.getJsonGeonames can be optimized. There is a test that verifies if the geonames username has been overused hence blocked. If it is, try another username. There could be a priority scheduling policy; a Map with priorities could be used to implement. The username that was able to be used would receive higher priority than blocked usernames. |Priority=1|