Prevent portfolio loader from wiping out local coverage
Currently, if we use a portfolio loader to update the portfolios in an electronic collection, e.g. to add a standard note in the portfolio internal description field, the loading of the portfolio loader will wipe out the local coverage in the portfolios. The local coverage will be gone but the coverage statement will remain marked "local".
The portfolio loader I use usually contains only the two columns of ISSN (for matching), and the column of INTERNAL_DESCRIPTION (for adding the note). This is done only for SOME of the portfolios in the collection.
The work around is to load the portfolio loader again, this time, with the portfolio ID and the local coverage, matching on portfolio ID. Then it can restore the local coverage.
This has been submitted as a bug. The Support could duplicate the problem, but suggested the above workaround. For libraries who thought their loading was successful, and didn't realize that all the local coverage was cleared out, it would be a disaster.
Desirable outcome: Alma should only change the values that appear in the portfolio loader, and leave the rest of the data in the portfolios alone. If they are not in the portfolio loaders, that means the users have no intentions of changing them in Alma.
Pauline Liu
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team