SWAN Membership --

This is a follow-up to the posting this morning regarding bibliographic data appearing in Enterprise. The following is some information pertinent to the catalog this week and in the weeks immediately following migration.

• Depending on what type of search you are performing, records appearing in Enterprise may not appear in WorkFlows. Though Enterprise refreshes daily, we have not fully indexed the New 19’s bibliographic records for use in WorkFlows due to the extreme strain it would place on the system. All records will appear normally in WorkFlows on our May 1st Go-Live date.
• If you are able to retrieve any New 19 records in WorkFlows, please do not merge or edit them at this time. However, you may attach new items to existing New 19 records if you wish.
• Many of these records will be duplicates. Please be reminded that SWAN is not taking merge requests until further notice. The bibliographic deduplication at the end of May will handle most duplicate records, at which point SWAN will announce when we will once again accept merge requests. Until then, the support site’s catalog merge submission form has been disabled, and requests via e-mail, tickets, and phone will not be fulfilled.
• Per the previous posting, SWAN's custom format vocabulary has not been applied. As soon as SirsiDynix comfirms the completion of the bibliographic data load, we will run a script to assign the appropriate 590 data. Until then, the Enterprise format facet will not produce expected results for New 19 data, particularly when limiting to Book materials.

For more information about the bibliographic database during and after the migration process, including a timeline of changes, please refer to the notes from February's Cataloging Advisory Group Meeting.