...
The DCB admin module is available to Consortium Central Office, EBSCO and K-Int staff for on-boarding and support activities.
...
Currently, the "Requests" mode contains access to the lifecycle of all DCB transactions. This is a request and circulation troubleshooting tool for implementation specialist and support desk staff.
...
- FOLIO patron group value "undergrad" is mapped to DCB canonical value "200"
| Requests |    |
| Audit | |
| Mappings |   |
FOLIO
QnA
Potentially useful fodder between ICs and Tim Auger Auger during original onboarding
| Question | Answer | Notes | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1. | OpenRS will create a virtual patron record for a specific patron in the borrowing FOLIO member tenant, without identifiable information. Will these be identified with a user type of “shadow,” or is that reserved for staff accounts? (Or maybe “system”?) | Not shadow accounts but "DCB" patrons with a very limited amount of data (DCB Patron Group, DCB Patron Barcode, DCB Library Code (aka agency code), DCB Transaction UUID). For more details on the relationship between entities, see the "Entity Relationship Diagram" section in DCB Integration. | No configuration needed. Automatically generated. | ||||||||
| 2. | Only the borrowing patron should receive patron notices. Is MCO aware of the possibility of customizing notices for OpenRS borrowing? | I have told MCO that they can customize notices for OpenRS borrowing but I've not gone into any detail about how to do it. | Important note – there is only one version of each type of staff slip. Need to inform MOBIUS so they decide whether or not to modify. | ||||||||
| 3. | Each FOLIO member tenant should have a location representing each other member library, under the DCB institution hierarchy. This needs to exist before circulation rules referencing those locations can be created. Who will create the locations in each member tenant? | I would assume MCO since they have the keys to the kingdom and/or a trusted delegate. |
| ||||||||
| 4. | Each FOLIO member tenant will need standard policies (loan, overdue fine, lost item fee, patron notice, request) created for each loan period for OpenRS transactions. Has MCO determined what these policies should contain? Who will create the 5 policies in each member tenant? | MCO is planning to maintain their existing policies. I would assume MCO would either do it themselves or assign it to their member libraries. |
| ||||||||
| 5. | FOLIO allows the use of multiple locations as criteria (connected with an implied “OR”) in a single circulation rule, which may lower the priority of possible development around wildcarding (to parallel Sierra’s feature). Once the location records exist in a FOLIO member tenant, a shared list of locations can be pasted into each tenant’s circulation rules, followed by removing that site’s location from the list. Who will create the circulation rules for lending (at least one per different loan period) in each member tenant? (The patron notice policy for lending transactions will not be set to send notices.) | I was planning to create a template and then have MCO figure out how they want to populate in each system. | |||||||||
| 6. | Every FOLIO member tenant needs patron groups along the lines of “OpenRS long” and “OpenRS short.” Who decides how these will be named? Who will create them? When will we know if MCO has approved this smaller number of loan periods than what they were hoping for? | MCO should decide. I kickstarted the process this morning with Scott Peterson. | |||||||||
| 7. | The circulation rules for borrowing in each FOLIO member tenant will use the borrowing library’s existing patron groups, in conjunction with an OpenRS location, to apply the appropriate sets of circulation policies. (Did I get that right?) Who will create the circulation policies and circulation rules for borrowing in each member tenant? | Correct. I'll create a template for the circ rules and then they can modify to suit their needs and copy into circ rules. It would be ideal if this process (and above processes) followed the standard FOLIO process. | |||||||||
| 8. | Each FOLIO member tenant’s circulation rules will need careful review to ensure that the combination of priority row, criteria used, and order of rule lines applies the OpenRS policies to the appropriate transactions. Who will do this review? | Great question. I will volunteer for manual inspection duties. | |||||||||
| 9. | An OpenRS service point specific to the lending library will be created automatically in the borrowing library’s member tenant. If FOLIO allows circulation transactions to happen without a calendar assigned to the corresponding service point ( , can you confirm?), then OpenRS can simply approximate the calendar’s function by padding due dates (e.g., a 7-day loan might actually be given 10 days). Tim is going to raise this with Molly. Who will notify MCO of this functionality workaround? | Brooks, "No, there must be a valid calendar assigned to the service point to create a loan transaction there." | |||||||||
| 10. | Are DCB transactions written to CIRCLOG? | Yes. | See | ||||||||
| 11. | What is this product called? | OpenRS DCB. OpenRS is the project nam. DCB is a model of Resource Sharing and the first piece of the OpenRS resource sharing portfolio. |
...