1. Moving from Aleph to Primo
Stephen Winch

2. The Shelcat landscape
Shelcat is currently composed of the library data from:
12 regional NHSS boards
5 special NHSS boards
4 partner organisations
It includes around 40 sub library locations that hold 294,049 items
There are roughly 27,000 registered borrowers (45,000 if you include expired) and around 80 Aleph library staff users.

3. Functions used in Aleph
Circulation
Circulation policies
Bookings
Photocopy requests
Self issue machines/Self issue from Opac
User management
Staff management
Cataloguing
Authority Management (Names, Mesh, DHDT)
Article records (HML, Health Scotland)
Serial records
Z39.50 libraries
Inter Library Loan
BL requesting
Partner records

4. Data that can be migrated
Aleph settings
Bibs
Holdings
Items
Patrons
Loans
Holds

5. Pre-implementation tasks
Data clean up
Remove orphan bibs
Remove duplication
Improve record quality
Improve serial records
Remove lost or missing stock from the system
Remove Patrons
Authorities
System clean up
Remove traces of old libraries and defunct configuration

6. Things we need to consider…
Which user database (Aleph, Athens, Knowledge Network)
Review statuses, circulation policies, material types
How does national and board level functions
How are National/Board eBooks handled
Review number of admin accounts
How are we handling journal article records
Stockmate
Current awareness
Self issue
ILL and Document delivery

7. Next steps Libraries need to consider their collections on Aleph
Get more familiar with Alma/Primo (documentation, videos)
Think about who might represent your service
Stocktaking
Libraries will need to collectively review statuses, circulation policies, material type
NES will do some automated data clean up, but we will be looking for libraries to improve their data. e.g updating serials holdings
Where libraries have capacity there may be additional data improvement tasks they can assist us with e.g removing duplication