How to test requesting in DCB - intcon-dev environment

For GIL testing, but also applies elsewhere. This guide may also be useful for people testing in other environments, but it is specifically aimed at the K-Int development integration environment, also known as ‘intcon-dev’.

To test requesting on the intcon-dev environment, please follow these steps. The steps differ, depending on if you need to push changes to DCB Service or not.

If you have made changes to DCB Service and are testing their impact, please follow these steps first.

As the automatic deployment of the latest dcb-service commits is currently not working on the intcon-dev environment, you need to do the following before your changes will be reflected there.

• SSH into the intcon-dev box at 195.10.254.20.

• Run

  kubectl get po -n intcon-dev

  to check the status of the pods. If the dcb pod is in an unhealthy state, resolve this first.

  • You can use

    kubectl logs -n intcon-dev dcb-example

    to get the logs for the dcb pod, which is useful to pick up issues.

• To push the latest changes, run

  kubectl rollout restart deployment/dcb -n intcon-dev

Testing requesting

• Log into DCB Admin and navigate to the shared index. If you have the ID of the record you would like to test with (or its title), you can enter that in the search bar.

  • If you don’t have this information, you can use the “contributor UUID” from a bib record to find a cluster record to test with.

  • Filtering bib records by “source system UUID” can also be useful here.

    • For example, if you need a record from the Alma LMS, do the following:

      • Find an Alma Host LMS on the “Host LMS” page in DCB Admin.

      • Copy its UUID.

      • Filter the Bib Records by “sourceSystemId”, using the UUID you copied.

      • The bib records will now all come from Alma cluster records. Choose one, and click on the “Contributor UUID” link. This will take you to the cluster record search in the shared index in DCB Admin.

• Once you have found your record in DCB Admin, you can check “Items” to see which available items it has, and you can click on the “Cluster UUID” link to go to the cluster record details page.

  • Open

    

     

• On the cluster record details page, click “actions” or “New request” (on older versions).

  • Newer versions where the “actions” menu is available also have the option to check out an item. This will place an expedited checkout request that skips tracking and goes straight to checking out an item at the user’s library.

• Fill in the patron barcode and library to authenticate, and then enter the relevant information for your request. You can choose between “automatic” selection, where DCB chooses the item for you, or you can choose to manually select an item yourself.

• When you’re happy, submit your new staff request - if it passes pre-flight checks, it will then be available to track in the DCB Admin “Patron requests page”.

  • From this page, you can select the request to view more details about it, and track its progress in the audit log.