Raise the limit to total number of rejections ( currently 1000) for exporting records that are not imported (due to import profile setup)
There is currently no limit to the number or records that can be imported into Alma (as far as I am aware).. there is however a limit of 1000 when needing to export the rejected data.. Workflows would be much better managed if this limit was raised to the total number of rejected records
Dear all,
The export limitation of a 1000 records rejection will be raised to 5000 in the upcoming February 2025 release.
-
Alison Hazelaar commented
Can we please have an update on this? It's frustrating to be limited to 1000 records when checking for issues with imports.
-
Lesley Lowery commented
Can we please get an update on this item? It has been on the "Accepted" list for 2.5 years, and I am increasingly hampered in processing updates at scale in my Network Zone. This change would drastically improve my ability to do that work - which is happening much more frequently now due to large algorithmic updates by OCLC.
When can we expect this idea to be developed and the enhancement to be released?
-
Fran Abbs commented
We would very much like to see this issue addressed. As Ian said, often there is a need to run test imports to check for matching/non-matching before running the import "for real" to merge/add/overlay records. Being able to easily access a complete set of the unimported records is essential if we want to then change the match criteria and run again to handle any not imported in the first attempt. Having to request this file from Support and wait for a response before being able to continue is not good enough and could delay an import that needs to be completed quickly.
Surely if Support are able to access this file of records, a link could be provided in the job report for us to retrieve the file too?
-
Ian commented
There is currently a limit of 1,000 records in downloading the total lists of matched and not-matched records from the job history of an import profile. Often, we need to import thousands of records in a batch. And we sometimes prefer to do a duplication check first by running the import profile that is set to No import upon match, and upon not match. And we may go back to download the match list or the not-match list for further action. But this limit of 1,000 records in downloading the match or not-match results cause inconvenience.