Skip to first unread message
societe....@cableamos.com
Nov 17, 2017, 2:29:23 PM11/17/17
to AtoM Users
Bonjour,
Je remarque une différence de comportement pour la recherche dans une nouvelle installation d'AtoM.
Quand je cherche pour un identifiant dans la première, les résultats sortent comme prévu.
Dans la seconde installation, il n'y a aucun résultat pour la même recherche.
Par contre en spécifiant le champs de recherche (dans la "Recherche avancée"), dans ce cas "Identifiant (cote)", les résultats sortent.
Est-ce que quelqu'un aurait une idée de la raison de ce comportement de l'outil de recherche?
Merci!
I notice a difference in behavior for searching in a new AtoM installation.
When I search for an identifier in the first, the results come out as expected.
In the second installation, there is no result for the same search.
On the other hand by specifying the search field (in the "Advanced search"), in this case "Identifier (dimension)", the results come out as expected.
Would anyone have an idea of the reason for this behavior of the search tool?
Thank you!
Guillaume Trottier
Guillaume Trottier
Dan Gillean
Nov 17, 2017, 3:36:21 PM11/17/17
to ICA-AtoM Users
Hi Guillaume,
As far as I can tell, searching for an identifier still works in AtoM 2.4. For example:
You can also search for part of the inherited reference code, as in this example, where the part being searched is the inherited repository code:
To understand more about why this is working as expected in one installation and not the other, we will need to know more about these installations. Such as:
- What is the full version number of both installations?
- Are they installed on the same operating systems? Do they use the same operating system?
- What is the default installation culture of each site? Note, you can always check in apps/qubit/config/settings.yml (docs here)
- What was the language of the user interface when you conducted the search?
- Are the descriptions you are searching for published or draft? Are you logged in when searching, or trying this as a public user?
- What have you tried to resolve the issue - for example, have you tried reindexing your site?
Please share any other information you think would be useful in helping us to understand and reproduce this issue. Thanks!
Regards,
--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/9874aad8-1fc3-4caa-ae1d-5bae25271569%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
societe....@cableamos.com
Nov 20, 2017, 10:02:34 AM11/20/17
to AtoM Users
Hi Dan,
Yes, searching for an identifier still work using the "Identifier" filter. However, in that case, when using "Any field" (default), it find nothing (only on the second installation, on Vagrant).
- What is the full version number of both installations? Both 2.4.0 - 156
- Are they installed on the same operating systems? Do they use the same operating system? One is on a server Ubuntu 16.04 (work OK) ; the other Vagrant Ubuntu 16.04 (Any field don't find the Identifier)
- What is the default installation culture of each site? Note, you can always check in apps/qubit/config/settings.yml (docs here) Both FR
- What was the language of the user interface when you conducted the search? Tried with FR and ENG
- Are the descriptions you are searching for published or draft? Are you logged in when searching, or trying this as a public user? Tried both ; tried both
- What have you tried to resolve the issue - for example, have you tried reindexing your site? Yes, clearing cache (symfony, browser); restart php, restart nginx; reimport; rebuild the nested set
Could it be related to Elasticsearch?
Thank you for your help!
Guillaume
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Dan Gillean
Nov 20, 2017, 10:38:40 AM11/20/17
to ICA-AtoM Users
Hi Guillaume,
Very interesting that this is particular to the Vagrant box! I'll try reproducing it there and see what I can find. Thanks for the further information. More soon!
Regards,
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/cfa4904b-632b-4b4d-a48d-8cbab1b04eb7%40googlegroups.com.
Dan Gillean
Nov 21, 2017, 6:10:50 PM11/21/17
to ICA-AtoM Users
Hi again Guillaume,
I've managed to recreate this in the 2.5 Vagrant box - it works fine in the 2.4 Vagrant box for me. Are you running the 2.5.0.0 version? You can check on the version of all your installed Vagrant boxes by running the following command in your host computer:
- vagrant box list
I suspect that this a regression resulting from our recent work to update the Elasticsearch index to 5.x in AtoM 2.5, as described in this ticket:
This is still a work in progress (there are a huge amount of changes, and we're still tracking down the regressions), and we know that there will be more to do to make sure everything continues to work as expected. Thanks for letting me know about this - I'm going to keep testing, and will report the feedback so we can follow up.
As a reminder: the boxes do not automatically update themselves based on our code repository! So don't forget to run git pull --rebase to pull in the latest changes. You may also want to do some of the other maintenance tasks described in slides 18-21 of this slide deck:
That said, it's broken in mine too, where I've done this, so I don't expect this to fix the issue until we've pushed a fix.
Thanks for bringing this to our attention. We'll make sure to test thoroughly prior to the 2.5 release!
On Mon, Nov 20, 2017 at 10:38 AM, Dan Gillean <d...@artefactual.com> wrote:
Hi Guillaume,Very interesting that this is particular to the Vagrant box! I'll try reproducing it there and see what I can find. Thanks for the further information. More soon!Regards,
Dan Gillean
Dec 1, 2017, 4:12:09 PM12/1/17
to ICA-AtoM Users
Hello again Guillaume,
We have a fix in the 2.5 code branch now - if you perform a git pull --rebase (and I recommend other upgrade/maintenance tasks as well, which are outlined in slides 18-21 of the slide deck I previously linked to), then you should be able to pull in the fix for this and see searches for identifiers working again in your Vagrant box.
If you are interested in the development details of the fix, you can see the related pull request here:
Cheers,
Reply all
Reply to author
Forward
0 new messages