Illiad uses LDS Logic and that may need to be updated depending on what data is changed and how it is represented in z39.50. As for record import into Iliad that is just a screen scrape so data changes will just be copied over. Changes will not affect items already checked out in Illiad or ReShare.
ReShare - Some name changes may help with ReShare but it is unclear what he full effect will be; Tom will email James for clarification ( attached)
Rapid - Jenn created the magic sauce to get Rapid working, she will need to be asked how name changes will affect that system.
ReShare response
There are two places where this can affect how Cornell participates in ReShare:
- How Cornell gets added to requesting rotas (i.e. your MARC records)
- How Cornell and ReShare communicate via Z39.50 and NCIP
For the former, if these changes are going to impact the data in your MARC records – specifically your library and shelving location codes – then we’d need:
- A new full set of records from you in POD
- New Display and Lendability Rules based on these new library and shelving location codes. Here’s the worksheet Cornell filled out during implementation to give us this information – tabs 4.1 and 5.1 are the ones that would need to be redone with the new information
Note that this is only if these codes are changing in your MARC records as well. If they aren’t, then you don’t have to submit new records to POD and provide new display/lendability rules.
For the latter, ReShare will pick up on a lot of the changes automatically – the autoresponder logs every new library/shelving location that comes in and notifies staff when something new comes in via a Z39.50 response. You may need to redo some of your supplying priorities as the autoresponder identifies new locations, but it’s nothing you need to necessarily set up in advance. The only thing that wouldn’t be picked up on automatically would be pickup locations. If existing pickup location names change, or if their LMS location codes change (i.e. the values that ReShare sends along via NCIP so FOLIO knows what the pickup location is), those will need to be done manually. The same goes for any new pickup locations that are being added. That’s not a big deal except for changing the directory slugs for the pickup locations. Those are universally unique identifiers in ReShare that are pretty much set in stone once created, so unless there’s a really strong reasons for it (e.g. the changes are such that the old slug names will look like the lineup with other existing pickup locations – Slug A looks like it should match with Location B and vice versa), Index Data is going to be pretty resistant to making changes to those values.
In short, the vast majority of this stuff will be either easy edits – changing some directory entries, updating supplying priorities as they come into the system – or stuff you’ve already done – providing a fresh set of records to POD. If we need to gets any more serious than that and we need to look at changing pickup location slugs, we’ll reach out to Index Data as soon as we have more information about what kind of changes are being requested there.