AdminDaniel Greenberg
(Product Manager, Ex Libris)
My feedback
9 results found
-
41 votes
An error occurred while saving the comment -
22 votes
An error occurred while saving the comment Hi,
Thank you for your idea. As described by support, Alma provides IIIF support for content stored in Alma Digital. Several institutions have embedded links to external IIIF manifests in Primo, eg https://library.nga.gov/discovery/fulldisplay?docid=alma994117781504896&context=L&vid=01NGA_INST:IMAGE&lang=en&adaptor=Local%20Search%20Engine
Please let me know if you would like me to put you in touch with a relevant institution to hear further details.
Thanks,
Daniel -
4 votes
An error occurred while saving the comment Hi,
As previously discussed, v6.1 includes the option to define any descriptive MD field to populate the share URL, or disable the link altogether. In case of a URL which needs to be generated on the fly, you can use the existing ie.xsl to add the link/s to the MD pane.
Please let me know if you would like to keep this idea open, or whether the updated functionality is sufficient.
Thank you!
Daniel -
1 vote
An error occurred while saving the comment Hi Ryan,
Release 6.1 introduced the video.js player as a replacement to JWPlayer. The player adjusts itself to the frame. Could you please confirm and update the idea accordingly?
Thank you,
Daniel -
4 votes
An error occurred while saving the comment Hi Dave,
Thank you for the suggestion. The British Library example is of JPGs, have you come across an example with PDF search?
Thank you,
Daniel -
24 votes
Adi Alter
responded
Submitted by Ex Libris PM on behalf of our customers
An error occurred while saving the comment Hi Teresa et al,
Please let me know if this issue can be closed. We have quite a strong preference not to provide an additional, "easy" method to categorically ignore all errors, so please let me know if the workaround is sufficient.
Thank you,
Daniel -
27 votes
As described in the comment, part of the request is already supported in 6.0. The rest will be included in 6.1.
An error occurred while saving the comment Hi Jörg,
A solution for issue no 1 is currently available with release 6.0 (please see "Distinguish fully and partially indexed results" in the highlights). Solr will be upgraded to SolrCloud as part of 6.1, providing full indexing redundancy, which will provide a solution for issue no. 2.
Thank you,
Daniel -
1 vote
An error occurred while saving the comment Dear Lijana,
Thank you for your idea. The DI working group has been working with us on download management and I strongly suggest that this idea will be discussed in the context of the WG, perhaps as a next stage of the download control which will be introduced in 6.1
Thank you,
Daniel -
4 votes
5.5 already includes XSLT 2.0 support in the XSLs files used for delivery – IE and file metadata, XSLT viewer and customized SRU response. 6.1 will include XSLT 2.0 in OAI transformation xsl
An error occurred while saving the comment Hi Kris,
We've come across several legal hurdles for upgrading to Saxon 9.8 HE, so before we confront them I would appreciate if you could elaborate on the Rosetta use cases which require XSLT > 1.0. There are currently several XSLs in Rosetta using XSLT 2.0 and we can possibly modify others to use 2.0, depending on your needs.
Thank you,
DanielAn error occurred while saving the comment Hi Kris,
Thank you for your suggestion. We will be upgrading Rosetta to Saxon 9.8 HE which provides implementations of XSLT 3.0. As described in the documentation (https://www.saxonica.com/documentation/index.html#!conformance/xslt30) the majority of the features you describe will be included, excluding Dynamic Evaluation. Thank you, Daniel
Thank you for the idea. Do you require support for a scenario where some titles will require one sort routine while others will require a different sort?