Development update

@Owen Stephens

Development Update

Sprint 221 - GOKB Search Integration and Package Deletion function
As well as planning to bring acquisition functionalities into ERM (Agreements)
Snapshot: GOKB Search tab is now available

Implementers' topic: Customized URLs should be shown in the UI

@Sabrina Bayer

Description

When using the URL customization, the changed URL is only shown in the export file. It would be very useful for our colleagues, if the changed URL is also shown on the AGL and on the  e-Resource record. This would help our cataloguers finding the e-resource on the provider platform quickly.

Notes

Agreements App - Local KB -Platform

• Changes to the platform URL are only visible in the export file

                            ○ Would it be possible to display the changed URL in the user interface?

                            ○ The URLs need to be customized and it would be helpful to see, whether the platform ULR has already been made

• Customization to URLs can be defined by the individual tenant in the Local KB Platform section

• Alternative: you can set up a Proxy-Server in the Local KB Admin section in the settings

                            ○ Due to customization, you could end up with multiple URLs (i.e. one with customization, one with Proxy and one with both)

                            ○ URLs/links for the individual titles can be found in packages --> e-resources in packages

                            ○ If several URLs should be displayed in FOLIO, it would be great to have an indicator on what caused the URL to change (Proxy or Customization)

What information should be included in the package deletion log?

@Owen Stephens

Owen - Package Deletion

• When something is deleted from the KB, what gets deleted depends on the information is provided

• You need to delete three different sets of information, to delete a title (or package), which are linked to each other

                            ○ package Content Item (PCI)

                            ○  Platform Title Instance (PTI)

                            ○ Title Instance (TI)

• Depending on the set-up of the package, deleting a PCI might cause the PTI and TI to no longer be usable

• When deleting the content of a package, FOLIO will tell you how many PCIs it will attempt/expect to delete

                            ○ It will not delete PCIs, that are linked to an agreement line

• What kind of information would be helpful to include in the package deletion report?

Philip Adams: When would I want to delete a PCI and not just set it to inactive?

• You don't have to delete packages, but GOKB contains a lot of information and it would be useful to delete packages that are definitely not used, to increase performance

• Setting a package to inactive can instead be helpful to keep track of acquisition history

Felix Hemme: My initial idea for metadata in the package deletion log statements:

• Job result: There should be a clear indication if something went wrong with a way to retrieve such logs that a user has to pay attention to. If all went okay, the log is just something a user would rarely look at in detail I assume.

• Name of package that included the e-resources

• ID of package

• External package identifier, e.g. GOKB id

• URL of package in the external source, e.g. GOKB URL

• Number of (and potential a FOLIO internal link to) resources that have been deleted from the local KB, divided by their entity: Work, TitleInstances, PTI, PCI

                            ○ Owen: we can't link to something, that has already been deleted. It would need to be captured in the log, before the point of deletion, but the link will then no longer lead to a destination

                            ○ Felix: the link might not be needed

• Number of (and potential a FOLIO internal link to) resources that could not be deleted from the local KB and reason a reason why, e.g because of dependency xyz, divided by their entity: Work, Titleinstances, PTI, PCI

                            ○ Owen: a link to the titles that couldn't be deleted should be possible to include, since the titles still exist

• Meta-metadata: Date of deletion, maybe duration of job run

• Is feedback on the representation/layout on the deletion reports/logs in the user interface also welcome?

                            ○ Owen: yes

• Felix will send some feedback on what they do with the cbs2folio logs