Page Comparison

Update links in “Library Items” reminder emails

generated by Polaris/LX Starter

• Several links point to current catalog

• Can they be changed?

  • Yes!

  • This will need to be a go-live task.

Self-registration

• City selection

  • Is ILS setting? It is set up in LEAP(?)

    • use text input for city.

  • Current registration has a list of cities. Do we need to recreate the list?

    • NO

  • Do we need to account for the the Country field?

    • Does Canada need to be a country option?

    • NO.

• Error when submitting self-registration; returning an error -1 “Password Invalid”

  • Marmot staff to provide language to Clearview staff for III request

PIN reset

• There’s no obvious path to recreate the “Forgot password” functionality via the Polaris API.

  • Can update patron PIN from the account in Pika (available in the API) from a logged in patron

  • No protected method to reset the PIN via email

  • Can we request a feature request from III to include this in the API?

• Will redirect to classic catalog in interim

  • Marmot staff to provide language to Clearview staff for feature request from III

eCommerce

• Direct out to classic catalog for fine payment

• • Marmot needs the exact URL to direct users to for fine payment

Target audience mapping

• best terminology for target audience?

  • Juvenile

  • Young Adult

  • Audience Facet documentation

Spreadsheet questions

• Spreadsheet link

In library use only status problem

• Marc Export not reporting this status:

  • bibId:

  • exported item data : status subfield e = 1 (In/Available) not 20 (in library use only)

    Code Block
    949 |a 3 |b 74 |f 61922 |e 1 |h 364.15 |i ONE |k REF |o 3 |p 30214100767285 |r 1 |u 1 |w 4 |y 2 |0 17.95 |j 3 |4 1 |5 0 |7 1 |g 1

  • item API call does have the correct status: /synch/item/61922

    Code Block

    { "PAPIErrorCode": 1, "ErrorMessage": "", "ItemGetRows": [ { "LocationID": 3, "LocationName": "Windsor Library", "CollectionID": 74, "CollectionName": "Reference", "Barcode": "30214100767285", "PublicNote": null, "CallNumber": "REF 364.15 ONE", "Designation": null, "VolumeNumber": null, "ShelfLocation": null, "CircStatus": "IN LIBRARY USE ONLY", "LastCircDate": null, "MaterialType": "Book", "TextualHoldingsNote": null, "RetentionStatement": null, "HoldingsStatement": null, "HoldingsNote": null, "Holdable": false, "DueDate": null, "ItemRecordID": 61922, "BibliographicRecordID": 71262, "IsDisplayInPAC": true, "CreationDate": "/Date(1050352455000-0600)/", "FirstAvailableDate": "/Date(1050352455000-0600)/", "ModificationDate": "/Date(1610741124013-0700)/" } ] }

  • Bib API call with include items also doesn’t report “IN LIBRARY USE ONLY” status /synch/bibs/MARCXML?bibids=71262&includeitems=1
    item record marcxml 852, circstatus subfield e = 1

    Code Block

    <marc:datafield tag="852" ind1=" " ind2=" "> <marc:subfield code="a">3</marc:subfield> <marc:subfield code="b">74</marc:subfield> <marc:subfield code="d">61922</marc:subfield> <marc:subfield code="e">1</marc:subfield> <marc:subfield code="f">3</marc:subfield> <marc:subfield code="g">30214100767285</marc:subfield> <marc:subfield code="i">4</marc:subfield> <marc:subfield code="j">2</marc:subfield> <marc:subfield code="k">1</marc:subfield> <marc:subfield code="l">0</marc:subfield> <marc:subfield code="m">REF 364.15 ONE</marc:subfield> <marc:subfield code="r">1</marc:subfield> <marc:subfield code="z">1</marc:subfield> </marc:datafield>

  • MARC export not generating circ status for “in-library use” (at least) items

  • Please investigate status values for items that should be in-library use only in Pika and report any issues you notice

bibliographic extraction

• Item record representation comes in three ways

  • full export - most complete

  • marcxml include Item info - second most complete, but not all from fields as above

  • item API call

Finalizing settings

• Ashley and Beth meeting?

  • Friday 09.27 10 AM

  • Beth to make changes in production site and we’ll review

Confirmation of display

• Holds appear as expected in ILS

• Self-reg users appear as expected in ILS