As a reference librarian, I regularly include a copy of a my strategy with a hypertext link to the search in an email or Google Doc. There is a nice summary of the strategy above the search in PRIMO, but I can't copy it well; it needs a lot of editing if pasted.

In my search history, it is a hyper-link and when I highlight it to copy, it tends to re-run the link.

The alternatives are too share a link (the links too searches are too long -- a short link may work) or to do a screen capture (takes multiple steps and is not as useful).

In sum: it would be nice if I could readily copy the search strategy on the screen that appears above my search results as it appears.

Although we can now display the MARC record in the UI using the "Show source records" we feel this feature is only really useful for Library staff and not for the vast majority of users who will not find it useful and will just add clutter to the full record for the majority. Ideally we would like the "Show source records" to be linked to the Alma library staff role so it will only display when our library staff are logged into Primo.

Currently the only option to display this link in the UI is to have it appear for everyone. We would like the ability to configure this link in a similar way to how we can configure other links in the UI (such as the General Electronic Services links) using service availability rules.

In primo's general configuration, there is a field for a staff email address. This address is used for emails which are generated by primo in response to an issue (e.g. when an IP is automatically blocked because it is suspected of being the source of a DoS attack) and is also displayed to users of primo when an error page is shown. We would ideally like to be able to send these to different email addresses so they can be processed differently. Would it be possible to add a second email address into the primo configuration and use that for one of these options?

As default behavior, Primo not only looks for the patron's query, but according to the guessed language enriches the original keywords of the user with additional terms, in order to improve the performance. Linguistic features ( https://knowledge.exlibrisgroup.com/Primo/ProductDocumentation/TechnicalGuide/120Linguistic_Features ) may be customized by the systems librarian, for example removing or adding synonyms. But these changes affects only the results coming from the local index (i.e. the index built with records coming from the library's pipes for the catalogue, the institutional repository etc.). Primo Central (PC) records are not affected: for PC records the query enrichment is run separately and using the default synonyms, thus ignoring customization applied by the systems librarian.
Expecially in a blended search, results may therefore result hardly explainable or misleading.
To have a consistent behavior the enriched query used for local records should be the one used for PC records as well.

The citation in the existing and new UI for books is not valid MLA or APA.

The PNX information that populates the citations is stored in a hidden mapping table that cannot be edited. For example, I can see that series information for a book comes from addata/seriestitle. Primo will use the entirety of the field in the citation. For this particular record, this is the content of that section:

Rowling, J. K. Harry Potter Ser. ; 2.

Likewise, book titles come from addata/btitle. For this record, this is the entirety of the section:

Harry Potter and the Chamber of Secrets / by J.K. Rowling ; illustrations by Mary GrandPré.

Because the content of the citation is based on fields in your records, you might want to examine your normalization rules for the addata section and see which fields from your source record are being used. Since you're seeing extraneous information in the citations, this might require changes to your source data or to the normalization rules (to pull data from a different source field).

If you want to change which PNX fields Primo uses to build the citation (for instance, changing from addata/btitle to display/title) this would qualify as an enhancement.

Primo Analytics users who also use Tableau would benefit from a generic Tableau Web Data Connector (WDC) available via a Primo Integrations page to integrate Primo Analytics into Tableau vizes via the Ex Libris API.
The WDC could generate report-specific field structure based on the schema/xsd section of the API report XML, making the addition of Primo Analytics report data to Tableau as easy opening an Excel spreadsheet.
Since I do not have Primo, I have not been able to test these as I did with Alma, but this idea is based on the assumption that Primo Analytics reports API output is similar to that in Alma.

Copyright agreement note for ADAM objects displayed in Primo new UI as the old Aleph OPAC page. It does not match the new UI look & feel.
Ex Libris explained that it's impossible to expand copyright agreement notes inside a frame like it was in traditional (old) UI. It happens since new UI supported full SSL protocol and HTML file in Aleph couldn't support this protocol.

My suggestion to change the relevant Aleph HTML file design and font is impossible because there are css differences between Primo new UI and Aleph.

The main idea of this enhancement is to develop the requested page inside Primo New UI instead of bringing it from Aleph since it should show constant text for all ADAM records.