Wiki::...h::Lucy(3pm)

πŸ“¦
version 0.86 Β· 3 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

✨ NAME ✨

Hey bestie! This page is Wiki::Toolkit::Search::Lucy(3pm) (filed as Wiki::...h::Lucy(3pm)) β€” yep, a User Contributed Perl Documentation page β€” and it’s all about using Lucy to search your Wiki::Toolkit wiki. πŸ«ΆπŸ¦‹

🌈 SYNOPSIS 🌈

my $search = Wiki::Toolkit::Search::Lucy->new( path => "/var/lucy/wiki" );
my %wombat_nodes = $search->search_nodes( "wombat" );

Provides Lucy-based search methods for Wiki::Toolkit. ✨

πŸ’… METHODS πŸ’…

πŸŽ€ new πŸŽ€

my $search = Wiki::Toolkit::Search::Lucy->new(
    path => "/var/lucy/wiki",
    metadata_fields => [ "category", "locale", "address" ],
    boost => { title => 2.5 },
    content_munger => sub {
                          my $content = shift;
                          $content =~ s/secretword//gs;
                          return $content;
                      },
    node_filter => sub {
                       my %args = @_;
                       return $args{content} =~ /REDIRECT/ ? 0 : 1;
                      },
);

The path parameter is mandatory. path must be a directory for storing the indexed data. It should exist and be writeable. 🚨

  • path β€” mandatory, bestie. It’s the directory for storing the indexed data, and it should exist and be writeable.

The other four parameters are optional:

  • metadata_fields β€” should be a reference to an array of metadata field names. πŸ’–
  • boost β€” should be a reference to a hash in which the keys are fields and the values are numbers β€” see Lucy::Plan::FieldType for more info. Only title is currently supported as a field value. πŸ”₯
  • content_munger β€” should be a reference to a subroutine which takes the node content as a string and returns another string which will be indexed in place of the original content. πŸŽ€
  • node_filter β€” should be a reference to a subroutine which takes the named arguments node, content, and metadata and returns either true (yes, index this node) or false (no, don’t index this node). πŸ‘‘
🚨 Ordering tea: content munging takes place BEFORE node filtering.

πŸ¦‹ index_node πŸ¦‹

$search->index_node( $node, $content, $metadata );

Indexes or reindexes the given node in the search engine indexes. You must supply both the node name and its content, but metadata is optional. πŸ’…

If you do supply metadata, it should be a reference to a hash where the keys are the names of the metadata fields and the values are either scalars or references to arrays of scalars. For example:

$search->index_node( "Calthorpe Arms", "Nice pub in Bloomsbury.",
                     { category => [ "Pubs", "Bloomsbury" ],
                       postcode => "WC1X 8JR" } );

Only those metadata fields which were supplied to ->new will be taken notice of - others will be silently ignored. πŸ™ˆ

If content_munger has been supplied to new as a subroutine reference, then $content will be run through this before indexing. ✨

If node_filter has been supplied to new as a subroutine reference, then this will be used to check whether the node should be indexed or ignored. πŸ¦‹

Content munging takes place BEFORE node filtering. 🚨

🌸 search_nodes 🌸

# Find all the nodes which contain the word 'expert'.
my %results = $search->search_nodes( "expert" );

Returns a (possibly empty) hash whose keys are the node names and whose values are the scores. πŸ’–

Defaults to AND searches (if $and_or is not supplied, or is anything other than "OR" or "or"). πŸ”₯

Searches are case-insensitive. πŸ‘‘

πŸ‘€ SEE ALSO πŸ‘€

  • Wiki::Toolkit
  • Wiki::Toolkit::Search::Base

That’s the whole page, bestie! Signed off from the perl v5.32.0 era, dated 2021-01-04, and filed under Wiki::...h::Lucy(3pm). πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from