Nicolas C (Normandy)
My feedback
13 results found
-
91 votesNicolas C (Normandy) supported this idea ·
-
113 votesNicolas C (Normandy) supported this idea ·
-
30 votesNicolas C (Normandy) supported this idea ·
-
26 votesNicolas C (Normandy) supported this idea ·
-
51 votes
Hello,
This idea has been selected in the NERS voting process to be pursued as a new content provider.
We will check with Lexbase if they can provide us with metadata for the Knowledgebases and CDI.
If you can provide a direct contact with Lexbase, that would be very helpful.
Kind regards,
Tamar Ganor
Content Product Manager
Nicolas C (Normandy) supported this idea · -
36 votesNicolas C (Normandy) supported this idea ·
-
38 votesNicolas C (Normandy) supported this idea ·
-
167 votes
Hi all,
This is planned to be handled in the Primo Next Discovery Experience User Interface.
More details on the new interface planning can be found here -
Best regards,
Yael.
Nicolas C (Normandy) supported this idea · -
305 votesNicolas C (Normandy) supported this idea ·
-
7 votesNicolas C (Normandy) supported this idea ·Nicolas C (Normandy) shared this idea ·
-
29 votesNicolas C (Normandy) supported this idea ·
An error occurred while saving the comment -
135 votesNicolas C (Normandy) supported this idea ·
-
44 votesNicolas C (Normandy) supported this idea ·
As it is not possible to :
- Put only the content of a subfield in a LOCAL PARAM but only the whole field;
- put together the contents of 2 MARC fields or subfields;
- assign a field according to whether a content condition is met or not (presence of ' no:' ).
And a fortiori to do these 3 things at the same time to index a LOCAL PARAM.
An Analytics index for related records is essential to manage this type of documents.
And thank you by the way for not neglecting the European customers using UNIMARC fields 461$v and 462$v ! ;^)
Nicolas