= SENSE feeds update process =
SENSE feeds are RDF feeds defined by the RDFS at http://www.eea.europa.eu/soer/1.0 This package uses eea.rdfmarshaller with specific adapters to create the export. To import the feeds you create a SOERCountry folder with a feed url. When you have feed url and you are Manager you will have new action in the object action menu: 'update from feed'. You can also add additional feeds to a SOERCountry by adding Link objects to it. The update process will look for them and use all of the feeds.
When the update process is initiated the current country folder is saved as a zexp export. Then all reports and their content is removed before the new content is created. If there is a unhandled error the normal Zope rollback will kick in and you'll see the traceback, i.e there is a syntax error in the RDF feed. This way no content will be lost. If you initiated the feed update manually from the action menu you need to remember that the zexp will not be rolled back. If you use the update script https://svn.eionet.europa.eu/projects/Zope/browser/trunk/eea-buildout/bin/sense it will save any previous zexp.
When you do a manual update from the action menu the zexp file is not stored in the "sensebackup folder" rather under the standard var/instance/The update script
In the update script https://svn.eionet.europa.eu/projects/Zope/browser/trunk/eea-buildout/bin/sense you enter in the loop which countries should be updated everytime the script is run from i.e cron. Usually all countries should be in the list but if you know some country has problems or will not update their feed then you can remove it and it later. This way the BRupdate will not remove and recreate the same content over and over again.
The script logs in with a manager user (!u:sense, the password is not committed to svn) and uses a zmi script to initiate the update feed process. The zmi script will return a short message if no errors happens or the traceback if an error occurs. The email generated from the shell script will contain this short message at the top and then it will contain a log from the wget script and the part from the instance log during the update. The traceback information is available at the end of this log.Known problems * Some times the update doesn't publish the content. You can suspect this if you run the update script https://svn.eionet.europa.eu/projects/Zope/browser/trunk/eea-buildout/bin/sense and you get an email saying that the update went fine but you didn't see any CMS emails from publishing content. * Content from feeds not perfectly formatted Some feeds contain content with markup,style and classes that interfere with EEA styles. The current Tidy up process doesn't catch all these since the more powerful filtering at EEA's website is done in the kupu editor on the browser side which is quite cumber sum to implement. * Multiple geo coverage values for same thingBRSome countries have multiple values for the same geo coverage and this is not harmonized in the import. Content overview
To give an overview of the current content of country assessments there is an admin view http://www.eea.europa.eu/soer/soer_admin_view . It will show all SOER countries and it's country profiles and commonality reports. ( not [https://svn.eionet.europa.eu/projects/Zope/search/opensearch?q=wiki%3ADiversityReports DiversityReports] aka National and regional stories). The list is grouped per country and if there is a report for a theme that doesn't have all the questions then the header for that section is marked red. The reports use normal folder contents/navigation listing colors to indicate which state they are in. If you are looking for unpublished reports related to above problem then they would be in red color(private state). eea.soer countries
The package eea.soer is used by SENSE countries Belgium, Serbia and Slovakia. They run Plone 3 so eea.soer and all it dependencies must work on this setup. If you do big changes that require migration step this step should work on Plone 3 too. They manage their content in their Plone sites and we use the RDF export feature to import it to SOER website.