arquivo / pwa-technologies

Arquivo.pt main goal is the preservation and access of web contents that are no longer available online. During the developing of the PWA IR (information retrieval) system we faced limitations in searching speed, quality of results, scalability and usability. To cope with this, we modified the archive-access project (http://archive-access.sourceforge.net/) to support our web archive IR requirements. Nutchwax, Nutch and Wayback’s code were adapted to meet the requirements. Several optimizations were added, such as simplifications in the way document versions are searched and several bottlenecks were resolved. The PWA search engine is a public service at http://archive.pt and a research platform for web archiving. As it predecessor Nutch, it runs over Hadoop clusters for distributed computing following the map-reduce paradigm. Its major features include fast full-text search, URL search, phrase search, faceted search (date, format, site), and sorting by relevance and date. The PWA search engine is highly scalable and its architecture is flexible enough to enable the deployment of different configurations to respond to the different needs. Currently, it serves an archive collection searchable by full-text with 180 million documents ranging between 1996 and 2010.
http://www.arquivo.pt
GNU General Public License v3.0
41 stars 7 forks source link

Extracted text API returns results with wrong encoding #915

Open amourao opened 4 years ago

amourao commented 4 years ago

What is the URL that originated the issue? https://arquivo.pt/textextracted?m=http://www.igot.ulisboa.pt/20181109014435

What happened? Results are returned with no encoding information/headers

What should have happened? Encoding should be set, according to the one found in the original page

Screenshots image

danielbicho commented 4 years ago

236 related

amourao commented 4 years ago

965 related

amourao commented 3 years ago

This problem goes all the way back to when the page was parsed in the original text indexer.

This can be improved by better encoding detection in the new indexer, but will still happen for some edge cases.

VascoRatoFCCN commented 1 year ago

reevaluate after solr implementation for textsearch