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

Description:
We have two libraries, abc01 and abc03, for which we want to publish records to Primo. We have this in the abc01 tab_publish:

PRIMO-FULL ABC01PUB N FULLP MARC_XML

and this in the abc03 tab_publish:

PRIMO-FULL ABC03 N FULLP MARC_XML

It seems that p_publish_06 is sometimes skipping records. Is the use of the same publishing_set name in the tab_publish for two different libraries a problem?

Resolution:
Since the library is an element of the z00p record ("z00p_library") and since the library can be an element in the file output by p_publish_06, it would seem that you could prevent the output from these libraries' p_publish_06 from overwriting each other, but there's a problem with this set-up.... The $aleph_root/tab/tab_publish_timestamp has a line like this:

PRIMO-FULL 201105270053487

As you can see, the library is not included. Thus, when you run p_publish_06 for abc01 it will update the line with the value appropriate for the abc01 PRIMO-FULL and when you run it for abc03 it will updated with the value appropriate for the abc03 PRIMO-FULL -- and will no longer be correct for the abc01 PRIMO-FULL.

Thus, you should *not* give publishing sets in different libraries the same name but rather give each a unique name, such as:

PRIMO-ABC03 ABC03 N FULLP MARC_XML

To correct this, in your case, you will need to:

make the change to abc03 tab_publish (and, perhaps, abc01 tab_publish)
dlib $usr_library
util a/17/1 for z00p
rerun p_publish_04 for both abc01 and abc03
rerun p_publish_06 for both abc01 and abc03

Then you should be in a position to test whether, after record updates, the p_publish_06 in each library results in the correct records being published.

tab_publish header corrected by v20 rep_change 3714 to indicate that same publishing set name should not be used for two different libraries.

• Article last edited: 10/8/2013