2024-08-28 Besprechungsnotizen Index Data & D-Fernleihe ZFL

Frageliste BSZ / BVB

wird gemeinsam durchgegangen

erledigt
Nachfrage / Nachbesserung notwendig
Noch offen

Directory

1. There is no shared address pool in the live environment of the BVB and the BSZ. It must be possible to change the address data of external libraries in the directory itself. It must also be possible to enter new libraries manually. Does this work in the version we get with the InstallationKit?

• At present, however, it is not possible to create German addresses. Only Canada, USA, England, Northern Ireland, Scotland and Wales are possible.

• If the country selection is important for the address entry: Please expand worldwide - not only the TUM maintains interlibrary loan relationships worldwide.

2. Connection between directory and user app seems to be the field “Institutional patron ID” in the directory. Which field in the UserApp is matched? Barcode, Last Name or another one?

Jakub

Barcode

3. What is the function of the field SLUG? Can the ISIL of a library be entered here instead of the name without a blank? Otherwise the name becomes really awkward in Germany! (Example: 114#Stadtbibliothek 'Heinrich Heine' Halberstadt - this is difficult even without a sigel at the beginning). In Germany, only libraries with an ISIL are authorized for interlibrary loan.

4. If I have understood correctly, it is necessary to create the own institution in the directory, including branches, so that the ServicePoints in Folio can be matched, among other things. (Tag “pickup”)

• How do I enter the 4 TUM interlibrary loan points here? (4 campuses, 9 libraries, presumably 4 locations, 20+ ServicePoints...)

ILL Supply

5. the “Location” + “Shelving Location” column is currently not filled.

• Is this a configuration problem in the test system or the quick&dirty created book data? Example 20240000923 in SLNP_TWO

• WHEN will  this column be filled? We would like these columns to be filled as soon as the requests are received in Folio in the RequestsApp (i.e. from the status “searching” at the latest in the ILL Supply). This would be very helpful for libraries like TUM, which have branch libraries at several locations to get a quick overview of which interlibrary loan location / service point still has unprocessed requests.

Evtl. liegt ein Missverständnis vor, wofür die Spalten sind?

6. If I cannot complete a request after all, e.g. because the book cannot be found (or something else), can the reason for cancellation be communicated from ILL Supply to the ZFL? At the moment, the reason is not communicated, only the cancellation itself.

• Can these reasons for cancellation be configured? If so, where? (For copies, for example, “At bookbinder”, “ Issue not available"....)

  

6. erneuter Test am 26.08.24, nach Jakubs Hinweis, daß ein Bug vorgelegen haben könnte:
   - Copy: Es wird gar keine Stornierung übermittelt
   - Loan: Es wird die Stornierung übermittelt (Nicht lieferbar), jedoch nicht der Grund, der angehakt wurde. Nur das Feld “additional note” wird übertragen und im ZFL angezeigt

ILL Request

7. if I cancel a user's order via the ILL Request

• does the user presumably receive a notification - does this have to be configured in ReShare or in the Folio Notifications?

• Is a confirmation sent to the ZFL so that the order is also cancelled there? Or must it be cancelled manually in the ZFL?

Jakub

7.

• noch keine Antwort

• the cancellation will be sent to ZFL
  Test am 26.08.24:
  Maybe i used a bad example  in slnp two (because its a copy AND its ordered in snlp-one): 20240000857
  But when i cancel the request in the ILL Request App of slnp two with the ticked reason "locally available" and an additional note (Please visit the Library in the City Hall): nothing happend in the ZFL. It is still an open request

Especially for the BVB-ZFL:

8.  What happens if I make the cancellation in ZFL (BVB has the user data in ZFL and can store complex text modules there very easily)

• Is the cancellation reported to the ILL Request and deleted there? (Current status with SISIS in BVB)

• If ZFL => ReShare does not work - where and how can I configure very complex cancellation reasons as text modules? Or can I suppress that a cancel in the ILL Request triggers a user notification?

Jakub

if ZFL sends a data change update when the request is cancelled we can report it in the ILL Request app, would be best to verify this