search

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
38 stars 7 forks source link

Extract text from page using link from technical details. #1078

Open PedroG1515 opened 3 years ago

PedroG1515 commented 3 years ago

What is the URL that originated the issue? https://arquivo.pt/wayback/19961102125336/http://www.dn.pt:80/#

What happened? Since old collections (e.g., IA) are not indexed with page search there is no possibility to extract the text using the functionality linkToExtractedText present in the technical details.

dcgomes commented 2 years ago

Try again after reindexing missing collections

PedroG1515 commented 2 years ago

DoD

Page search index all small collections as a single large collection to save memory in the query servers.

AWP24 (0,42 TB) EAWP20 (0,01TB) EAWP22 (sem infor) 3 WARCs EAWP25 (1,5 TB) EAWP26, (0,54TB) Weblog (0,03 TB) BlocoEsquerda (0,00TB) BlogsSapo2018 (0,20TB) DEM-IST (0,00TB) DinisAlves2018 (0,00TB) NON (0,00TB) RAQ2017 (0,01TB) RAQ2018 (0.10TB) RAQ2019 (0,51TB) PATCHING2019 (0,04TB) CEGER (0,00TB)

To try:

page search indexing multi-version separated url indexing separated image indexing

We assume that there will be inconsistency between page, url and images

VascoRatoFCCN commented 11 months ago

reevaluate after solr implementation for text search