In an electronic portfolio, there is a field called "Electronic material type originating from Bib" which can be overloaded by another field called "Electronic material type".
The Job "Change electronic portfolio information" allows to update the material type of portfolios into the field "Electronic material type" into a set of portfolios.
If we do so, the material type is not updated into the Portfolio service editor's list... which is confusing.

our request : when the material type of a portfolio has been updated in the field "Electronic material type", ALMA should only considare this material type and display it in the Portfolio service editor's list.

We now have the ability to log current access dates and perpetual access dates on a portfolio. However there is no way to display the perpetual access dates in Alma or Primo unless looking at the coverage tab of the portfolio.

It would be good if there was an option to use the perpetual coverage dates as our display dates either by having an additional option for the local, global, local and global section, or just displaying those dates if local only is selected and there is nothing in the local section.

We have titles that we had current and perpetual coverage for , now publication has ceased and we only have access to our perpetual coverage. For this to display in Alma and Primo we have to update the local coverage dates to match our perpetual coverage dates.

Data elements that are set at a Electronic collection service level should cascade down and be applied/display at the electronic portfolio level.
While portfolios that are part of an electronic collection/package inherit the properties that are set at the service level, those inherited properties do not display in Alma in the individual portfolios. For example, the proxy value in the individual portfolios will always display in Alma as "No" even when the true value inherited from the electronic collection's service is "Yes." Similarly, a public or authentication note entered at the electronic collection or service level does not cascade down to the individual portfolio display in Alma either. Currently, the only service level information that appears in a portfolio is the Service Parse Params. Request: Data elements that are set at an electronic collection's service level (specifically, proxy settings and public/authentication notes) should cascade down to the portfolio level display. Staff shouldn't have to check two places to see the correct setting

We currently use the Load Portfolios tool in the Electronic service to update portfolio information. We have found this won't update the PO Line information in the Acquisition tab of the Portfolio. It is included in the data in an extended export of portfolio information, but does any changes/additions made to this field in the spreadsheet are not reflected in Alma when it is loaded.

We would like to be able to add/change this information using the Load portfolios tool.

A recent example of where this would be useful was a number of portfolios were incorrectly deleted from a collection. The portfolio and POL data was able to be extracted from Sandbox, but the POL data did not load into Alma and then had to be entered manually for each portfolio with an individual POL.

Currently electronic portfolios are generated from the 856 fields in the bibliographic record, but they appear in reverse order in ALMA and Primo. Vendors often have 856 for multiple volumes in their records and they often list URLs in the order of their importance. In my attached example, the vendor includes a link to browse the particle resource first, then links to search the collections which contains the resource. The links are listed in order of importance. It is confusing to the user to list v.2 before v.1 and less important searching options before the most direct way of access the material. This should be corrected.

i work almost exclusively with local, standalone portfolios for electronic resources. I need to be able to globally update the "Interface name" field with free text. The"Change Portfolio" job currently only allows the change to be to one of the vendor code names established in the Acquisitions area. Our acquisitions staff have not set up in Alma such codes for many resources, for example, e-collections for which we purchased perpetual access years before we migrated to Alma.

One reason I need an interface name on the portfolios, is that when I do a repository electronic titles search, there is nothing to show me which vendor's record I'm looking at (because they are not gathered in local ecollections, or linked to CZ collections). We might have access to the same audio recording through Naxos and Alexander Street Press, and I can't tell from the title search results display, which record is for Naxos and which for ASP (I have to click "Portfolio List", then "Edit Portfolio", then the "Linking" tab to see the URL).

The "Interface name" field displays on the portfolio "General" tab, where I can manually edit it, and there it allows me to select one of the acquisitions codes or enter free text.

One of our technical support staff was able to globally change the "Interface name" field to free text using an API, I think, but I don't have such privileges.

At present in the coverage tab, there are the global dates, local, and perpetual (if the collection has been identified as having some perpetual access) Some of these titles have free access, which is not technically perpetual but is also not part of a subscription. Could a new line be added to include these free years/volumes, with the option to display these dates (or not) ? It would allow us to reduce the number of Free collections we have which all take users to the same place, and identify why we have access to journal years outside of our subscription dates