For a total of 24.253 lines (+535).

After a big search with thousands of results, I like to export everything and then re-import it. But here it failed. Some hours of work allowed to find that illegal XML characters could be introduced to Meta-Press.es generated RSS files via the URL of some illustrations. In particular the one talking to PHP Thumbnailer like https://www.journal-ipns.org is.

Some unencoded '&' were passing through, luring the XML parser into unfinished XML entities. My first move was to encoding those '&' with some & # 2 6 ; (without spaces) but this lead to miss interpretation of the URL by the server-side PHP Thumbnailer.

Encoding them with & amp ; did the trick.

Here the problem was that searching for journal-ipns.org in the source list were not giving any results, while the source exists. It was due to the fact that the ListJS library used by Meta-Press.es is interpreting the scheme -atext as : do not include results containing atext in the ListJS search results.

As ListJS is not maintained, Meta-Press.es is now equipped with the Lovasoa version, containing fix for such bugs.

When a timezone were not explicitly chosen by the user (so the default "Browser timezone" setting was used), french users could not schedule new automated search during summer time.

This was fixed by some solid improvements in how Meta-Press.es creates timezoned dates.

This was a (very well) user reported bug. It was the kind of small bugs that should be simple to fix : just re-apply filters each time you add new results to a query. But it was just in the middle of the way of the MVC refactoring of the code (detailed bellow), and the fix needed to import big files.

If you search for "europe" across all the known sources (which is approximately how sources are tested) you end up with more than 10 000 results. Meta-Press.es was able to export them in RSS or CSV, but not in JSON !? And without any error message.

It appears that all the current export procedure might be limited to 20MO files only (it should be 32MO). In our case RSS and CSV files are just smaller than JSON ones, because JSON files include more information, especially the list of sources and their alleged number of results.

The fastest fix was to remove JSON presentation / indentation characters to get a smaller file and pretend that you currently can’t produce searches with more results with Meta-Press.es, but a better solution will have to be found soon.

It might look like an export feature that splits big exports into 20MO file slices and a reworked import feature and dialog to be able to import many slices.

Being focused at it, imports were globally improved in user feedback reactivity while performance penalty for MVC refactoring (impacting JSON imports) have been mitigated by a 15x factor, reducing how often ListJS' lists were re-ordered. Ordering a list is time consuming, and you can’t loose that time when importing a file (as you’re not just waiting for the next source to answer).