Primo publish and load: multiple pipes for different bib libraries or just one?

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
We're a bit confused about the various incidents we've submitted on Aleph publishing and Primo load.

We have four different bib libraries (xxx01, yyy_01, etc.). The question is on whether we really need to load each library via separate pipes within Primo. I thought we had determined that we could output one pipe worth of data from Aleph (via p_publish_06) and then it would be loaded into Primo and separated on that end. But the latest from Ex Libris staff suggests the Primo folks think we need separate pipes to properly load and track the data within Primo.

Can you clarify things at all? I'd rather only track one pipe if Primo can handle things that way, because it would be easier in terms of overhead. I'm just not clear on whether Primo would properly handle the data if it all came in on the one pipe.

Resolution:
Latest info from the Primo side is that these have to be separated into separate outputs so that they can come in as separate incoming pipes. We have changed our tab_publish files accordingly. (We now have "PRIMO-FULL-xxx" in the xxx01 tab_publish , "PRIMO-FULL-yyy in the yyy01 tab_publish, etc.)

• Article last edited: 10/8/2013