Luigi Siciliano
My feedback
36 results found
-
11 votes
Luigi Siciliano
supported this idea
·
Luigi Siciliano
shared this idea
·
-
15 votes
Luigi Siciliano
supported this idea
·
-
208 votes
Luigi Siciliano
supported this idea
·
An error occurred while saving the comment -
107 votes
An error occurred while saving the comment
Luigi Siciliano
commented
I mean of course update the value in purge date when saving *the user*.
Luigi Siciliano
shared this idea
·
-
10 votes
Luigi Siciliano
supported this idea
·
-
34 votes
Na'ama Shamir Kenan
responded
Dear Colleagues,
This item is not planned for 2023 but I am keeping it open here for more votes and future reference.
We will let you know if there will be any updates.
BR
Na'ama
Luigi Siciliano
supported this idea
·
-
30 votes
An error occurred while saving the comment
Luigi Siciliano
commented
Actually it would be great if all Public Notes, also those of electronic collection and electronic services and portfolios, could be translatable.
Luigi Siciliano
supported this idea
·
-
64 votes
An error occurred while saving the comment
Luigi Siciliano
commented
Exporting structurally invalid binary MARC records sounds like more like an error that should be pointed out and fixed. Did anyone open a case about it?
-
17 votes
Luigi Siciliano
supported this idea
·
Luigi Siciliano
shared this idea
·
-
85 votes
Luigi Siciliano
shared this idea
·
-
30 votes
Hello,
We will reach out to R&W to the contact you have provided, and ask for their metadata.
Kind regards,
Tamar
Luigi Siciliano
supported this idea
·
-
100 votes
Luigi Siciliano
supported this idea
·
An error occurred while saving the comment
Luigi Siciliano
commented
@François,
the solution you propose is quite powerful. Perhaps a bit complex to implement and manage, but of course powerful.
Simply allowing to include/exclude in the index by resource type (e.g. exclude Book reviews and Reference and include articles) would be an important step ahead that perhaps is more doable in the short term.
However the two ideas go in the same direction and make clear to ExL how some sort of improvement must be figured out.
Luigi Siciliano
shared this idea
·
-
44 votes
Luigi Siciliano
supported this idea
·
Luigi Siciliano
shared this idea
·
-
117 votes
An error occurred while saving the comment
Luigi Siciliano
commented
Let me add that the documentation section I quoted in this idea, explaining the current behavior, is the chapter "The FRBR Vector" in the Technical Guide.
Can be found here:
https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Technical_Guide/040FRBRization/010The_FRBR_Vector
Luigi Siciliano
shared this idea
·
-
Show the terms added to the patron's query by the linguistic features (i.e. stemming, synonyms etc.)
57 votesAn error occurred while saving the comment
Luigi Siciliano
commented
Two closely related ideas are:
new option/checkbox: "expand my results with synonyms"
http://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/18441406-new-option-checkbox-expand-my-results-with-synonSend the same enriched query (stemming, synonyms, etc) to both local index and Primo Central PC index ( important for blended search ) http://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/18551905-send-the-same-enriched-query-stemming-synonyms
There is also a thread in the Primo ML having as subject:
[Primo] query enrichment is applied by default and is a bit a black box - need for improvements to linguistic features
Luigi Siciliano
shared this idea
·
-
35 votes
An error occurred while saving the comment
Luigi Siciliano
commented
Dear Lukas thank you for proposing this old NERS request as idea. Both approaches, copy NR subset (statically) or include NR subset (dynamically) are useful. We preferred in our original NERS proposal the latter approach because it allows to use subset of NR as routines in a procedural language, and in case of update of the NR subset, any change would have been applied automatically to/inherited by all NR using that included subset.
On the other hand statically copying pieces of rules - as you propose in this idea - allows to use them as templates and it's perhaps easier to implement. Which might also be a factor.
Under the circumstances, any of the two solutions would be welcomed.
We strongly support implementation of this idea and we rely on Alma + Primo classic.
Actually, rather than an enhancement request, it looks to me that the current behaviour of Database type collections is inconsistent with the general behavior of collections in the system, and should be fixed without the need of an enhancement request.