Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.

If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping

Answers may be delayed for posts that do not include sufficient information.

Quick and Basic Search

Hi. I'm having problem in finding the objects I create. I am working with providence 1.6.3.

the idno is defined as xx.1234.5.6
(2 characters, a dot, a number, a dot, another number).

I also added nonpreferred labels like '1234' (just the first number) or like "MV.1234" for each object

The point is that I cannot find any object by using quick o basic search looking for any specific idno (i.e. MV.1234.0.0, or - better - just MV.1234). It works just with other labels (preferred label, title,...)

It seems that it is only possible to find an object by idno using the Advanced Search.

Any suggestions? maybe changing the search_indexing.conf file (I am using the one provided without changes).

Thank you!


  • Hi,

    The default search_indexing.conf file *should* already be accounting for identifiers of that format, so the first thing I would try is rebuild your search indices. They may just be out of sync, which can cause searches on identifiers to fail.

    You can rebuild the search index in the web UI from Manage - Administration - Maintenance - Rebuild Search Indices.

    If that doesn't solve the problem, then the issue may in fact have to do with how your search_indexing.conf file is configured. Here is the relevant documentation for fixing it:

    Hope this helps!
  • thank you Jonathan!
    It worked fine!

    Really, in the search config, the expressions 
    search_tokenizer_regex = ^\pL\pN\pNd/_#\@\&\.
    indexing_tokenizer_regex = ^\pL\pN\pNd/_#\@\&\.
    had a "-" instead of the "." at the end.
    Changing it and rebuilnding indices made the difference!
    Ciao e grazie,
Sign In or Register to comment.