Difference between revisions of "Search indexes"
Mgautierfr (talk | contribs) (Do not make `listing/titleOrdered/v1` relative to `C` namespace.) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 4: | Line 4: | ||
All indexes are optional. | All indexes are optional. | ||
All indexes and listing items MUST be stored in uncompressed cluster. | |||
== Xapian Indexes == | == Xapian Indexes == | ||
| Line 15: | Line 17: | ||
'''Mimetype''' : <code>application/octet-stream+xapian</code> | '''Mimetype''' : <code>application/octet-stream+xapian</code> | ||
=== | === Title index === | ||
'''Namespace''': <code>X</code> | '''Namespace''': <code>X</code> | ||
| Line 54: | Line 56: | ||
'''Mimetype''' : <code>application/octet-stream+zimlisting</code> | '''Mimetype''' : <code>application/octet-stream+zimlisting</code> | ||
The content of the listing is the list of all article entries in the zim archive. | The content of the listing is the list of all "article entries" in the zim archive. | ||
Those "article entries" may be redirect (what is a article entry is not really defined in the spec, it is up to the creator to define in which category a entry is). | |||
Entries are sorted using the key <code><title></code> (All article entries are in <code>C</code> namespace by definition) | Entries are sorted using the key <code><title></code> (All article entries are in <code>C</code> namespace by definition) | ||
Latest revision as of 16:37, 25 November 2023
Zim archives contain specific indexes in the X namespace.
They are content that can be used by reader implementation to locate user entries.
All indexes are optional.
All indexes and listing items MUST be stored in uncompressed cluster.
Xapian Indexes
Xapian indexes are xapian database. They have to be opened using the xapian library.
Fulltext index
Namespace: X
Path: fulltext/xapian
Mimetype : application/octet-stream+xapian
Title index
Namespace: X
Path: title/xapian
Mimetype : application/octet-stream+xapian
Listing
Listings are listing of entries.
The content of listing are binary array of entry numbers. Each entry number is 4 bytes (little-endian) unsigned integer. Entry number is the index of the entry in the URL pointer list.
To get the offset of an entry from the title pointer list, you have to look it up in the URL pointer list
Title index v0
Namespace: X
Path: listing/titleOrdered/v0
Mimetype : application/octet-stream+zimlisting
The content of the listing is the list of all entries in the zim archive (all namespace included, including X/listing/title/v0 itself).
Entries are sorted using the key <namespace><title>
Content size is 4 * <nbEntries>
This is the exact same content of the data titlePtrPos.
If present, titlePtrPos should directly point to the data of this entry.
Title index v1
Namespace: X
Path: listing/titleOrdered/v1
Mimetype : application/octet-stream+zimlisting
The content of the listing is the list of all "article entries" in the zim archive.
Those "article entries" may be redirect (what is a article entry is not really defined in the spec, it is up to the creator to define in which category a entry is).
Entries are sorted using the key <title> (All article entries are in C namespace by definition)
Content size is 4 * <nbArticle>
listing/titleOrdered/v1 may be used to pick random articles or to search article by title and be sure that no resource entries are included.