Kelly
My feedback
21 results found
-
53 votes
Kelly
supported this idea
·
-
61 votes
Kelly
supported this idea
·
-
93 votes
Kelly
supported this idea
·
-
51 votes
Kelly
supported this idea
·
-
206 votes
Kelly
supported this idea
·
-
302 votes
Kelly
supported this idea
·
-
56 votes
Kelly
supported this idea
·
-
6 votes
Kelly
shared this idea
·
-
87 votes
Kelly
supported this idea
·
-
27 votes
Kelly
supported this idea
·
-
68 votes
Kelly
supported this idea
·
-
80 votes
Can you please confirm whether the $e subfield is always expected to appear before $0 and $1 in your workflows? If this is consistently the case, it may be possible to address the issue using an XSL normalization rule to automatically position the $e subfield before these subfields.
Kelly
shared this idea
·
-
94 votes
Kelly
supported this idea
·
-
196 votes
AdminTamar Ganor
(Admin, Ex Libris)
responded
Hello,
This idea will be transferred to the Primo forum as it will require product development to support this metadata.
Kind regards,
Tamar Ganor
Content Product Manager
Kelly
supported this idea
·
-
213 votes
Kelly
supported this idea
·
-
73 votes
Kelly
supported this idea
·
-
76 votes
Kelly
supported this idea
·
-
115 votes
Kelly
supported this idea
·
-
70 votes
Kelly
supported this idea
·
-
91 votes
Kelly
supported this idea
·