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

Wrong label on OK button of CitationSaver UI #1358

Closed dcgomes closed 11 months ago

dcgomes commented 11 months ago

What is the URL that originated the issue? https://arquivo.pt/services/citationsaver?l=pt

What happened? The confirmation button on the message presents the label: "Copiar link e fechar" or "Copy link and close". There is no link to be copied. image image image

The label should be: "OK"

The problem prevails in the English version: image

VascoRatoFCCN commented 11 months ago

This happened due to a mis-labeling on the translations: It was getting the text for the savepagenow button rather than the citationsaver button.

It's already fixed in preprod and will sort itself on the next deploy (Helios release)