| Age | Commit message (Collapse) | Author |
|---|
|
Only the headline gets a larger font, the network nodes stay with
a 5-pixel font. However, the overall size had been increased by 20%
|
|
You can now import zim files into YaCy by simply moving them
to the DATA/SURROGATE/IN folder. They will be fetched and after
parsing moved to DATA/SURROGATE/OUT.
There are exceptions where the parser is not able to identify the
original URL of the documents in the zim file. In that case the file
is simply ignored.
This commit also carries an important fix to the pdf parser and an
increase of the maximum parsing speed to 60000 PPM which should make it
possible to index up to 1000 files in one second.
|
|
|
|
|
|
|
|
To help identify why remote crawl results may not be received.
|
|
This makes possbile to set up much more advanced document crawl filters,
by filtering on one or more document indexed fields before inserting in
the index.
|
|
As reported by bubul
(http://forum.yacy-websuche.de/viewtopic.php?f=23&t=5924) , LF and MH
acronyms meaning were not detailed.
Also added label tags for improved accessibility on these input fields.
|
|
This permits an easier and more flexible reverse proxy configuration.
Some related mantis issues : http://mantis.tokeek.de/view.php?id=106 and
http://mantis.tokeek.de/view.php?id=701
|
|
(prefer relative for same pg or neighbors) to ease proxied access
e.g. http://mantis.tokeek.de/view.php?id=701
|
|
|
|
Fix mantis 690 ( http://mantis.tokeek.de/view.php?id=690 ).
Tested on :
- MS Windows 10 : Edge, Firefox 49, Chrome 53
- Debian Jessie : Firefox ESR 45
|
|
This page was already no more XHTML 1.0 as it makes use of the HTML5
<progress> element.
Applied current HTML standard recommended Doctype declaration (see
https://www.w3.org/TR/html/syntax.html#the-doctype ).
|
|
|
|
This fixes warnings reported by W3C Nu Html Checker
(https://validator.w3.org/nu/).
|
|
|
|
|
|
using/setting the config param DECORATION_GRAFICS_LINKSTRUCTURE
|
|
when the post-processing started/ended.
|
|
(Make it work as [probably] actually intended)
|
|
|
|
|
|
|
|
- added a servlet api/linkstructure.json which generates a link graph
information in json
- added a javascript link graph renderer hypertree.js using d3 and the
new servlet linkstructure.json
- embedded the new link graph in the crawler monitor and the host
browser
|
|
|
|
|
|
- adopted all YaCy administration pages to new framework
- created new search page layout (working, but still work in progress)
- old skin files are fully appliable! (and looking good)
- target is a new style based on bootstrap examples, see /test.html
- icons in YaCy may be replaced by glyphicons (to be done)
|
|
|
|
|
|
|
|
|
|
|
|
aware servlets
note also http://bugs.yacy.net/view.php?id=106
|
|
settings available in Crawler_p.html servlet for steering.
|
|
monitor page
|
|
|
|
monitor
|
|
the Crawler_p servlet.
|
|
|
|
The default schema uses only some of them and the resting search index
has now the following properties:
- webgraph size will have about 40 times as much entries as default
index
- the complete index size will increase and may be about the double size
of current amount
As testing showed, not much indexing performance is lost. The default
index will be smaller (moved fields out of it); thus searching
can be faster.
The new index will cause that some old parts in YaCy can be removed,
i.e. specialized webgraph data and the noload crawler. The new index
will make it possible to:
- search within link texts of linked but not indexed documents (about 20
times of document index in size!!)
- get a very detailed link graph
- enhance ranking using a complete link graph
To get the full access to the new index, the API to solr has now two
access points: one with attribute core=collection1 for the default
search index and core=webgraph to the new webgraph search index. This is
also avaiable for p2p operation but client access is not yet
implemented.
|
|
http://bugs.yacy.net/view.php?id=218
- reduced Solr logging (/select)
|
|
|
|
|
|
|
|
|
|
|
|
- the list of urls is entered in the expert crawl start in a textfield;
the one-line input field was replaced with a text box
- start urls can also be given in one single line where the urls are
separated by a '|'-character
- as an effect, the crawl profile cannot carry a single start url for
identificaton because it is possible to have more. Therefore the url was
removed from the crawl profile
- this affect all servlets which display a crawl profile: removed the
url field from all there servlets
- to work consistently with several start urls and the other crawl
starts which computed crawl start url lists from sitelists or sitemaps,
the crawl start servlet was restructured completely
- new rules for must-match patterns were created to make it possible
that site crawl starts also work with several crawl starts at once
|
|
|
|
|
|
queue of urls that shall be crawled
|
