[OPEN-ILS-DEV] ***SPAM*** Re: ***SPAM*** Re: script to break up big marc load to avoid cataloging conflict

[John Craig]

Melissa Belvadi wrote: So back to my original question. Any idea if such a batch script type sequence of steps would be feasible? Or will Vandeley actually solve my main problem for me? but am trying to avoid the ritual of having to ask cataloging and reserves to stop adding bib records for multi-hour stretches while this loads (because of the bib record id conflict problem), If you have a solution planned that works, other than the bib record id conflict problem, then presumably your programming is hitting the database directly (rather than using the middle-ware--which would preclude any id conflicts)? If you're already fiddling around at that level, I'm wondering how you're getting record id conflicts in the first place, though.... In any case, if this is the problem, then it sounds like you could either: 1) use the biblio.record_entry_id_seq to get the id's you need for your process (so there won't be any conflicts with other, "normal" cataloging activities (this seems like the best of my suggestions); or 2) alter the sequence so that there's a gap of sufficient size (give yourself some headroom: maybe 60,000) so that you can do your fiddling without disrupting anything else (this sounds quite messy, but it did come to mind because it's a technique we use in data migrations). (I have some other ideas, but as they don't really apply to Evergreen development, I'll contact you off the list about them.) John