Moving records between reserves libraries; tab_move_record
- Article Type: General
- Product: Aleph
- Product Version: 20
Description:
We opened a second reserves library, ABC31, to support reserves for our overseas Campus. This was done based on your response to KB 16384-28497, in which you recommended against sharing a reserves library between 2 ADMs.
We're now finalizing a last phase of cleanup for that project, in which we're trying to transfer some items that were created with ABC30 <-> ABC51 relationships prior to the creation of ABC31.
These are a small number of reserves bibs, but have large numbers of items associated with them, and we're trying to avoid the process of having to recreate all of those items, and instead are looking to clone the reserves bibs and then move the ADM trees between them. Initially, we could not get this to work. I think I've developed a viable workaround, but wanted to see if you saw any potential problems.
What I've done is,
* Temporarily associated ABC30 with both 50 and 51 in library_relation >> ADM ABC30 ABC50 ABC51
* Copied ABC01's tab_move_record to both ABC30 and ABC31
The latter step has me a little nervous, as the documentation indicates this is only for bib libraries. However, without this table specifying the move routines to use, attempts to move items &/or ADMs through the cataloging client were producing errors.
We've tested this in stage, and everything seems to have worked as I'd hoped, but I wanted to open an SI in case there were potential problems that I'm not thinking of.
Resolution:
The Course Reserve libraries are really a sub-category of bib library. Most procedures which can be performed for bib libraries apply equally to Course Reserve libraries, so I think that the use of tab_move_record in the xxx30 is fine -- though I would check carefully to assure that you are getting correct results.
- Article last edited: 10/8/2013